Release v6.0.4 to production

[dondi]

• [x] In the days leading up to the release, all open issues that need to be resolved before the release will be given the label "for next release".
• [x] Any new or changed client-side features need to be documented on the Client Side Testing Document page.
  • [x] the feature JSON files file should be updated
  • [x] the new feature also needs to be added to the Pull Request Checklist
• [x] Test the candidate build (typically the beta branch)
• [x] Merge the branch(es) under development (typically beta) into master
  • [x] Resolve any version control conflicts
  • [x] Test the final merged version
  • [x] Perform hotfixes on master as needed
• [x] Update README.md at top-level directory of master branch, if necessary
  • [x] Update Travis and Coveralls badges to reference the master branch
• [x] Tag the final, tested version as v#.#.# (all three numbers are required, even if 0; see npm step below)
  • [x] Update version numbers in package.json
  • [x] Remember that the tag needs to be pushed to GitHub: git push origin <tag-name>
• [x] Create draft release item on Github repository (name it exactly like the tag)
  • [x] Make release notes: a list of new features/bug fixes with issue numbers covered by this release. Note that this at least will be the ones labeled "for next release", with possible others.
• [x] Publish GitHub release item
• [x] Publish release to GRNsight home page
  • [x] Refresh (pull) the master clone on grnsight.cs.lmu.edu
  • [x] Update the version number and modification date on gh-pages
  • [x] Update the About page with release notes (GitHub release item without issue numbers)
    • [x] Update the browser version compatibility statement with the latest version of Chrome and Firefox for which the new GRNsight version has been tested.
    • [x] Update modification date
  • [x] Add news item about the release to the News page
    • [x] Update modification date
    • [x] Link news item to the corresponding release notes in the About page
  • [x] Update Documentation page with any new features or updates to old features
• [x] Increment beta version
  • [x] Merge released master with beta, especially if hotfixes/merges were made on master
  • [x] Update version number and modified date on gh-pages
  • [x] Update Travis and Coveralls badges to reference the beta branch
  • [x] Refresh (pull) the beta clone on grnsight.cs.lmu.edu
• [x] Publish to npm (npm publish)
  • [x] npm requires all .0s in the semantic version
• [x] Update version number/other relevant information at current bioinformatics listing sites
  • [x] Elixir
    • [x] Then change hyperlink on the GRNsight Links page, if necessary
• [x] Get DOI for new release from Zenodo
  • [x] Verify that the badge in README.md at top level of repo is correct (it might be necessary to invoke curl -X PURGE https://camo.githubusercontent.com/camo-GitHub-id in order to update the badge image)
  • [x] Verify that CITATION.md file DOI links to the new release, updating if necessary
  • [x] Verify that "How to cite GRNsight" section on About page links to the new release, updating if necessary

[kdahlquist]

We went through the checklist and verified that unchecked items have not been completed.

[dondi]

• @Onariaginosa to take point on release notes and new export features
• @Sarronnn to take point on client-side testing (focus on export section)
• @ntran18 and @ahmad00m to take point on documentation items (most likely after release notes are out)

[kdahlquist]

@Sarronnn needs to know how to generate and post the client-side testing document. Look in the GRNsight archive repository. The first line of the code should say how to run it. https://github.com/dondi/GRNsight-archive/blob/main/documents/developer_documents/testing_script_generator/GRNsightTestingDocument.md

[ahmad00m]

Updated documentation based on the latest release notes.

[Sarronnn]

Generated and posted the client-side testing document: https://github.com/dondi/GRNsight-archive/blob/main/documents/developer_documents/testing_script_generator/GRNsightTestingDocument.pdf

[kdahlquist]

@Sarronnn is going to finish the feature JSON and pull request checklist. @ahmad00m is going to finish the About and News webpages.

[ahmad00m]

@ahmad00m has updated the about page with release notes and finished the news items in the news page. Also, I checked the compatibility of GRNsight on Safari v16.2 and Chrome v109.0.5414.119 and it doesn't seem to have any issues. Though I have not yet updated compatibility notes on about page so others can check for it as well.

[Sarronnn]

• The feature JSON file has been updated
• The new feature is in the Pull Request Checklist
• Client-side features have been documented on the Client Side Testing Document page.

[dondi]

@Sarronnn can you please double-check that the updates are complete? We found the following items actually missing still, and there may be more:

• Load from database
• Export to image

[Sarronnn]

Do you mean updates to the Client Side Testing Document?

[dondi]

@Sarronnn the JSON object is the source that generates that document—it is the link above for the text “feature JSON files.” It looks like you did edit exportFeatures.json, so we just need for you to confirm that all of the JSON files have been reviewed and updated if needed

The pull request checklist was last updated in January 2022, so this one most likely will also need updates for the new features of 6.0.4

[Sarronnn]

Ona walked Maika and I through the whole process, so the JSON files are now up to date.

[kdahlquist]

Closing.