THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
RCs should be made available in succession until the community is satisfied that the RC in question is of release quality. The RC that finally makes the cut as the release should be used as it was originally built so the RCs will be named as if they were the final release. This means that we have a few technical issues to resolve:
- TODO We need a staging repository where the RCs can be placed so that failed RC attempts don't pollute a release repository
- TODO We need a reliable way of moving the successful RC from the staging repository to the release repository. This is an intended feature for the Repository Manager but we may need a stop-gap solution until the Repository Manager is ready for production use.
...
| No Format |
|---|
mvn release:prepare ... mvn release:perform ... |
- TODO We need to figure out the process of how we tag the RCs, probably don't need to keep them. Maybe just roll over the previous one until the RC is good enough to release.
How to integrate bug fixes into an RC
If bugs are found in the RCs, then the fixes should be applied to the trunk and then immediately be applied to the it will be up to the release manager to integrate the fixes into the release branch.
- TODO Some tag in the SCM message might be useful to give a hint to the release manager, or a tool, as to which revisions need to be merged.
Generating Generating an official release
When you are ready to create a release you need to create a tag and release with the release plug-in:
| No Format |
|---|
svn copy -m "Tag release 2.0.3" svn://svn.apache.org/repos/asf/maven/XXX/branches/maven-2.0.x svn://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.3 |
...
| No Format |
|---|
mvn release:prepare
...
mvn release:perform
...
|
How to integrate bug fixes into a release branch
If bugs are found in the release , then the fixes should be applied to the trunk and then immediately be applied to it will be up to the release manager to integrate the fixes into the release branch. The only time this would no apply is when there are features in the branch that are not present in the trunk i.e. deprecated features.
...