> when I read your message about the critical bug fixed in > the 2.1.2a2 nightly release, so I upgraded to 2.1.2a2. > Now, having 2.1.2 been released immediately after on > saturday 22, I wonder if I should plan to upgrade to 2.1.2 > shortly or if I can stay safely on 2.1.2a2
James v2.1.2a2 and v2.1.2 are identical except for the HTML documenting the release contents, and MX4J being disabled. The code is identical. Visit http://www.red-bean.com/cvs2cl/. cvs2cl.pl is a very nice script that can give you a nice changelog. I just ran it as: cvs2cl.pl -T -F branch_2_1_fcs --delta build_2_1_fcs:build_2_1_2_fcs If we don't switch to use Maven, I may use cvs2cl to produce the change logs, rather than do it manually. You can see what the above command generated by look at the JamesV2/Plans wiki page: http://nagoya.apache.org/wiki/apachewiki.cgi?JamesV2/Plans > I want to take the opportunity of this message to thank you > and the other developers for the job you are doing and the > time you spend on it. Thank you. :-) And you're welcome. We look forward to your continued participation with James. By the way, if you're not familar with http://nagoya.apache.org/wiki/apachewiki.cgi?JamesUsers, you might want to take a moment and add yourself. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
