<div class="gmail_quote">On Fri, Dec 18, 2009 at 1:47 PM, Ed Burns <span dir="ltr"><<a href="mailto:Ed.Burns@sun.com">Ed.Burns@sun.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>>>>> On Mon, 14 Dec 2009 12:33:43 -0500, Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>> said:<br>
<br>
EB> I've added milestones for 2.1 - 2.4. I've deleted 2.next.<br>
<br>
DA> It was fun while it lasted (I say that jokingly because it we were<br>
DA> having a fun play on words with JSF 2.next ;))<br>
<br>
DA> What about 2.0.MR1? Could you add that for the errors we need to have fixed<br>
DA> for the MR?<br>
<br>
As promised I went to the Sun Java EE Architects email list and asked<br>
what was Sun's position on naming. </blockquote><div><br>Thanks!<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Here it is. This is the convention<br>
Sun uses, it's not a JCP mandate.<br>
<br>
8<------------------------------------------<br>
<br>
We apply version numbers to all three of the JCP-defined artifacts -<br>
specification document, reference implementation (RI), and technology<br>
compatibility kit (TCK). At the completion of a JCP update to a<br>
technology, all three artifacts will have the same version number, in<br>
the single dot major.minor format.<br>
<br>
Between JCP updates, each of these artifacts may also be updated,<br>
following these rules:<br>
<br>
* Specification document<br>
<br>
Updates to a specification document that do not change the meaning<br>
of the specification are called "errata". (See JCP Processes for<br>
details.) An errata update to a specification document is indicated<br>
by including a "Rev level" after the specification version number.<br>
<br>
For example, if an initial specification numbered "1.0" is updated<br>
by an errata, the updated document would be given a number of "1.0<br>
Rev a". A subsequent errata update would be "1.0 Rev b".<br>
<br>
Note that since an errata typically does not require a change to<br>
the RI or TCK, a Rev level is never applied to those artifacts.<br>
<br>
* Reference Implementation<br>
<br>
A change to the RI that is not associated with a change to the API<br>
(for example, a bug fix, performance improvement, new feature, etc.)<br>
is indicated by using a dot-dot number of the form major.minor.micro<br>
or a patch number of the form major.minor.micro_patch. The major and<br>
minor numbers correspond to the version of the API that is<br>
implemented.<br>
<br>
To summarize...<br>
<br>
For a spec of version X.Y, the spec document will be version "X.Y" for<br>
the initial release or "X.Y Rev L", where "L" is a letter nominally<br>
starting with "a" and incrementing as more errata are approved via the<br>
JCP Maintenance Review process.<br>
<br>
For a spec of version X.Y, the RI will be "X.Y" or "X.Y.Z", where "Z" is<br>
a number starting with 1 and incrementing as more RI bug fixes are<br>
made. ("X.Y.0" should be considered equivalent to "X.Y") These changes<br>
are outside the JCP process.<br>
<br>
8<------------------------------------------<br>
<br>
As Dan requested, I have made 2.0 Rev a the default target milestone.<br></blockquote><div><br>As always, thanks for your detailed explanation.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Which brings me to the issue captains. I'll check the status of that<br>
volunteer effort as a separate message.<br></blockquote><div><br>I've been meaning to follow-up with you about that. Perhaps we can do it first thing in 2010.<br><br>I also updated several of the issues and noticed that we could use two additional subcomponents:<br>
<br>Configuration (such as faces-config.xml or web.xml)<br>Documentation (errors with JavaDoc, PDLDoc, etc)<br><br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>