[CCC DEV] kroc-1.5 vs. master: battle
ellism88 at gmail.com
Tue Apr 23 11:56:37 BST 2013
I would suggest a slightly different route...
Try and cherry pick 1.5 changes into master.
Create a 1.6 branch to avoid any confusion and tag it as 1.6.0.
Tags become releases. We don't bother with preview/beta releases any more.
just bump the minor on fixes.
Branch is only used to back-port bug fixes from master.
On Tue, Apr 23, 2013 at 11:46 AM, Fred Barnes <F.R.M.Barnes at kent.ac.uk>wrote:
> Hi all,
> I sat down the other evening with the intention of pulling things from
> 'master' (unstable) branch into the 'kroc-1.5' (stable) branch. However,
> there's a *lot* and it's not clear to me whether it's all sensible (the
> change looks like 2005/2008 which seems a bit old!). There are probably
> committed in kroc-1.5 that aren't in master, but the log this way isn't
> The way svn and Git merge branches seems to be different, so crudely
> in changes from one to the other is, I suspect, likely to result in a
> horrid mess.
> As the 'master' branch is pretty stable (as far as I know), any objections
> we rename the kroc-1.5 branch (to something like kroc-1.5-stable-old) and
> re-branch 'master' to 'kroc-1.5'? [once that's in place, we can
> (or similar) changes that were made on kroc-1.5[-stable-old] that should be
> kept, if there are any].
> -- Fred
> developers mailing list
> developers at concurrency.cc
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the developers