THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
1. Checkout the trunk.
| Code Block |
|---|
svngit checkoutclone httpshttp://svngit-wip-us.apache.org/repos/asf/flume/trunk.git flume |
2. Update CHANGELOG in the trunk to indicate the changes going into the new version.
...
4. Commit back to the trunk.
| Code Block |
|---|
svngit commit -m "Preparing for release 1.0.0" git push origin trunk |
5. Create a branch.
| Code Block |
|---|
svngit copy https://svn.apache.org/repos/asf/incubator/flume/trunk \ https://svn.apache.org/repos/asf/incubator/flume/branches/checkout -b branch-1.0.0 \ -mgit "Branchingpush fororigin branch-1.0.0 releases" |
6. Switch back to trunk branch.
| Code Block |
|---|
git checkout trunk
|
76. Update the "oldversion" value of all pom.xml in the trunk to "1.0.0". 7. Update the "version" value of all pom.xml in the trunk to "1.1.0-SNAPSHOT".
8. Commit back to the trunk.
| Code Block |
|---|
svngit commit -m "Preparing for release 1.1.0 development" git push origin trunk |
9. Tag a candidate, where R (starting from 0) is the iteration number for this candidate:
| Code Block |
|---|
svngit copy https://svn.apache.org/repos/asf/incubator/flume/branches/branch-1.0.0 \ https://svn.apache.org/repos/asf/incubator/flume/tags/flumetag -a flume-1.0.0-rc0 \ -m "flume 1.0.0-rc0 release." |
...
1. Check out the candidate
| Code Block |
|---|
svngit checkout https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.0.0-rc0 |
2. Generate a tarball
| Code Block |
|---|
cd flume-1.0.0-rc0
mvn clean install -DskipTests
|
...
| No Format |
|---|
To: dev@flume.apache.org Subject: [VOTE] Release Apache Flume version 1.2.0 This is the first release for Apache Flume as a top-level project, version 1.2.0. We are voting on release candidate rc0. *** Please cast your vote within the next 72 hours *** The list of fixed issues: https://svn.apache.org/repos/asf/flume/tags/flume-1.2.0-rc0/CHANGELOG<Link-to-CHANGELOG-in-the-tag> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5sum, *.sha1sum) for the source and binary artifacts can be found at: https://people.apache.org/~mpercy/flume/apache-flume-1.2.0-rc0/ The tag to be voted on: https://svngit-wip-us.apache.org/repos/asf/flume/tags/flume-1.2.0-rc0?p=flume.git;a=commit;h=<commit-hash-of-the-tag> The KEYS file can be found here: https://svn.apache.org/repos/asf/flume/dist/KEYS |
...
After you get your settings.xml file configured correctly (see above link) then you can run: mvn clean deploy -DskipTests -Papache-release to push the artifacts to the staging repo.
You will need to go to the Apache Maven Repository @ http://repository.apache.org/
and log in with your Apache LDAP credentials
Once you log in you will see Build Promotion > Staging Repositories on the left hand side
You will want to edit the Flume artifacts that you don't want to push to Maven (you can delete stuff like the release tarball)
Click Close to make the artifatcs atrifacts available on the Staging repository.
To push to Central, you click Release.
...