On Friday, October 14, 2011, Bruno Friedmann elucidated thus: > Dear Developers > > This proposal doesn't have to by applied now, so it's mainly a > reflection for the next run 5.3dev 5.4x > > Most of the package system (rpm / apt) and associated tools doesn't > play well with beta rc string in number making it always complicated > for no good reasons 5.2.0rc2 is > than 5.2.0 (work if we start at > 5.2.1) > > On what I see, most big project now use this numbering politics > alpha stage start with 5.1.6x to 5.1.79 > beta are mostly in the range 5.1.80 to 5.1.89 > rc are in 5.1.90 - 5.1.99 > > This is limiting the number of beta and rc but shouldn't be a big > trouble for Bacula :D > > so if we apply this to the current trunk : 5.2.0rc2 would be numbered > 5.1.92 > > Is that works for you, yes no doesn't care, shut-up etc
Why not just use the same method that the Linux kernel used to use? X.Y.Z: if Y is odd, it's dev, if Y is even it's release. That gives us as many alphas/betas/RCs as needed. j -- Joshua Kugler Part-Time System Admin/Programmer http://www.eeinternet.com - Fairbanks, AK PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel