Incorrect version number in v1.1.0 tag

[fossell]

Describe the Problem

The version number displaying in RTD title for this build (and maybe other places) reads "v1.1.0-rc1" (e.g. here). The VERSION and RELEASE_DATE files were not updated.

Expected Behavior

Version should be updated and read "v1.1.0" in RTD for this release build and on stable build.

Environment

RTD User Guides

To Reproduce

See here.

Relevant Deadlines

Aug 1, 2023

Define the Metadata

Assignee

• [ ] Select engineer(s) or no engineer required
• [x] Select scientist(s) or no scientist required

Labels

• [x] Select component(s)
• [x] Select priority

Projects and Milestone

• [x] Select first Project for support of the current release
• [x] Select second Project for development toward the next official release
• [x] Select Milestone as the next bugfix version

Bugfix Checklist

• [x] Complete the issue definition above, including the Time Estimate and Funding Source.
• [x] Fork this repository or create a branch of main_\. Branch name: bugfix_<Issue Number>/main_<Version>_<Description>
• [x] Fix the bug and test your changes.
• [x] Add/update log messages for easier debugging.
• [x] Add/update tests.
• [x] Add/update documentation.
• [x] Push local changes to GitHub.
• [x] Submit a pull request to merge into main_\. Pull request: bugfix <Issue Number> main_<Version> <Description>
• [x] Define the pull request metadata, as permissions allow. Select: Reviewer(s) and Development issue Select: Project for support of the current release Select: Milestone as the next bugfix version
• [x] Iterate until the reviewer(s) accept and merge your changes.
• [x] Delete your fork or branch.
• [ ] Complete the steps above to fix the bug on the develop branch. Branch name: bugfix_<Issue Number>/develop_<Description> Pull request: bugfix <Issue Number> develop <Description> Select: Reviewer(s) and Development issue Select: Project for the next official release Select: Milestone as the next official version
• [x] Close this issue.

[fossell]

@georgemccabe - I missed these updates for the release. I'll put them into main and retag the release. Should the updates also go into develop for consistency?

[georgemccabe]

Ah, yes I didn't notice this. This doesn't need to go into develop because the version number was updated for future development.

[fossell]

Closed with #231