[CCC DEV] kroc-1.5 vs. master: battle
F.R.M.Barnes at kent.ac.uk
Tue Apr 23 12:28:39 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.
Sounds sensible -- I'll probably start looking at this today, unless anything
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 185 bytes
Desc: not available
More information about the developers