release: version v10.5.0

[georglauterbach]

Description

This PR marks the feature freeze phase for the v10.5.0 release.

The current :edge image will be tested for roughly one week and if no bugs get reported, v10.5.0 will be released. During this testing period, only PRs that do not change functionality will be merged.

If you want to support us, give the latest :edge image a try and report any issues you encounter back to this PR.

Documentation updates may be merged. Feature freeze is in place until 01 March 2022.

(Previously) Blocking:

• PERMIT_DOCKER=none as new default value #2424
• Adjust envrionment variables - more sensible defaults #2428

Until it is decided whether they go into this release or not, 10.5.0's feature free is not in place.

EDIT: I seems as if a decision was reached. #2424 and #2428 are breaking changes and require a major version bump.

Type of change

• Release

Release-Checklist:

• Update CHANGELOG.md
• Update version in VERSION
• Draft release

[wernerfred]

Thanks for Putting together all PRs 🚀
For Future us: We could think of Auto-generating the Changelog / Release content through CI

[casperklein]

If you want to support us, give the latest :edge image a try and report any issues you encounter back to this PR.

No problems in my setup 👍

I thought about, how to get more people testing the edge image. There seems to be no way to pin PRs like issues. Maybe next time, we open/pin also a an issue about the upcoming release?

[georglauterbach]

I thought about, how to get more people testing the edge image. There seems to be no way to pin PRs like issues. Maybe next time, we open/pin also a an issue about the upcoming release?

We could, as an alternative, open a discussion (type: announcement). Maybe this is more fitting.

[georglauterbach]

What say ye @docker-mailserver/maintainers? :D

[NorseGaud]

I see nothing that would cause me to reject it :)

[georglauterbach]

Release was scheduled for today, but this PR lacks approval. Currently, changes requested by @wernerfred are blocking and @polarathene has not approved either. There is no rush, just wanted to let you know.

[wernerfred]

Sorry. I didn't approve in a first place as I hadn't time to test edge. Didn't notice that the change request is still blocking after it got adressed. Hope this "Reviewal Comment" will superseed the Change Request.

EDIT: Seems like a comment will only be added to the reviews, not replace a previous one. I'll find a way to remove the blocker
EDIT: It worked 👍🏻

Dismiss as requested change was implemented

[polarathene]

@polarathene has not approved either

I still don't actually run this project, only contribute/maintain 😅

I can approve but I've not done any testing on my end.

[georglauterbach]

@polarathene has not approved either

I still don't actually run this project, only contribute/maintain sweat_smile

I can approve but I've not done any testing on my end.

While this is true, there is no hard requirement that forces you to use :edge to approve this PR. Otherwise I assume there is a very valid reason for not approving this PR so I will not merge it :)