Re: Time to cut an Olio release

[Damien Cooke]

Shanti, This mechanism  for labeling releases is extremely simple and widely used.  It provides people with an insight to the magnitude of the change.  But what needs to be determined is what constitutes a x.x.X update and what constitutes an x.X.x update.  In the past I have used X.x.x update for interface changes x.X.x update for functional enhancement and x.x.X for minor fixes. Regards Damien On 18/02/09 11:25 AM, Shanti Subramanyam wrote: Here are some guidelines for versioning : http://incubator.apache.org/guides/releasemanagement.html#best-practice-versioning I know Akara likes to use dates for release names and the guidelines above certainly don't preclude it. I checked the existing incubator projects and they're all using the /major.minor.point/ system of versioning. If we follow this convention, our first release will be 0.1.0. The advantage to this is that if we make only minor changes and/or fix bugs we can simply update the point (to 0.1.1). This naming gives the user some idea of the level of changes that went in. Does anyone else have a suggestion or opinion on the above ? Shanti William Sobel wrote: A month sounds like it's doable, or should be! I think we already have a planned release structure in the repo. Now for the toughest question, how do we want to number the releases? Cheers, - Will Sobel -- Damien Cooke Open Scalable Solutions Performance Performance & Applications Engineering Sun Microsystems Level 2, East Wing 50 Grenfell Street, Adelaide SA 5000 Australia Phone x58315 (x7058315 US callers) Email damien.co...@sun.com