On 3/20/25 04:16, intrigeri wrote:
Hi,
4.1.0~beta5 has been in Debian for a few weeks. Looks good so far, we
merely had to cope with a few hickups related to userns and the new
"unconfined" stub profiles. Congrats for all the work that went into
this new series!
My calendar for the next steps is:
1. March 24-30: AFK
2. March 31 - April 9: last chance for me to upload a new upstream release
What are the chances that this is 4.1.0 final?
Good, while we know of a few outstanding issues, I think we have closed all
the blockers. So now its just a matter of deciding when to do a release.
In case 4.1.0 is not ready in time, could we please have a beta6 or rc1?
This would make it vastly easier for me to handle step 3 below,
and to maintain the package during the lifetime of Trixie.
I plan to cut a new beta this weekend, and do some of the tasks that have been
waiting for me to not be so swamped at work. I have one specific bug in mind
I would still like to land a fix for, and a few other that would be nice to
have but not required. We could cut an RC1 or final release next weekend.
3. Afterwards: I can only add small, targeted fixes — with increasing
overhead required to get them into the Trixie release as we
progress through freeze stages. If the 4.1 tree is maintained in
a super strict way I might be able to pull directly from it.
Otherwise I'll have to cherry-pick the most important fixes.
That would be nice. At least at first, we will keep it super strict.
Everything will have a bug/issue etc. The policy side is where it gets ugly.
That is part of why I would like to split policy from the rest of the
userspace for the next release.
Cheers,
