[Cuis] Managing the evolution of Cuis (Public APIs, checking them and Releases)
Ken.Dickey
Ken.Dickey at whidbey.com
Thu Jul 23 02:13:17 CDT 2015
On Thu, 23 Jul 2015 11:59:38 -0300
Juan Vuletich <juan at jvuletich.org> wrote:
> We need a name for this release. The obvious choice is "Cuis4.3-nnnn".
> So, there might be a Cuis4.3-2456, and as that branch evolves, a
> Cuis4.3-2457 and Cuis4.3-2458. Shortly after, we'll be doing the "alpha"
> updates of Cuis4.4. So, I guess #2459 would be (a potential risky
> change) for Cuis 4.4. What if later we need to apply some patch to the
> stable Cuis4.3? How would we name it?
How about a fork with the suffix "-stable" ?
E.g. "4.2-stable", "4.3-stable", ... The revisions on these would be independent of the main development thread. Only bugfixes and (rare) backports.
$0.02
-KenD
More information about the Cuis
mailing list