[CCC DEV] kroc-1.5 vs. master: battle

[Fred Barnes]

Hi,

> 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
else distracts.


Cheers,

-- Fred
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 185 bytes
Desc: not available
URL: <http://lists.concurrency.cc/pipermail/developers/attachments/20130423/f7bee8cb/attachment.pgp>