...

See http://stackoverflow.com/questions/3618330/what-is-the-format-of-svn-settings-xml-for-use-with-maven-scm-plugin how to change your scm:svn: url and provide a password.

Done with the above? Proceed with the rest of the steps:

...

Create a release specific job to build images:

https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.24.10/

Make sure all the built images are uploaded to Dockerhub

https://hub.docker.com/r/bigtop/slaves/tags/

...

Make sure all the built images are downloaded on docker-slave-06

...

and

...

docker-slave-07

...

https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.4.0-pull/

5.2. Build RPM/DEB packages

Create a release specific job to build packages:

https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.4.0/

5.3.  Sign RPM packages and yum repos

Ref: 

Clone RPMs built by CI job into a temp dir. You can find built packges under jenkins job's workspace. For example:

# Go to the build slave, docker-slave-06 or docker-slave-07, depends on which built the packages
cp -r /home/jenkins/workspace/Bigtop-1.4.0/DISTRO/centos-7/PLATFORM/amd64-slave/output ~/centos-7

Startup a docker images that is RPM based system:

cd ~/
docker run -ti --rm -v $PWD:/tmp bigtop/puppet:1.4.0-centos-7 bash

Prepare the environment for signing:

gpg --import YOUR_CODE_

Make sure all the built images are downloaded on docker-slave-06 and docker-slave-07

for os in centos-6 centos-7 fedora-25 opensuse-42.1 debian-8 ubuntu-16.04; do docker pull bigtop/slaves:1.2.1-$os; done

5.2. Build RPM/DEB packages

Create a release specific job to build packages:

https://ci.bigtop.apache.org/job/Bigtop-1.2.1/

5.3.  Sign RPM packages and yum repos

Ref: 

Clone RPMs built by CI job into a temp dir. You can find built packges under jenkins job's workspace. For example:

# Go to the build slave, docker-slave-06 or docker-slave-07, depends on which built the packages
cp /home/jenkins/workspace/Bigtop-1.2.1/OS/centos-7/output ~/centos-7

Startup a docker images that is RPM based system:

cd ~/
docker run -ti --rm -v $PWD:/tmp bigtop/puppet:centos-7 bash

Prepare the environment for signing:

gpg --import YOUR_CODE_SIGNING_SECRET_KEY
 
echo > ~/.rpmmacros <<__EOT__
%_gpg_name 8C10EE0AYOUR_CODE_SIGNING_KEY_ID
__EOT__

yum install -y rpm-sign createrepo

...

git checkout release-x.y.z
git tag rel/x,y,z -u <signing key ID>
git push --tags

...

Deploy binary packages to permanent location

...

It will take an hour or so for the website to become live, but you can inspect the website by temporarily setting your browser proxy to see the new, unmirrored content (I used FoxyProxy in Firefox) as described in http://www.apache.org/dev/project-site.html.

11. Announce the Release

TODO: Add a news section to the website.

Send an email to announce@apache.org (the from: address must be @apache.org). E.g.

Remember to update download page accordingly.

As said in 

VERSION=X.Y.Z #Example: 1.2.1
svn co https://dist.apache.org/repos/dist/release/bigtop
cd bigtop
svn delete bigtop-$VERSION
svn commit

11. Announce the Release

TODO: Add a news section to the website.

Send an email to announce@apache.org (the from: address must be @apache.org). E.g.

To: announce@apache.org, user@bigtop.apache.org, dev@bigtop.apache.org
Subject: [ANNOUNCE] Apache Bigtop X.Y.Z released

The release is available here:
    https://bigtop.apache.org/download.html#releases

To: announce@apache.org, user@bigtop.apache.org, dev@bigtop.apache.org
Subject: [ANNOUNCE] Apache Bigtop X.Y.Z released

The release is available here:
    https://bigtop.apache.org/download.html#releases

A few highlights of this release include:
    <LIST-OF-ITEMS-TO-BE-HIGHLIGHTED>


With Bigtop X.Y.Z the community continues to deliver the most advanced big data stack to date. More details about X.Y.Z release are here: 
    https://bigtop.apache.org/release-notes.html

Deploying Bigtop is easy: grab the repo/list file for your favorite Linux distribution:
  https://www.apache.org/dyn/closer.lua/bigtop/bigtop-X.Y.Z/repos/
and you'll be running your very own bigdata cluster in no time!

We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at:
https://bigtop.apache.org

Please be noted that for download page it should be updated with following compliance:

• It should contain links to all current and archived releases along with links to KEYS, checksums, and signatures for all releases.
• The links on the page need to be links to release artifacts, not links to directories.
• The links to the asc and sha files should refer to archives only for non-current releases. The current release links should be to apache.org/dist, not archive.apache.org/dist.

12. Add the Next Release to JIRA

Add the next version number (e.g. 0.2.0 after 0.1.0) to JIRA using this
link: https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12311420.

In JIRA mark the released version as "released" on the "manage versions" page. Be sure to fill in a date if not already specified.

13. Remove old releases

As said in 

...

problems, and to get involved, visit the project website at:
https://bigtop.apache.org

Please be noted that for download page it should be updated with following compliance:

• It should contain links to all current and archived releases along with links to KEYS, checksums, and signatures for all releases.
• The links on the page need to be links to release artifacts, not links to directories.
• The links to the asc and sha files should refer to archives only for non-current releases. The current release links should be to apache.org/dist, not archive.apache.org/dist.

12. Add the Next Release to JIRA

Add the next version number (e.g. 0.2.0 after 0.1.0) to JIRA using this
link: https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12311420.

In JIRA mark the released version as "released" on the "manage versions" page. Be sure to fill in a date if not already specified.

13. Remove old releases

...