Page History

...

<settings>
  <servers>
    <server>
      <id>apache.stagingreleases.https</id>
      <username>your_user_id</username>
      <password>your_password</password>
    </server>
  </servers>
</settings>

...

Copy the apache-flume-X.Y.Z-{bin,src}.tar.gz{,.{asc,md5,sha1}} files to people.apache.orgthe distribution directory.

$ 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

...

1. Checkout https://svn.apache.org/repos/asf/flume/site/trunk
2. Add a page to the content/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).

   1. 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

      
      

3. Update content/sphinx/releases/index.rst to update the pointer to the latest release.
4. Update content/sphinx/download.rst to also point to the latest release.
5. Update content/sphinx/index.rst as necessary to add a News item to the home page.
6. Copy the release version of the FlumeUserGuide.rst and FlumeDeveloperGuide.rst to the Documentation directory.
7. Commit the changes and push them.

8. Run mvn package and verify the site at target/site/index.html.

9. Run mvn resources:copypre-resources site install.
10. Verify the site at https://flume.staged.apache.org.

...