...
No Format |
---|
git checkout trunk findmvn .versions:set -name pom.xml | xargs sed -i "" -e "s/X.Y.0-SNAPSHOT/X.$(Y+1).0-SNAPSHOT/" find flume-ng-doc/ -name "*.rst" | xargs sed -i "" -e "s/X.Y.0-SNAPSHOT/X.$(Y+1).0-SNAPSHOT/"DnewVersion=X.Y.(Z+1)-SNAPSHOT -DgenerateBackupPoms=false cd build-support mvn versions:set -DnewVersion=X.Y.(Z+1)-SNAPSHOT -DgenerateBackupPoms=false cd .. git add . git commit -m "Updating trunk version to X.$(Y+1).0-SNAPSHOT for Flume X.Y.Z release" |
...
No Format |
---|
git checkout flume-X.Y find . -name pom.xml | xargs sed -i "" -e "s/X.Y.0-SNAPSHOT/X.Y.0/" find flume-ng-doc/ -name "*.rst" | xargs sed -i "" -e "s/X.Y.0-SNAPSHOT/X.Y.0/" mvn versions:set -DnewVersion=X.Y.(Z+1)-SNAPSHOT -DgenerateBackupPoms=false cd build-support mvn versions:set -DnewVersion=X.Y.(Z+1)-SNAPSHOT -DgenerateBackupPoms=false cd .. git add . git commit -m "FLUME-XXXX: Removing -SNAPSHOT from X.Y branch" |
...
Select org.apache.flume from the list of repositories, verify it looks OK, and then click Close using "Apache Flume X.Y.Z" as the description to allow others to see the repository. Note that the staging repository will have a numeric id associated with it that will be used later
4. Copy artifacts to people.apache.orgthe distribution directories
Copy the apache-flume-X.Y.Z-{bin,src}.tar.gz{,.{asc,md5,sha1sha512}} files to the distribution directory.
No Format |
---|
$ ssh people.apache.org
$ cd public_html
$ mkdir apache-flume-X.Y.Z-rcN
$ cd apache-flume-X.Y.Z-rcN
$ wget --no-check-certificate https://repository.apache.org/content/repositories/orgapacheflume-XXXX/org/apache/flume/flume-ng-dist/X.Y.Z/flume-ng-dist-X.Y.Z-{src,bin}.tar.gz{,.{asc,md5,sha1}}
$ for file in flume-ng-dist-*; do mv $file $(echo $file | sed -e "s/flume-ng-dist/apache-flume/g");done
|
Update the staging website
Copy the distribution archive files from flume-ng-dist/target to where https://dist.apache.org/repos/dist/dev/flume is checked out on your machine.
- Use "svn delete" to remove any files from prior releases in the directory.
- Use "svn commit" to update the new files.
Update the staging website
- Clone https://github.com/apache/flume-site.
- Checkout the asf-staging branch.Checkout https://svn.apache.org/repos/asf/flume/site/trunk
- Add a page to the
contentsource/sphinx/releases
directory for the new release, with the Changelog and links to the documentation (refer previous release pages for details. The documentation should simply use the same paths as the previous releases with correct versions - the documentation will be checked in directly to the production website as mentioned below).edit the new release page using a regex. The search string should be
Code Block ^(.*)\[FLUME\-(\d+)\](.*)$
and the replacement string should be
Code Block $1\[`FLUME-$2 <https://issues.apache.org/jira/browse/FLUME-$2>`__\]$3
- Update
content/sphinx/releases/index.rst
to update the pointer to the latest release. - Update
content/sphinx/download.rst
to also point to the latest release. - Update
content/sphinx/index.rst
as necessary to add a News item to the home page. - Copy the release version of the FlumeUserGuide.rst and FlumeDeveloperGuide.rst to the Documentation directory.
- Commit the changes and push them.
Run mvn package and verify the site at target/site/index.html.
- Run mvn pre-site install.
- Verify the site at https://flume.staged.apache.org.
...
No Format |
---|
svn checkout https://dist.apache.org/repos/dist/release/flume dist-flume cd dist-flume mkdir 1{x.0y.0z} cp <all release artifacts including asc/checksum files> 1{x.0y.0z}/ svn rm stable{x.?.?} # remove older version link ln -s 1.0.0 stable # update stable version link svn add stable 1.0.0 svn commitprior release(s) svn commit -m "Release Flume {x.y.z}" |
It may take up to 24 hours for all mirrors to sync up.
...