Sylvain Wallez wrote:
Carsten Ziegeler wrote:
Considering all our version discussions, we want the next Cocoon version to be a minor version change, so this will be 2.2. We will put new features into it that were planned for 2.2 anyway, perhaps except blocks.
Pier suggested that we follow the Linux versioning, so the version numbers .0, .2, etc. mark stable versions whereas .1,.3 etc. mark developer versions. If we want to follow this, we should imho skip 2.2, use 2.3 to indicate a developer version and 2.4 will then be the final and stable version.
I'm sorry, but I never understood this concept of "developper version". Can it be called a version if it's for developpers only ? Isn't this actually a development _branch_ that can be given whatever name we want, such as "newkernel" as was suggested ?
well, one could say the same about alpha and beta ;-)
So you mean that instead of e.g. 2.2-alpha, 2.2-beta, 2.2-rc and 2.2.0 we would have 2.3.0, 2.3.1, 2.3.2 and then 2.4.0 for the stable release? And then 2.4.1 for bug fixes?
As much as I agree that using odd/even numbers to identify meaning is odd, I think it worked very well for linux and I don't see why it shouldn't work for us.
It follows a mental picture that many already have (and, besides, I think HTTPD is following this too)
Considering how things are going in cocoon-land, I guess we'll have a flurry of even numbers because new features are introduced along with bugfixes all the time.
This odd/even numbering scheme applies well IMO for very focused projects but not for the constant evolution and refinement of our large code base. Things may change however with the introduction of real blocks, as each block will live its own life independently and the kernel and core are likely to evolve less.
To sum up, my opinion is : - why not once we have blocks and each block has its own version numbering - it won't fit with the current single large code base we have today
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
