Versions Compared

Old Version 104

changes.mady.by.user Steve Lawrence

Saved on

compared with

New Version 105

changes.mady.by.user Mike Beckerle

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Small improvements.

...

  1. Move the release candidate files to the release directory. (This prompts for your apache account password. It may prompt you about plaintext password storage. If so, it works even if you answer "no".)

    Code Block
    languagebash
    $ svn mv -m "Release Apache Daffodil 2.0.0" \
    https://dist.apache.org/repos/dist/dev/daffodil/2.0.0-rc1/ \
    https://dist.apache.org/repos/dist/release/daffodil/2.0.0/

      

  2. Make a new clean clone (for good measure), create a signed git tag based on the release candidate tag. You need your KEYID (See step 3b above) for your apache signing key, and you will be prompted for the pass-phrase for your apache signing key.

    Code Block
    languagebash
    $ cd /tmp
$ git clone git@github.com:apache/daffodil.git daffodil-2.0.0-rc1
$ cd daffodil-2.0.0-rc1
$ git tag -as -u KEYID -m "Release v2.0.0" v2.0.0 v2.0.0-rc1^{}
$ git push origin v2.0.0

    You can delete the /tmp clone directory  at this point.
     

  3. "Release" the staged files at https://repository.apache.org--log into that URL with id.apache.org credentials, check the box for the Daffodil staging repository, and click "Release" at the top.
     
  4. Deploy the RPM the to Apache Artifactory repository:
     
    1. Download the RPM convenience binary for this release (from e.g., https://dist.apache.org/repos/dist/release/daffodil/2.0.0/)
       
    2. Visit https://apache.jfrog.io/ and login using Apache credentials
       
    3. Click "Artifacts"
       
    4. Click "daffodil-rpm"
       
    5. Click "Deploy"
       
    6. Click "select file" and select the previously downloaded RPM
       
    7. Click "Deploy"
        
  5. Update the JIRA versions to mark the version as released (need to be PMC - ask a PMC member if you are not one).
      

  6. Give approximately 24 hours for the release files to sync to mirrors and Maven Central. To verify, check here
      

    1. https://search.maven.org/  (ensure you can see both daffodil librarys with versions matching all supported scala versions; select one and verify the release versions exist in at least the sbt version)
        

    2. https://www.apache.org/dyn/closer.lua/daffodil/2.6.0 (pick a mirror and ensure the files exist)
       

  7.  Once the mirrors have synced, make the following changes to the daffodil site repository and publish them:

      

    1. 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/daffodil/2.0.0/"
checksum-root: "https://downloads.apache.org/daffodil/2.0.0/"


    2. Modify the release page of the previous release to use archived root URLs, for example:

      Code Block
      artifact-root: "https://archive.apache.org/dist/daffodil/1.0.0/"
checksum-root: "https://archive.apache.org/dist/daffodil/1.0.0/"


    3. Modify the site/doap.rdf file to include the release date and version, for example:

      Code Block
      languagexml
      <release>
    <Version>
        <name>Apache Daffodil</name>
        <created>2018-02-18</created>
        <revision>2.0.0</revision>
    </Version>
</release>


    4. Update the symlink  to the latest Javadoc and Scaladocs in the site/docs directory (note that there is no forward slash at the end of latest).

      Code Block
      languagebash
      $ cd site/docs/
$ ln -sfn 2.0.0 latest


    5. Follow the steps in the README in that repository to test and publish the new release page.
        

  8. 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 1.0.0" \
    https://dist.apache.org/repos/dist/release/daffodil/1.0.0/

      

...

  1. Send an announcement email from your apache.org email address 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 below template.

    (info)  To send to announce@apache.org, your email app needs to be configured. Settings can be found on Apache's Committer Email page. For Gmail, you can request to "Send Email as" and with Thunderbird, you can add a new Outgoing SMTP Server and create a new Identity (Manage Identities) to send from the relay.

    (info) Make sure to update links and use "plain text" editing for the email. HTML editing often leads to broken links or incorrect formatting.


    Code Block
    languagetext
    Subject: [ANNOUNCE] Apache Daffodil 2.0.0 Released

The Apache Daffodil community is pleased to announce the
release of version 2.0.0.

Notable changes in this release include <short summary of changes>.

Detailed release notes and downloads are available at:

https://daffodil.apache.org/releases/2.0.0/

Apache Daffodil is an open-source implementation of the DFDL
specification that uses DFDL data descriptions to parse fixed format
data into an infoset. This infoset is commonly converted into XML or
JSON to enable 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 serializing or
"unparsing" data back to the original data format. The DFDL infoset
can also be converted directly to/from the  data structures carried by
data processing frameworks so as to bypass any XML/JSON overheads.

For more information about Daffodil visit:

https://daffodil.apache.org/

Regards,
The Apache Daffodil Team


  2. The same or a similar announcement can also be posted to the DFDL Workgroup News page here: https://github.com/OpenGridForum/DFDL/wiki/DFDL-Workgroup-News  (Done by a DFDL Workgroup member, like Mike B).
      

  3. Send a tweet from the @ApacheDaffodil twitter account, mentioning the release version, highlights of changes, and a link to the release page. You will need to be invited/accept, via tweedeck,  permission to tweet from the account. At which point you may compose the below style of message from Tweetdeck.

    Code Block
    The @ApacheDaffodil team is excited to announce the release of version 3.1.0!

Notable changes include <short summary of changes>.

Details and downloads at https://daffodil.apache.org/releases/3.1.0/


  4. Various published DFDL schemas and examples will, most-likely, want to be updated so that they automatically reference the latest release of Daffodil from their main branch.

(info)  For some Daffodil releases DFDL schemas must also have updated library versions. (E.g., for release 3.2.0, in the build.sbt the scalaVersion must be "2.12.15" to enable Java 17 to work.) This is generally a good time to update other library versions used by the DFDL schema to newer versions consistent with those used by Daffodil, which are in daffodil/project/Dependencies.scala. (E.g., junit and junit-interface)