...
After at least 72 hours, if the VOTE passes with at least 3 binding +1's, create a RESULT thread announcing the passage.
Code Block |
---|
Hi all,
The vote to release Apache Daffodil (incubating) 2.6.0-rc2 is now
closed. Thanks to those that took the time to review and vote.
The release has passed with 3 +1 (binding) votes and no 0 or -1 votes.
Binding:
[List of +1 Voters]
Vote threads (as Ponymail isn't showing the whole thread in one link):
(Paul K)
https://lists.apache.org/thread.html/r58be3a87481b89040be50b10acc445b3f04a1502b03beb079785b41e%40%3Cgeneral.incubator.apache.org%3E
(Furkan K, Justin M)
https://lists.apache.org/thread.html/rdec5007b03029a34f74d85531e3c98dc61b43c6278d196c265b725cf%40%3Cgeneral.incubator.apache.org%3E
We will proceed with the official release of 2.6.0. |
As before, if the VOTE does not pass, fix the issues, "Drop" the release at https://repository.apache.org, repeat the "Create Release Candidate" process from the beginning with a new rc number. Note that creating a new release candidate will automatically delete the previous one.
...
Move the release candidate files to the release directory:
Code Block language bash $ svn mv -m "Release Apache Daffodil (incubating) 2.0.0" \ https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.0.0-rc1/ \ https://dist.apache.org/repos/dist/release/incubator/daffodil/2.0.0/
In the Daffodil git repository, create a signed git tag based on the release candidate tag:
Code Block language bash $ git clone git@github.com:apache/incubator-daffodil.git incubator-daffodil-2.0.0-rc1 $ git tag -as -u KEYID -m "Release v2.0.0" v2.0.0 v2.0.0-rc1^{} $ git push asf 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 and publish them:
Modify the release page to have the following parameters:
Code Block released: true date: <date of release> artifact-root: "https://www.apache.org/dyn/closer.lua/incubator/daffodil/2.0.0/" checksum-root: "https://downloads.apache.org/incubator/daffodil/2.0.0/"
Modify the release page of the previous release to use archived root URLs, for example:
Code Block artifact-root: "https://archive.apache.org/dist/incubator/daffodil/1.0.0/" checksum-root: "https://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>
Update the symlink to the latest Javadoc and Scaladocs (note that there is no forward slash at the end of
latest
.Code Block language bash $ ln -sfn 2.0.0 site/docs/latest
Now that the download URLS of the previous release point to the archive, remove that release from Apache dist to free up space on mirrors:
Code Block $ svn delete -m "Archive Apache Daffodil (incubating) 1.0.0" \ https://dist.apache.org/repos/dist/release/incubator/daffodil/1.0.0/
- Update the JIRA versions to mark the version as released.
...