Updated versions, dates, rotated authorship

[bikegeek]

Pull Request Testing

• Describe testing already performed for these changes:
  

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes or No]

• Do these changes include sufficient testing updates? [Yes or No]

• Will this PR result in changes to the test suite? [Yes or No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Do these changes introduce new SonarQube findings? [Yes or No]
  
  If yes, please describe:

• Please complete this pull request review by [Fill in date].
  

Pull Request Checklist

See the METplus Workflow for details.

• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the version that will include these changes
  Select: Coordinated METplus-X.Y Support project for bugfix releases or METviewer-X.Y.Z Development project for official releases
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[jprestop]

@bikegeek For some reason, the 'develop' release notes page for METviewer has not only the betas and rc1 for 6.0.0, but also still has the release notes for 5.1.0, 5.0.1, and 5.0.0. Unfortunately, when you were consolidating the notes, issues from those old releases were included too. I'll go in and clean it up, removing the issues from those older releases since you're cutting all four Analysis repos this time. I'll continue to review and approve soon, hopefully.

[bikegeek]

sorry about that, I can clean that up right now...

…

On Wed, Dec 18, 2024 at 6:14 PM Julie Prestopnik ***@***.***> wrote: @bikegeek <https://github.com/bikegeek> For some reason, the 'develop' release notes page for METviewer has not only the betas and rc1 for 6.0.0, but also still has the release notes for 5.1.0, 5.0.1, and 5.0.0. Unfortunately, when you were consolidating the notes, issues from those old releases were included too. I'll go in and clean it up, removing the issues from those older releases since you're cutting all four Analysis repos this time. I'll continue to review and approve soon, hopefully. — Reply to this email directly, view it on GitHub <#558 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4UJHTIVQALFZ7RPI7C3J32GIMYJAVCNFSM6AAAAABT33WSGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSGU3TCOJSGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jprestop]

@bikegeek No, it's done! I just did it. It's all good.

[bikegeek]

Thanks, that is strange, I wonder why those didn't show up in my editor? Thanks for getting that done so quickly.

…

On Wed, Dec 18, 2024 at 6:20 PM Julie Prestopnik ***@***.***> wrote: @bikegeek <https://github.com/bikegeek> No, it's done! I just did it. It's all good. — Reply to this email directly, view it on GitHub <#558 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4UJHXUCYO64OSIWSWDW3D2GINO3AVCNFSM6AAAAABT33WSGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSGU3TOOBRGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jprestop]

Thanks for all of your work on this task, @bikegeek. I appreciate it. I approve this request.