camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henryk Konsek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5397) Deal with Camel-Extra backlog
Date Mon, 02 Jul 2012 14:25:37 GMT

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

Henryk Konsek commented on CAMEL-5397:
--------------------------------------

Regarding the licenses in releases - we can release Camel-extra 2.9 to the old Google-code
SVN repository. The first version of camel-extra in public repo can be 2.10.
                
> 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
> * configure Maven rat plugin

--
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

        

Mime
View raw message