[jira] [Resolved] (CAMEL-5397) Deal with Camel-Extra backlog

["Henryk Konsek (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henryk Konsek resolved CAMEL-5397.
----------------------------------

    Resolution: Won't Fix

Camel-Extra issues will be hosted on Google Issues [1] from now on.

[1] http://code.google.com/a/apache-extras.org/p/camel-extra/issues/list
                
> 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.0
>
>
> 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
> * configure Maven rat plugin

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira