Update release.md

[mavaylon1]

Motivation

What was the reasoning behind this change? Please explain the changes briefly.
Remove a duplicate bullet point.

How to test the behavior?

Show how to reproduce the new behavior (can be a bug fix or a new feature)

Checklist

• Did you update CHANGELOG.md with your changes?
• Does the PR clearly describe the problem and the solution?
• Have you reviewed our Contributing Guide?
• Does the PR use "Fix #XXX" notation to tell GitHub to close the relevant issue numbered XXX when the PR is merged?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.53%. Comparing base (0998190) to head (b7e0316).
Report is 58 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev    #1059   +/-   ##
=======================================
  Coverage   88.53%   88.53%           
=======================================
  Files          45       45           
  Lines        9605     9605           
  Branches     2732     2732           
=======================================
  Hits         8504     8504           
  Misses        778      778           
  Partials      323      323           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stephprince]

There's nothing in the README.rst other than the legal file dates that gets updated usually, right? I was wondering if that's why they were separate steps originally.

[mavaylon1]

My view is that "checking information" is the same as "Update". I think this is just an interpretation. I'll leave this as is.

[oruebel]

Originally the README contained more detailed information, e.g,. about installing HDMF, so there was more to check then just the legal dates. In general, checking the README is there to make sure it is up-to-date with any changes that have happened in the repo, since this is the first thing developers see when they come to the repo.

Case in point, currently there is a broken badge in the README that points to a non-existing GitHub workflow:

It looks like the broken badge is pointing to check_external_links.yml, which I assume has been renamed to check_sphinx_links.yml

I think taking a look at the README before a release is still a good idea, even if no actions are needed in most cases.