[jboss-dev-forums] [Design of EJB 3.0] - Versioning Conventions

[ALRubinger]

How will we proceed with versioning conventions in the EJB3 Component?

Originally Carlo had set up a relationship between RC number and release such that RC12 == 0.12.0 for each project comprising the EJB3 component.

However, this becomes invalidated as we've added modules to the project which may or may not change with each subsequent release.  

I'll propose a format of X.Y-SNAPSHOT for trunk, to be named X.Y in a branch (in preparation for tagging) and X.Y.Z for each release, where the following applies:

X = Major version; rewrites, no guarantee of backward-compatibility
Y = Minor version; typically each release with new features or API
Z = Patch version; small changes made as release is prepared

We may then build a matrix in which EJB3 Release N consists of 0.3.0 ext-api. 0.1.3 core, etc, eg.

I'm not married to the above, but I'd like some sort of convention; things are getting messy in there.

S,
ALR

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127262#4127262

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127262