I would prefer to propose a clean 2.3.1 fixing one of the major issue in
2.3.0. I don't want to hurry to release 2.3.1 without the Aries fix.
I'm sure that Dan will be able to cut off a new Aries release quickly.
If it's take too much time, I will see how to move forward.
It's just a question of days, no more.
Regards
JB
On 01/31/2013 04:38 PM, Claus Ibsen wrote:
On Thu, Jan 31, 2013 at 4:32 PM, Jean-Baptiste Onofré <[email protected]> wrote:
I updated Aries JMX, Blueprint, ... in Karaf 2.3.1-SNAPSHOT, but
unfortunately, this Aries release introduced two new issues.
I created the Jira and provide fixes, I'm afraid that it will require a new
Aries release. Anyway, I'm investigating some workaround, but I would prefer
a clean Aries release.
What about releasing 2.3.1 with the *same* Aries release as 2.3.0.
At least end users of Karaf 2.3.0 gets the fixes.
And when the new Aries release is out and has been tested and works etc.
Then Karaf 2.3.2 can be released.
Regards
JB
On 01/31/2013 03:18 PM, Claus Ibsen wrote:
Hi
Any update on a Karaf 2.3.1 release?
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
