The Apache Jenkins build system has built Camel.2.14.x.notest (build #186)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.14.x.notest/186/
to view the results.
I believe changing the package name would be a real problem for users of
the library.
Not sure why we can not continue to use that package name since according
to the answers Raul got on the com-dev mailinglist [1] it is up to each
projects PMC to decide how there extras project should be handled.
I'm also not happy with the support/guidance from dev@community regarding
this topic and +1 to move to Github now. I'm not convinced from SF.
Before we are releasing our first release there, please check with the
Apache trademarks first, whether you can still use the name "Camel Extra"
or not. The
Agree. From my point of view, if the Camel extras community feels
comfortable with Github, then go for it. It seems like the joint Apache
Extras effort has somewhat disintegrated anyway.
We did our part: having a discussion there and sharing our concerns at
dev@community. So I'm happy with how we
Hi Tristan
Thanks for helping the project. I have granted your edit karma.
On Thu, Sep 17, 2015 at 9:34 AM, Tristan Hill wrote:
> Hi,
> Per https://camel.apache.org/how-do-i-edit-the-website.html, my ICLA is now
> on http://people.apache.org/committer-index.html (Tristan Hill). Wiki
> username
Hi,
Per https://camel.apache.org/how-do-i-edit-the-website.html, my ICLA is
now on http://people.apache.org/committer-index.html (Tristan Hill).
Wiki username is tristanh.
Thanks
Tristan
