On Thursday 06 April 2006 17:58, Miguel wrote:
> Daniel pointed out that many open source projects have adopted the
> odd-even scheme ... internal development releases are odd and public
> releases are even.

Very good. I wrote up something like this too, but the email seems to got lost 
on the web interface :(

> Under this scheme.
>
> 10.2.0 -> public 'feature' release  - 10.2 branch is created
> 10.3.0 -> development trunk immediately becomes 10.3
>
> 10.3.1 -> development prerelease
> 10.3.2 -> another development prerelease
> 10.3.xx
>
> In parallel with this:
>
> 10.2.1 -> first public bug fix release, fixed in 10.2 branch
> 10.2.2 -> second public bug fix release, fixed in 10.2 branch
>
> 10.4.0 -> following public release - branch is created
> 10.5.0 -> development trunk immediately becomes 10.5

I am fully in favor of this. My argument this morning was that we might indeed 
need a branch for the stable version: the applet is now used on so many 
websites, which will not want to use a development release for a bug fix the 
desperately need...

> When I sent out my first message I proposed:
>
> 10.1 (official public release)
> 10.11 (first public bug-fix release)
> 10.12 (second public bug-fix release)
>
> 10.2 (following public release)
>
> Daniel said that 10.11 > 10.2 ... revealing my 'decimal point centric'
> view of the world.

That would indeed give trouble in many package based systems like Debian.

> Personally, I am now in favor of the odd-even scheme recommended by Daniel.
>
> Q: What do other people think?

I prefer this option too.

Egon

-- 
CUBIC
blog: http://chem-bla-ics.blogspot.com/


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers

Reply via email to