April 2024 stabilization week

[Gleb Smirnoff]

Hi FreeBSD/main users & developers:

This is an automated email to inform you that the April 2024 stabilization week
started with FreeBSD/main at main-n269602-dd03eafacba9, which was tagged as
main-stabweek-2024-Apr.

The tag main-stabweek-2024-Apr has been published at
https://github.com/glebius/FreeBSD/tags. Those who want to participate
in the stabilization week are encouraged to update to the above
revision/tag and test their systems.

Developers are encouraged to avoid pushing new features to FreeBSD/main,
but focus on bugfixes instead. The stabilization week runs up to
Friday 18:00 UTC, but if there is consensus that any regressions
discovered by participants have been fixed, it will end early.

Once that happens, the advisory freeze of FreeBSD/main branch is thawed.

--
Gleb Smirnoff


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Gleb Smirnoff]

Hi FreeBSD/main users & developers,

On Mon, Apr 22, 2024 at 01:00:50AM -0700, Gleb Smirnoff wrote:
T> This is an automated email to inform you that the April 2024 stabilization week
T> started with FreeBSD/main at main-n269602-dd03eafacba9, which was tagged as
T> main-stabweek-2024-Apr.
T>
T> The tag main-stabweek-2024-Apr has been published at
T> https://github.com/glebius/FreeBSD/tags. Those who want to participate
T> in the stabilization week are encouraged to update to the above
T> revision/tag and test their systems.

* Netflix testing didn't discover any stability issues with
main-n269602-dd03eafacba9. We are still running the performance test,
but preliminary results are that everything is fine.
* My personal desktop/server experience with the tag neither has any problems.

Feel free to reply with your reports if you participated in the testing, too.

In bugzilla we have this submission, which looks important:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278494

I want to hear from Alexander and Martin before thawing the advisory freeze.
Don't want to declare the tag good if some ZFS systems fail to boot after
upgrade.

[Gleb Smirnoff]

Hi FreeBSD/main users & developers,

this stabilization week [likely final] status update:

* Netflix testing didn't discover any stability issues with
main-n269602-dd03eafacba9.
* Netflix testing didn't discover any substantial performance
degradations. The data is still being analyzed though.
* A regression with ZFS reported in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278494
has been addressed by ZFS 9f83eec03904b18e052fbe2c66542bd47254cf57.
* An old (more than a month old) regression has been identified
with accept_filter(9).
Fixed by a8acc2bf5699556946dda2a37589d3c3bd9762c6.

Since FreeBSD/main has been pushed with several non-documentation, non-a-
trivial-bugfix commits during the days of the stabilization week, I can't
guarantee that the above testing results are applicable to the current state of
FreeBSD/main. That's why I created a temporary cherry-picking branch
stabweek-2024-Apr that is published at https://github.com/glebius/FreeBSD.git.

Users of FreeBSD/main are adviced with the following choices:

- Pull up FreeBSD/main up to a8acc2bf5699556946dda2a37589d3c3bd9762c6 and use it
as your stabilization point. There is tiny risk of untested changes added
recently.
- Pull stabweek-2024-Apr from https://github.com/glebius/FreeBSD.git.
- Craft stabweek-2024-Apr yourself:
# git checkout -b stabweek-2024-Apr dd03eafacba962c9dcec929c3ed9d63e7c43da3a
# git cherry-pick -x --strategy=subtree -Xsubtree=sys/contrib/openzfs 9f83eec03904b18e052fbe2c66542bd47254cf57
# git cherry-pick -x a8acc2bf5699556946dda2a37589d3c3bd9762c6

I'm planning to end the advisory freeze on the main branch Wednesday morning
at 8:00 UTC, unless somebody opposes that with a valid reason, e.g. a
regression that I missed.