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

Amend RELEASING.md #2615

Merged
merged 1 commit into from
Jan 15, 2024
Merged

Amend RELEASING.md #2615

merged 1 commit into from
Jan 15, 2024

Conversation

DigitalBrains1
Copy link
Member

Add Mergify instructions and improve the instructions for writing CHANGELOG.md.

Still TODO:

  • Write a changelog entry (see changelog/README.md)
  • Check copyright notices are up to date in edited files

Add Mergify instructions and improve the instructions for writing
`CHANGELOG.md`.
@DigitalBrains1
Copy link
Member Author

Erm, I think when you look at development process documentation in a git repo, you look at master. If we say you can also look in stable branches, we'd have to backport it to every stable branch we might conceivably ever do another release for, every time. Ideally, the stable branches wouldn't even have the file to begin with, but I think that's a bit more trouble than it's worth.

So I'd rather not backport this so as not to create false hopes that somehow outdated development process documentation is still valid.

@martijnbastiaan
Copy link
Member

Fair enough!

@DigitalBrains1 DigitalBrains1 merged commit e1feb20 into master Jan 15, 2024
@DigitalBrains1 DigitalBrains1 deleted the amend-instructions branch January 15, 2024 08:58
hiddemoll pushed a commit that referenced this pull request Feb 1, 2024
Add Mergify instructions and improve the instructions for writing
`CHANGELOG.md`.
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.

2 participants