Hey Ant, I definitely agree - the 1.2.1 release was very worthwhile in terms of being able to quickly turnaround a new release with critical bug fixes included, so now that 1.3 is out and I'd like a few more fixes included soon then it definitely gets my +1 :)
This is my list of ideal inclusions for 1.3.1, along with a brief comment on the priority for me as well as a comment on it's situation: o TUSCANY-2531: Critical o TUSCANY-2535: High, fix already present and tested o TUSCANY-2539: High, no current fix o TUSCANY-2534: High, though with workaround o TUSCANY-2514: Nice to have, though confusing currently Does any one have any thoughts on the applicability/ability of inclusion for these issues' fixes for 1.3.1? Cheers, Dave. -- Dave Sowerby MEng MBCS On Tue, Aug 5, 2008 at 4:11 PM, ant elder <[EMAIL PROTECTED]> wrote: > Now that 1.3 is just out I'd like to do another release! Its been over a > month since the 1.3 branch was taken from trunk and I've been doing a lot of > work on the JMS binding since then so would like to get that code released. > The 1.2.1 release showed its not too much work to do a point release so I > wondered about doing a point release from the 1.3 branch with just the new > changes for the JMS binding and what ever other small JIRAs may be ready. > > Comments? > > ...ant > > > >
