You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2009/05/19 16:27:45 UTC
[jira] Created: (JS2-1018) Release 2.2.0 preparation
Release 2.2.0 preparation
-------------------------
Key: JS2-1018
URL: https://issues.apache.org/jira/browse/JS2-1018
Project: Jetspeed 2
Issue Type: Task
Components: Release Preparation
Affects Versions: 2.2.0
Reporter: Ate Douma
Assignee: Ate Douma
Fix For: 2.2.0
For the 2.2.0 release we'll be using the maven portal-pom-1.2 parent pom and the new staging repository at repository.apache.org (Nexus).
The apache release requirements (for using maven) are captured/enforced for a greater part with the portals-pom (inheriting from apache 6 pom).
A few actions needed to be done:
- adjust/verify/clean maven pom configurations leveraging the already predefined plugins and profiles ("rat", "apache-release")
- ensure legal src headers, NOTICE and LICENSE files are in the proper place and provided where needed
- ensure a clean source distribution is (automatically) generated and released to be voted upon as it constitutes the formal ASF release
This task needs to be completed for both j2-admin and the main Jetspeed Portal application
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Issue Comment Edited: (JS2-1018) Release 2.2.0 preparation
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710850#action_12710850 ]
Ate Douma edited comment on JS2-1018 at 5/19/09 12:55 PM:
----------------------------------------------------------
Release preparation for j2-admin seems to be complete now with respect to build configuration and release requirements.
Next step is getting jetspeed portal itself ready on the same level.
I think we should change our current trunk version (both j2-admin and portal) from 2.2-SNAPSHOT to 2.2.0-SNAPSHOT as that is the target version for the upcoming release.
This can also be set during the release itself (interactive release plugin), but that is more error prone and manual work. Doing it upfront can be done more easily using search/replace.
was (Author: adouma):
Release preparation for j2-admin seems to be complete now with respect to build configuration and release requirements.
Next step is getting jetspeed portal itself ready on the same level.
I think we should change our current trunk version (both j2-admin and portal) from 2.2-SNAPSHOT to 2.0.0-SNAPSHOT as that is the target version for the upcoming release.
This can also be set during the release itself (interactive release plugin), but that is more error prone and manual work. Doing it upfront can be done more easily using search/replace.
> Release 2.2.0 preparation
> -------------------------
>
> Key: JS2-1018
> URL: https://issues.apache.org/jira/browse/JS2-1018
> Project: Jetspeed 2
> Issue Type: Task
> Components: Release Preparation
> Affects Versions: 2.2.0
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.2.0
>
>
> For the 2.2.0 release we'll be using the maven portal-pom-1.2 parent pom and the new staging repository at repository.apache.org (Nexus).
> The apache release requirements (for using maven) are captured/enforced for a greater part with the portals-pom (inheriting from apache 6 pom).
> A few actions needed to be done:
> - adjust/verify/clean maven pom configurations leveraging the already predefined plugins and profiles ("rat", "apache-release")
> - ensure legal src headers, NOTICE and LICENSE files are in the proper place and provided where needed
> - ensure a clean source distribution is (automatically) generated and released to be voted upon as it constitutes the formal ASF release
> This task needs to be completed for both j2-admin and the main Jetspeed Portal application
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-1018) Release 2.2.0 preparation
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711155#action_12711155 ]
Ate Douma commented on JS2-1018:
--------------------------------
Trunk is now bumped to version 2.2.0-SNAPSHOT
> Release 2.2.0 preparation
> -------------------------
>
> Key: JS2-1018
> URL: https://issues.apache.org/jira/browse/JS2-1018
> Project: Jetspeed 2
> Issue Type: Task
> Components: Release Preparation
> Affects Versions: 2.2.0
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.2.0
>
>
> For the 2.2.0 release we'll be using the maven portal-pom-1.2 parent pom and the new staging repository at repository.apache.org (Nexus).
> The apache release requirements (for using maven) are captured/enforced for a greater part with the portals-pom (inheriting from apache 6 pom).
> A few actions needed to be done:
> - adjust/verify/clean maven pom configurations leveraging the already predefined plugins and profiles ("rat", "apache-release")
> - ensure legal src headers, NOTICE and LICENSE files are in the proper place and provided where needed
> - ensure a clean source distribution is (automatically) generated and released to be voted upon as it constitutes the formal ASF release
> This task needs to be completed for both j2-admin and the main Jetspeed Portal application
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Resolved: (JS2-1018) Release 2.2.0 preparation
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma resolved JS2-1018.
----------------------------
Resolution: Fixed
All preparation work finished now.
Ready to start the release!
> Release 2.2.0 preparation
> -------------------------
>
> Key: JS2-1018
> URL: https://issues.apache.org/jira/browse/JS2-1018
> Project: Jetspeed 2
> Issue Type: Task
> Components: Release Preparation
> Affects Versions: 2.2.0
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.2.0
>
>
> For the 2.2.0 release we'll be using the maven portal-pom-1.2 parent pom and the new staging repository at repository.apache.org (Nexus).
> The apache release requirements (for using maven) are captured/enforced for a greater part with the portals-pom (inheriting from apache 6 pom).
> A few actions needed to be done:
> - adjust/verify/clean maven pom configurations leveraging the already predefined plugins and profiles ("rat", "apache-release")
> - ensure legal src headers, NOTICE and LICENSE files are in the proper place and provided where needed
> - ensure a clean source distribution is (automatically) generated and released to be voted upon as it constitutes the formal ASF release
> This task needs to be completed for both j2-admin and the main Jetspeed Portal application
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-1018) Release 2.2.0 preparation
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710850#action_12710850 ]
Ate Douma commented on JS2-1018:
--------------------------------
Release preparation for j2-admin seems to be complete now with respect to build configuration and release requirements.
Next step is getting jetspeed portal itself ready on the same level.
I think we should change our current trunk version (both j2-admin and portal) from 2.2-SNAPSHOT to 2.0.0-SNAPSHOT as that is the target version for the upcoming release.
This can also be set during the release itself (interactive release plugin), but that is more error prone and manual work. Doing it upfront can be done more easily using search/replace.
> Release 2.2.0 preparation
> -------------------------
>
> Key: JS2-1018
> URL: https://issues.apache.org/jira/browse/JS2-1018
> Project: Jetspeed 2
> Issue Type: Task
> Components: Release Preparation
> Affects Versions: 2.2.0
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.2.0
>
>
> For the 2.2.0 release we'll be using the maven portal-pom-1.2 parent pom and the new staging repository at repository.apache.org (Nexus).
> The apache release requirements (for using maven) are captured/enforced for a greater part with the portals-pom (inheriting from apache 6 pom).
> A few actions needed to be done:
> - adjust/verify/clean maven pom configurations leveraging the already predefined plugins and profiles ("rat", "apache-release")
> - ensure legal src headers, NOTICE and LICENSE files are in the proper place and provided where needed
> - ensure a clean source distribution is (automatically) generated and released to be voted upon as it constitutes the formal ASF release
> This task needs to be completed for both j2-admin and the main Jetspeed Portal application
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org