[ 
https://issues.apache.org/jira/browse/CAMEL-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404835#comment-13404835
 ] 

Christian Müller commented on CAMEL-5397:
-----------------------------------------

I started to do some house keeping in camel-extra. Most of the files didn't had 
the right license headers which I fixed today. But because of this, I think we 
cannot release camel-extra 2.9.x in any public Maven repo.

I would like to have a very similar release procedure as we have for our normal 
Camel releases [1]. I started to get the rat plugin working - still in 
progress...

[1] http://camel.apache.org/release-guide.html
                
> Deal with Camel-Extra backlog
> -----------------------------
>
>                 Key: CAMEL-5397
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5397
>             Project: Camel
>          Issue Type: Task
>            Reporter: Henryk Konsek
>            Assignee: Henryk Konsek
>             Fix For: 2.11
>
>
> Camel Extra is always in the tail of "regular Camel". This is sad and should 
> be addressed :) .
> In order to deal with Camel Extra backlog we need to:
> * tag 2.10 release (so Camel Extra can be in sync mainstream Camel)
> * release 2.9 and 2.10 artifacts
> * start syncing artifacts from apache-extra with Maven Central (via
> Sonatype I guess)
> * make sure that whenever new version of Camel (major and minor) is
> released, we release Camel-Extra as well
> * add camel-extra to Jenkins
> * add e-mail notifications on SVN changes
> * rethink Camel-Extra voting process (there is no such now)
> * migrate issues from Google Project into Jira

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to