Karaf-343: The issue doesn't mention if the upgrade is to take in a needed bug fix or if this represents new functionality -- as a patch release we should only be updating for fixes, not features (if new features then full backward compatibility must be confirmed).
Other than Karaf-333 and Karaf-344 it appears we have all the issues reported resolved for this patch release round, as such this is a good time for everyone to start trying out their latest snapshot builds on their target platforms (IBM Java, HPUX, Windows, etc). Looking forward to starting the release process and getting a vote started early in the new year :) Cheers, Jamie On Thu, Dec 30, 2010 at 8:37 AM, Andreas Pieber <[email protected]> wrote: > Ok, I've fixed most of the issues assigned to karaf-2.1.x release by now. > Things > missing: > > KARAF-333: waiting for the paxurl release here (the paxurl release fails for > me; > gnodet can you do this please?) > > KARAF-343: seams to be a "wont fix"? WDYT > > KARAF-344: I'll take a look at it later this day > > --> Anything else to do? Otherwise I think we can fix a release date for 2.1 > (when > ppl are comming back to work after new year's parties :)) > > WDYT? > > kind regards, > andreas > > On Sun, Dec 12, 2010 at 10:09:15PM +0100, Andreas Pieber wrote: >> Hey guys, >> >> How do you feel about releasing karaf-2.1.3? We've fixed 6 bugs and also >> included 2 minor improvements till now. 2 Bugs are still opened (with already >> attached patches). I'm goging to give KARAF-315 a shot tomorrow and add one >> or >> two minor improvements to the integration tests. Anything else you want to >> include? Anything else we should do before releasing karaf-2.1.3? >> >> WDYT? >> >> kind regards, >> andreas >> > >
