Hadrian Zbarcea schrieb:
I dropped the current staged build and will redo the camel-2.3.0 release.
I had mixed feelings about this one. For what is worth, you probably know a -1 does not necessarily mean that a release won't pass, it just mean it won't pass with a unanimous vote. In this particular case there was also a workaround available and the issue was quite isolated.
Thanks for redoing the release, I really appreciate it. Regarding this
particular issue, many Camel/IPF applications that we and our customers
have written rely on having access to the raw input stream. The changes
introduced into the Jetty component in 2.3 are not compatible any more
with these applications - we often need to write large message streams
into a special datastore and not to a file. Writing messages to the
local filesystem is also a security issue in some situations. I think
that migrating existing code by adding a further option to the endpoint
URI is less fragile than providing a custom HttpBinding to workaround
that issue. I just want to keep migration pains as small as possible as
these significantly impact Camel/IPF acceptance.
The few examples missing from the build, and a couple of components made me change my vote (reluctantly) so I decided to redo it.
Camel as any apache project, is volunteer based, so a -1 also implies that you
are willing to jump in and redo the release :).
Fully agree - it's only that I'm currently on vacation and don't have
access to a development environment ATM. Should I ever vote with a -1
again, which I really hope is not necessary, I'll be prepared for
helping to redo the release.
Cheers,
Hadrian
On May 21, 2010, at 3:05 AM, Martin Krasser wrote:
Hi guys,
I see https://issues.apache.org/activemq/browse/CAMEL-2738 as a must-have for
the release. Although, the issue status is marked as resolved for version 2.3
there was a necessary second fix committed by William after the release
candidate (the fix was at revision 946605, see also the last post in this
thread
http://old.nabble.com/2.3-SNAPSHOT%3A-Stream-Caching-again-enabled-by-Bug-Fix-for-Camel-2686-and-CAMEL-2694-%28rev-941275%29--ts28582952.html).
So I have to give my -1 here.
Sorry for coming up that late but I'm currently on vacation with only limited
internet/mail access. I'll try to be available for discussions (if necessary)
within the next few hours.
Claus Ibsen schrieb:
On Fri, May 21, 2010 at 8:22 AM, Willem Jiang <willem.ji...@gmail.com> wrote:
Hi,
I just found there are three examples which pom version are still
2.3-SNAPSHOT, in the Camel 2.3.0 tar.gz And these examples are not published
into staging repo too.
It is caused by these examples is not included in the examples pom.xml, I
just committed a fix[1] for it.
As these examples will not be compiled if the camel2.3-SNAPSHOT is removed.
I'm afraid we need to cut the camel 2.3.0 again.
I dot NOT think this is such a problem that a new release has to be
cut. We just add it to the knowns issue section of the 2.3 release
notes.
So I am still +1 on this release.
[1]http://svn.apache.org/viewvc?rev=946888&view=rev
Willem
Hadrian Zbarcea wrote:
A new release apache-camel-2.3.0 is out with approximately 252 issues
resolved: new features, improvements and bug fixes.
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-005/
The tarballs are here
https://repository.apache.org/content/repositories/orgapachecamel-005/org/apache/camel/apache-camel/2.3.0/
Please review and vote to approve this release binary. Your vote counts!
[ ] +1 Release the binary as Apache Camel 2.3.0
[ ] -1 Veto the release (provide specific comments)
Vote is open for 72 hours.
Here's my +1
Hadrian
