...
In the Apache dist directory, move the release candidate files to the release directory:
Code Block language bash svn mv dev/incubator/daffodil/2.0.0-rc1/ release/incubator/daffodil/2.0.0/ svn rm release/incubator/daffodil/1.0.0/ svn ci -m "Release Apache Daffodil (incubating) 2.0.0"
In the Daffodil git repository, create a signed git tag based on the release candidate tag
Code Block language bash git tag -as -u KEYID -m "Release v2.0.0" rel/v2.0.0 v2.0.0-rc1 git push asf rel/v2.0.0
- Release the published Nexus files by visiting https://repository.apache.org, log in, find the release in "Staging Repositories" and selecting "Release".
Give approximately 24 hours for the release files to sync to mirrors and maven central.
Once the mirrors have synced, make the following changes to the daffodil site repository to make the release available:
Modify the release page to have the following parameters:
Code Block released: true date: date of release artifact-root: "http://www.apache.org/dyn/closer.lua/incubator/daffodil/2.0.0/" checksum-root: "http://www.apache.org/dist/incubator/daffodil/2.0.0/"
Modify the release page of the previous release to use archived root URLs, for example:
Code Block artifact-root: "http://archive.apache.org/dist/incubator/daffodil/1.0.0/" checksum-root: "http://archive.apache.org/dist/incubator/daffodil/1.0.0/"
Modify the doap.rdf file to include the release date and version, for example:
Code Block language xml <release> <Version> <name>Apache Daffodil</name> <created>2018-02-18</created> <revision>2.0.0</revision> </Version> </release>
Remove the previous release from the Apache dist repository now that the download URLs point to the archives:
Code Block svn rm release/incubator/daffodil/1.0.0/ svn ci -m "Archive Apache Daffodil (incubating) 1.0.0"
Update the symlink to the latest Javadoc and Scaladocs
Code Block ln -sf 2.20.0 site/docs/latest
Announce the release
...