On Thu, Aug 7, 2008 at 10:35 PM, Dave Sowerby <[EMAIL PROTECTED]>wrote:
> 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 > > > > > > > > > Hi Re. JMS. I'm a little nervous about putting completely new function out in 1.3.1. JMS changes that fix deficiencies from 1.3 would be candidates though. As we took so long to get 1.3 out we should probably start 1.4 straight away for new function. We need to vastly improve our release process though. So some thoughts... - Start 1.3.1 straight away to include immediate issues outstanding for 1.3 - Start 1.4 to release new function from trunk - have a washup of 1.3 for areas we need to improve re. our release process - either use 1.4 as an input to the process improvement or as a guinea-pig for process improvements (depends how quickly we want to do 1.4). Re. Dave's JIRA. It looks like we should definitely look at the top 3 (one of them is already done). I'd also like to do TUSCANY-2534 as that's a bit of a mystery. I'd associate them all with the 1.3.1 tag in JIRA and this will help us define 1.3.1. Depending on how may other bugs we get there we may need to set a cut off but let's see. Regards Simon
