<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
You might consider 1.1.1 to be the "stable" build Olivier suggested
and go through at least a release candidate before declaring 1.1.3.<br>
I found the problem I reported immediately, so probably 1.1.2 hasn't
had enough testing by installed-base users.<br>
<br>
Leigh.<br>
<br>
On 01/25/2012 06:42 AM, Rolf Lear wrote:
<blockquote cite="mid:98cae462f08b0dcd7161b15737854dfc@tuis.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="MS Exchange Server version
6.5.7036.0">
<title>[jdom-interest] JDOM 1.x release schedule</title>
<!-- Converted from text/plain format -->
<br>
<p><font size="2">Hi All.</font>
</p>
<p><font size="2">Given the bug fix pending in the JDOM 1.1.x
stream I believe a new release</font>
<br>
<font size="2">of the JDOM 1.1.x is required.</font>
</p>
<p><font size="2">On the other hand I do not want to be releasing
1.1.x versions for every</font>
<br>
<font size="2">issue that arises.</font>
</p>
<p><font size="2">I think a compromise schedule is viable, and it
goes something like this:</font>
</p>
<p><font size="2">1. build the current JDOM 1.x stream with the
current bug fix in it and</font>
<br>
<font size="2">post it on the github download page. Call it</font>
<br>
<font size="2">JDOM.1.1.x.hotfix.2012.01.25.zip</font>
<br>
<font size="2">2. if any additional bug fixes are needed another
hotfix package will be</font>
<br>
<font size="2">built.</font>
<br>
<font size="2">3. at some fixed point in time we schedule a
formal 1.1.3 release that</font>
<br>
<font size="2">contains all the fixes.</font>
<br>
<font size="2">4. if any bug comes up that is considered to be
'critical' an</font>
<br>
<font size="2">earlier-than-schedule release could be made.</font>
</p>
<p><font size="2">In this case, I think 1st March 2012 is a good
candidate date... 5 weeks</font>
<br>
<font size="2">from now.</font>
</p>
<p><font size="2">Later today I will build the current JDOM 1.x
code base as</font>
<br>
<font size="2">JDOM.1.1.x.hotfix.2012.01.25 and I will post it
to github.</font>
<br>
<font size="2">If any other issues arise I will create hotfix
updates to address them.</font>
<br>
<font size="2">On March 1st I will rebuild the JDOM code again
as 1.1.3 and do the formal</font>
<br>
<font size="2">release process to <a class="moz-txt-link-abbreviated" href="http://www.jdom.org">www.jdom.org</a> as well as
maven-central.</font>
</p>
<p><font size="2">Does this sound like a viable process?</font>
</p>
<p><font size="2">Rolf</font>
<br>
<font size="2">_______________________________________________</font>
<br>
<font size="2">To control your jdom-interest membership:</font>
<br>
<font size="2"><a moz-do-not-send="true"
href="http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com">http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com</a></font>
</p>
</blockquote>
<br>
</body>
</html>