Hi William,
Yes, you can go ahead with your commits. The rest of the release
process is not affected by changes on trunk.
Cheers,
Hadrian
On Aug 23, 2009, at 7:22 PM, William Tam wrote:
Hi Hadrian,
I just submitted a patch to trunk for 2.1 (I saw the POM version
updates and thought the trunk has been cleared). Let me know if it is
a problem.
Thanks,
William
On Sun, Aug 23, 2009 at 7:13 PM, Hadrian Zbarcea<hzbar...@gmail.com>
wrote:
At this time the minotaur is still down. Hopefully it will be back
up
tomorrow so I can finalize the release.
Hadrian
On Aug 22, 2009, at 6:39 PM, Hadrian Zbarcea wrote:
The vote passes with:
[7] +1 binding votes [janstey, rajdavies, jstrachan, wtam,
ningjiang,
cibsen, hadrian]
[1] +1 non-binding votes [cmoulliard]
[0] -1 votes
Many thanks to all who took the time to test this release and to the
community in general who made this release possible.
During the next days I will finalize the release process. The
minotaur
server seems down at the moment.
Hadrian
On Aug 18, 2009, at 5:39 PM, Hadrian Zbarcea wrote:
The first release candidate of apache-camel-2.0.0 is out with 61
new
features, improvements and bug fixes. This concludes more than
one year of
efforts to bring a new and improved Apache Camel. Many thanks to
everybody
in the community who contributed to this release.
Please find the staging repo here:
https://repository.apache.org/content/groups/staging/org/apache/camel/
The tarballs are here
https://repository.apache.org/content/groups/staging/org/apache/camel/apache-camel/2.0.0/
Please vote to approve this release binary
[ ] +1 Release the binary as Apache Camel 2.0-M3
[ ] -1 Veto the release (provide specific comments)
Vote is open for 72 hours.
The Camel Riders
