Bill, I prefer the use
of capital -B, -M, and -RC. This is consistent with the capital -SNAPSHOT.
And, it's consistent with what we've been doing with MicroProfile
(just for reference).
Now, if you really
don't care about consistency, I would even throw out the idea of -b, -M,
and -RC. My experience has been that most "build drivers"
use a lower-case -b. But, the milestone and release candidate drivers
use a capital -M and -RC, respectively. --------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect @ IBM e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
Shannon <bill.shannon@xxxxxxxxxx> To:
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx> Date:
[jakartaee-platform-dev] version numbers and release qualifiers Sent
I've updated our versioning spec
 to reflect our recent decision to use dot-dot version numbers for API jar files, e.g., of the form x.0.0. Please let me know if you see any mistakes, especially in the OSGi rules.
Also, we need to decide what release qualifiers to recommend. So
far we've been recommending these (where <number> is a sequence number):
The pre-defined qualifier is "-SNAPSHOT", which raises the question
as to whether our qualifiers should be upper case as well. I've mostly seen lower case being used, which is why the document recommends lower case, but I can see an argument for all qualifiers being upper case.
Once we come to a decision on this I'd like to send it to the PMC and ask them to "bless" it as the recommendation for all EE4J and
Jakarta EE projects.