Page History

...

The previous steps have pushed the new scaladoc and javadoc to the daffodil-site repository. In order for your local sandbox copy of that repository to have this same content, you must fetch those updates, which is typically done via:

cd daffodil-site
git checkout main
git fetch --prune asf 
git rebase asf/main

The most recent commit should then show the addition of new scaladoc and javadoc to the site. 

Create a new release file in the site/_releases/ directory in the Daffodil Site Repository, updating the page to include a summary of the changes and links/descriptions of the bugs that were fixed in this release. The usual procedure for gathering the tickets materials of interest is as follows:

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, that 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
   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. 

Parameters of the release file (near the top) that must be set because this is a release candidate include:

...

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

...