On Sat, Aug 16, 2008 at 1:53 AM, Peer Sommerlund <[EMAIL PROTECTED]> wrote: > > > 2008/8/16 TK Soh <[EMAIL PROTECTED]> >> >> I am going to release 0.4 with 1.0.1 (in >> a day or two). After that we will try to follow up with a quick 0.4.1 >> release to link to 1.0.2. Though an 0.4.1RC1 would seem like a safer >> approach. > > I think 0.4.1 is a good tag for the next release > > It seems a little too caucious to me to have an RC cycle when you increase > your patch-level -- assuming the version numbering is "major.minor.patch"
I'd very much like to go straight to 0.4.1. An RC is just an extra precaution, since there's still a chance something can be broken by Hg 1.0.2's API change. > major releases may break backwards compatebility > minor releases add (compatible) features > patch releases are bug fixes only > > .. but this is just my opinion > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
