Release v6.0.0

[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)
    • [ ] 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

[dondi]

General breakdown:

• final version testing—everyone
• tagging issues for next release—everyone
• client-side testing document—looks like changes are there, but some typos and can use one more round of review @ahmad00m @Onariaginosa
• tagging, GitHub, npm, external links— @dondi
• documentation— @Onariaginosa
• website updates— @Sarronnn

[ahmad00m]

I double checked the client-side testing document and it seems that all the new features has already been added (which mainly includes the Network sidebar and dropdown menu) that was done by @Onariaginosa at the end of last semester.

[Onariaginosa]

I redid the documentation, I didn't want to check it off the list yet, because I think that it should be heavily reviewed. There are many changes and I'm suspicious.

[dondi]

All issue items completed!