Skip to content

Release notes#485

Draft
jholveck wants to merge 1 commit intoBoboTiG:mainfrom
jholveck:release-notes
Draft

Release notes#485
jholveck wants to merge 1 commit intoBoboTiG:mainfrom
jholveck:release-notes

Conversation

@jholveck
Copy link
Contributor

@jholveck jholveck commented Mar 10, 2026

This is not intended to be merged as a Markdown file. It's just in that form for easier review and discussion for now. Once we've got the content settled, we can reformat this into reStructuredText for the docs.

Based on #471.

Closes #471.

This is not intended to be merged as a Markdown file.  It's just in
that form for easier review and discussion for now.  Once we've got
the content settled, we can reformat this into reStructuredText for
the docs.

Based on issue BoboTiG#471.
@BoboTiG
Copy link
Owner

BoboTiG commented Mar 10, 2026

I do not see what can be changed to make it better.

@BoboTiG
Copy link
Owner

BoboTiG commented Mar 24, 2026

It's now possible to include markdown files in the documentation, that will lower our work with such a PR.
Example: https://github.com/BoboTiG/python-mss/blob/main/docs/source/changelog.rst (and we now have the full project history in the docs: https://python-mss.readthedocs.io/latest/changelog.html)


Now, I am not sure how to present this file in the documentation, where to put it, under what name? Maybe do you have a clearer idea than me?

At the beginning I wanted to add it under "History" with the title "Next". But maybe this file should be kept for a while (even maybe forever) so it should have its own section 🤔

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Release planning

2 participants