Here's my point of view:
KARAF-301: no interest to merge on 2.1.x. This issue concerns unit tests
and it's more important for the trunk.
KARAF-282: agree to merge on 2.1.x.
KARAF-299: agree to merge on 2.1.x
Regards
JB
On 12/17/2010 12:47 AM, Andreas Pieber wrote:
Ok, I've checked all issues fixed for 2.2.0. I think three issues may be
interesting for backporting:
KARAF-301, KARAF-282, KARAF-299
All other issues are already backported or not relevant for 2.1.x.
While KARAF-301 is quite easy to backport, the other two does not apply
directly. KARAF-299 isn't that important (IMHO). KARAF-282 is not that easy to
port, but is important since this issue also exists for 2.1.3-SNAPSHOT...
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
--
Jean-Baptiste Onofré
---------------------------------
HomePage
http://www.nanthrax.net
---------------------------------
Contacts
[email protected]
[email protected]
---------------------------------
OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086
