...

After at least 72 hours, if the VOTE passes, create a RESULT thread announcing the passage.

If the VOTE does not pass, "Drop" the release at https://repository.apache.org, and delete the dist files, e.g.:

svn add dev/incubator/daffodil/*
svn ci -m "Drop Apache Daffodil (incubating) 2.0.0-rc1"

Once the issues are resolved, start again at Creating a Release Candidate to create a new release candidate with a bumped rc number (e.g. rc2).

Incubator Release Vote

You must now create a VOTE thread on general@incubator.apache.org to get approval from the Apache Incubator Project Management Committee for release. This email should be the same as the above, but with the following at the beginning of the email, again making sure to update the links to the vote and result thread.

...

After at least 72 hours, if the VOTE passes with at least 3 binding +1's, create a RESULT thread announcing the passage.

If it does not pass, follow the same steps as if the Daffodil Release Vote fails and create a new release as before.

Promoting to Final Release

...

1. In the Apache dist directory, move the release candidate files to the release directory. The previous release should also be deleted (it is automatically archived at https://archive.apache.org/dist/):

   Code Block
   language bash
   svn mv dev/incubator/daffodil/2.0.0-rc1/ release/incubator/daffodil/2.0.0/ svmsvn rm release/incubator/daffodil/1.0.0/ svn ci -m "Release Apache Daffodil (incubating) 2.0.0"

   
   

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

   
   

3. Release the published Nexus files by visiting https://repository.apache.org, log in, find the release in "Staging Repositories" and selecting "Release".
   
   

4. Modify the website release page to have the following parameters:

   Code Block
   released: true 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/"

   And update 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/"

   
   

5. Give approximately 24 hours for the release files to sync to mirrors and maven central.

6. Send an announcement email to announce@apache.org, dev@daffodil.apache.org, and users@daffodil.apache.org, (note: send three separate emails instead of one email with multiple TO/CC's), with the following template:

   Code Block
   language text
   Subject: [ANNOUNCE] Apache Daffodil (incubating) 2.0.0   The Apache Daffodil (incubating) community is pleased to announce the release of version 2.0.0. Release notes and downloads are available at: https://daffodil.apache.org/releases/2.0.0/ Daffodil is an open source implementation of the DFDL (Data Format Description Language) specification that uses DFDL schemas to parse fixed format data into an infoset, which is most commonly represented as either XML or JSON. This allows the use of well-established XML or JSON technologies and libraries to consume, inspect, and manipulate fixed format data in existing solutions. Daffodil is also capable of the reverse by serializing or "unparsing" an XML or JSON infoset back to the original data format. For more information about Daffodil visit: https://daffodil.apache.org/ Regards, The Apache Daffodil Team

   
   

...