Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Patch release r1.3 #383

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

hdamker
Copy link
Collaborator

@hdamker hdamker commented Dec 10, 2024

What type of PR is this?

  • subproject management
  • documentation

What this PR does / why we need it:

Update of README and changelog for patch release r1.3
Updating release numbers and API versions across all files
Replacing links to main branch with release specific links (closing the remaining issue from the patch release scope in #

Which issue(s) this PR fixes:

Fixes #381
Fixes #363

Special notes for reviewers:

Create temporarily created branch r1.3 from main to be able to test the links. That branch will need be deleted before the release tag can be created.

Changelog input

na

@hdamker hdamker added documentation Improvements or additions to documentation subproject management labels Dec 10, 2024
@hdamker
Copy link
Collaborator Author

hdamker commented Dec 10, 2024

@RandyLevensalor @eric-murray @jlurien could you have a view on this PR ... I suppose that we are ready for the patch release, but would be great to double-check the CHANGELOG etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation subproject management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create release PR for r1.3 (patch release) Local links within API documentation have to be release specific
1 participant