mercurial/crew at 9898: 3 outgoing changesets (2 stable)

Thomas Arendsen Hein thomas at intevation.de
Fri Nov 20 10:02:35 CST 2009


* Dan Villiom Podlaski Christiansen <danchr at gmail.com> [20091120 15:04]:
> On 20 Nov 2009, at 14:36, Mercurial Commits wrote:
> 
> > 3 outgoing changesets (2 stable) in mercurial/crew:
> > …
> 
> For what it's worth, I think this is a major improvement! The redundant mails felt like too much information for me, and as a result, I tended to skip them all.

Thanks for the feedback.

> By the way, has a more traditional naming convention for the release branches been considered? Branch names like 1.4.x or 1.4-stable should make it easier to determine the what release contained a given feature or bug fix. Then, rather than merging the development branch into stable, a new branch could be forked and the old one either be closed or left around.

Yes, some people (including me) had that as their first idea, too,
but were convinced that a permanent 'stable' name is better.
(I don't have time to state the reasons right now, maybe someone
else can post a summary)

Regards,
Thomas Arendsen Hein

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1378 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20091120/e26ce556/attachment.bin>


More information about the Mercurial-devel mailing list