Ahh, I see. On 02/04/2010 12:11 PM, Martin Knoblauch wrote:
Perhaps in stead of tagging the "public beta" releases as a final version, they could be tagged as "release candidate". I.e. call it 3.1.6rc1 or 3.1.6pre1 or something similar.3.1.3 .. 3.1.5 were canned during testing. Apparently our process does not allow for fixing bugs/regressions between tagging and final release, so it was decided to never publish the intermediates.
The public beta's are a good way to counter that, but it seems a bit silly to me to skip entire version levels just because of release procedures.One of the reasons might be lack of good beta testing (which I am guilty of myself :-(, but I do not really understand, why we couldn't just keep 3.1.3 as the name of the release.
Cheers Martin
-- R. Bastiaans, B.ICT :: Systems Programmer, HPC&V SARA - Computing& Networking Services Science Park 121 PO Box 94613 1098 XG Amsterdam NL 1090 GP Amsterdam NL P.+31 (0)20 592 3000 F.+31 (0)20 668 3167
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com
_______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
