Skip to content

contributing: Update release howto after the 8.4.2 release - #6765

Open
wenzeslaus wants to merge 7 commits into
OSGeo:mainfrom
wenzeslaus:update-release-howto-after-8.4.2
Open

wenzeslaus wants to merge 7 commits into
OSGeo:mainfrom
wenzeslaus:update-release-howto-after-8.4.2

Conversation

@wenzeslaus

Copy link
Copy Markdown
Member

Uses the version script more. Removes hardcoded messages from the guide (they need editing anyway). Improves the flow and removes duplication of steps. Adds Errata and clarifies when and how the release notes are edited.

Uses the version script more. Removes hardcoded messages from the guide (they need editing anyway). Improves the flow and removes duplication of steps. Adds Errata and clarifies when and how the release notes are edited.
@github-actions github-actions Bot added docs markdown Related to markdown, markdown files labels Dec 19, 2025
Comment thread doc/howto_release.md

```bash
python ./utils/generate_release_notes.py api releasebranch_8_4 8.3.0 $VERSION
python ./utils/generate_release_notes.py api $(git rev-parse --abbrev-ref HEAD) 8.3.0 $VERSION

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have to remember that it is probably not always relative to 8.3.0. The previous line made it clear to me when reading, the new line not as much

@neteler neteler May 22, 2026 •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any chance to retrieve the previous version automagically?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This issue of a hardcoded version is still open: is there a way to retrieve the previous version automagically?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

git tag --sort=v:refname --list "[0-9].[0-9].[0-9]$*" | tail -n 2

echoix
echoix previously approved these changes Dec 19, 2025
@echoix echoix added the conflicts/needs rebase Rebase to or merge with the latest base branch is needed label Dec 23, 2025
@echoix echoix removed the conflicts/needs rebase Rebase to or merge with the latest base branch is needed label Dec 23, 2025
@echoix

echoix commented May 10, 2026

Copy link
Copy Markdown
Member

Should this have been merged before even doing the 8.5 release?

@echoix
echoix requested review from neteler and nilason May 10, 2026 21:26
@echoix

echoix commented Sep 17, 2026

Copy link
Copy Markdown
Member

Pinging @neteler, was there missing something you think?

@neteler

neteler commented Sep 17, 2026

Copy link
Copy Markdown
Member

Pinging @neteler, was there missing something you think?

Yes, see above for "hardcoded version".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs markdown Related to markdown, markdown files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants