You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Henryk Konsek (JIRA)" <ji...@apache.org> on 2012/06/26 08:58:44 UTC
[jira] [Created] (CAMEL-5397) Deal with Camel-Extra backlog
Henryk Konsek created CAMEL-5397:
------------------------------------
Summary: 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
--
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
[jira] [Commented] (CAMEL-5397) Deal with Camel-Extra backlog
Posted by "Henryk Konsek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405081#comment-13405081 ]
Henryk Konsek commented on CAMEL-5397:
--------------------------------------
Regarding the release process - I think that 2.11 will be a good starting point to make it more formal.
> 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
[jira] [Updated] (CAMEL-5397) Deal with Camel-Extra backlog
Posted by "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 updated CAMEL-5397:
---------------------------------
Description:
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
was:
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
> 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
[jira] [Commented] (CAMEL-5397) Deal with Camel-Extra backlog
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CAMEL-5397) Deal with Camel-Extra backlog
Posted by "Henryk Konsek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405087#comment-13405087 ]
Henryk Konsek commented on CAMEL-5397:
--------------------------------------
As I understand [1], we want to deploy snapshots and publish to public repo via OSS sonatype repository.
According to the Sonatype OSS guide [2] we should inherit our parent POM from their org.sonaptype.oss:oss-parent:7 POM. Since we already inherit from camel-parent and Maven doesn't support multiple inheritance, we need to copy configuration from the oss-parent parent POM and add it to camel-extra parent manually.
I've done it and committed in rev894. Christian, could you take a look at my commit?
[1] https://issues.sonatype.org/browse/OSSRH-1465
[2] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
> 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
[jira] [Resolved] (CAMEL-5397) Deal with Camel-Extra backlog
Posted by "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
[jira] [Updated] (CAMEL-5397) Deal with Camel-Extra backlog
Posted by "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 updated CAMEL-5397:
---------------------------------
Description:
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
* rethink Camel-Extra voting process (there is no such now)
was:
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
> 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
> * rethink Camel-Extra voting process (there is no such now)
--
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
[jira] [Commented] (CAMEL-5397) Deal with Camel-Extra backlog
Posted by "Henryk Konsek (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CAMEL-5397) Deal with Camel-Extra backlog
Posted by "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 updated CAMEL-5397:
---------------------------------
Description:
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
* rethink Camel-Extra voting process (there is no such now)
was:
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
* rethink Camel-Extra voting process (there is no such now)
> 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
> * rethink Camel-Extra voting process (there is no such now)
--
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
[jira] [Updated] (CAMEL-5397) Deal with Camel-Extra backlog
Posted by "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 updated CAMEL-5397:
---------------------------------
Description:
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
was:
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
* rethink Camel-Extra voting process (there is no such now)
> 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