You've been faster, Hadrian :) Wanted to checkin this morning (no time
left yesterday evening), because I expected you'll start the release
procedure on Monday. I'm going to add my changes to 2.3-SNAPSHOT.
Am 06.02.2010 18:54, schrieb Hadrian Zbarcea:
+1. If you did not ci, please do it fast.
Sorry Martin,
Unfortunately, it seems that nights or weekends are the best time to cut a
release. It took me 12 hours, a bit more than the previous release. Most of
the time is consumed by the artifact upload and a less busy net helps. I
sincerely hope we won't find blockers that would
Hi Hadrain,
William Tam fixed the issue last weekend, I also verified it.
I think we are ready to cut the Camel 2.2.0 release.
Willem
Willem Jiang wrote:
Hi,
I created a JIRA[1] for it and will try to resolve this issue this
afternoon.
[1]
Hi,
I did some pre-relese dry runs in the past couple of days. The trunk is stable
and the issues for 2.2.0 are closed.
I think it's time to start the 2.2.0 release unless you think that there's some
pending issue that absolutely must go in 2.2.0. Please shout.
Thanks,
Hadrian
Hi,
I created a JIRA[1] for it and will try to resolve this issue this
afternoon.
[1] https://issues.apache.org/activemq/browse/CAMEL-2425
Willem
William Tam wrote:
I'd like to investigate some random MTOM test failures reported by
Willem. I'll look at it tomorrow. I hope to get it
On Thu, Jan 28, 2010 at 4:42 PM, Hadrian Zbarcea hzbar...@gmail.com wrote:
Hi,
I did some pre-relese dry runs in the past couple of days. The trunk is
stable and the issues for 2.2.0 are closed.
I think it's time to start the 2.2.0 release unless you think that there's
some pending issue
