Page History

...

1. Find all tickets that have the version being released as their Fix Version, that are not resolved or closed (i.e Unresolved), and do a bulk change (Top Right: Tools > Bulk Edit) and move them to the next release (under Unreleased Versions)
      
2. Do a search for all tickets that have the version being released as their Fix Version, and export it as a CSV (Top Right: Export > CSV (All fields)
     

3. In Excel (or equivalent), delete the columns that aren't needed, then do some manipulation to get that list of bugs in the format for the release page(i.e \{% Jira XXXX %} Title)
     

4. For changes that need more description (e.g. big features), create sections on the release page and add those descriptions.
     

5. For the section on Dependency updates, the following command shows the changes or new dependencies that should be mentioned. 

   Code Block
   language bash
   $ git diff v3.1.0 -- project/Dependencies.scala

   You will of course change "v3.1.0" in that command to the tag of the prior release to the one you are preparing. 

...

Note that these links refer to https://dist.apache.org instead https://downloads.apache.org because this is a pre-release.

Additionally, update the Unsupported Features page if any features/errated errata are now supported in this releasedrelease.

Follow the steps in the README in the daffodil-site repository to test and publish the new release page.

...