release: v11.2.0#2790
Conversation
I introduced the "Keep a Changelog"-format which helps me in **not** spending this much time on changelogs in the future. There is a another PR that will update the documentation before v11.2.0 is released, which focuses on adding the entry to the changelog before merging a relevant PR. Releasing is always a huge efforts when I get the changelog and adjus it. This is incceptable and needs to change. This is the solution.
wernerfred
left a comment
There was a problem hiding this comment.
I like it! Writing the release information was always a manual nightmare.
Just curious: what speaks against taking the release notes that github can autogenerate for the changelog? It is not that structured but i like the fact that every change is included (even if very small) and every change is linked to its PR.
Indeed 🙏🏼
Nothing really, but I like the way that "Keep a Changelog" structures the information. I decided against just copying, because
|
|
NICE UPDATE: Take a look at the latest manual run I started: https://github.com/docker-mailserver/docker-mailserver/actions/runs/3100146489 Image build time is 1:15 min :D Nice! Caches and generic workflows seem to work! 🙌🏼 |
|
@casperklein feel free to bring up your PR about the F2B/Dovecot packages - no time pressure with this release. |
|
@casperklein do you want to merge #2808 before we do the freeze & release this? |
|
Alright, feature-freeze is in-place. |
Neither on mine :D |
Description
I know, this is a release PR, but:
I introduced the "Keep a Changelog"-format which helps me in not spending this much time on changelogs in the future. There is a another PR (#2789) that will update the documentation before v11.2.0 is released, which focuses on adding the entry to the changelog before merging a relevant PR.
Releasing is always a huge efforts when I am writing the changelog because of the many manual adjustments. This is unacceptable and needs to change. The format change is the solution I think.
I already prepared a draft for v11.2.0, have a look :D
Currently waiting on:
Feature freeze is now in place until 12 Oct 2022.
Type of change
Checklist:
docs/)