The 12.1-RELEASE process has begun . This is a tracking bug for coodinating resolution of 12.1-RELEASE blockers.
Bugzilla issues that are (or should be) potential release blockers, should:
- Add their issue ID's to their "Blocks:" field
- Set patches (attachments) maintainer-approval flags to request (?) approval from email@example.com
re@ can then accept (+), or not-accept (-) approval according to their policies/guidelines, and leave/remove the issue from this bugs "Depends on" field, respectively.
this is one of the bugs I encountered on FreeBSD 12.1-BETA1:
(In reply to vermaden from comment #1)
This is a meta bug for listing issues that block the 12.1-RELEASE pending approval (or not) of patches that resolve the issues. A requirement for listing here is that the issue has been been isolated, and with at least a patch proposed, if not committed to head already
Add bug 240729 to this bugs "Depends On" field if and when it has occured
Another 'blocker' for 12.1-RELEASE:
Another one to the list:
I do not believe 240478 should be tagged as a release blocker - the issue is not a regression, and Glen's workaround in base r353004 should mask the issue.
(In reply to Ed Maste from comment #5)
You're correct, it is not a blocker. It was intended as an MFC reminder. (Note, I had no intention of closing 240478 after the MFC.)
Shouldn't this one be also fixed before RELEASE?
(In reply to vermaden from comment #7)
To keep this issue clean, discussions as to whether particular issues should or should not be release blockers should take place in those issues, rather than here.
If issues are already committed/merged and closed, they may be re-opened to let the resolver (committer) know they should to add that issue as a blocker, if warranted.