Stratis 3.2.0 includes one significant enhancement, one bug fix, and a number of more minor improvements.
Owners, do not implement this work until the FESCo vote has explicitly ended. The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed. See the FESCo ticket policy and the Changes policy for more information.
Perhaps I am missing something critical here, but isn't stratisd 3.1.0 already in Fedora? I see 3.1.0 all the way back in Fedora 35.
I only see builds of it in Fedora RPMs (as opposed to modules) since May.
https://koji.fedoraproject.org/koji/packageinfo?packageID=26124
Looks like they backported it to F35+ as well, which is what has you confused, I think.
(I also wish they had held off until the Change was approved, but we can't reverse time).
+1 for the Change
When Stratis creates a release, packaging for Fedora starts and the creation of a Fedora change request is initiated using the release notes and blogs provided for the release. So, the process for Stratis will be updated to provide change request earlier and allow time for voting before packaging is started, my apologizes.
+1 regardless
So, the process for Stratis will be updated to provide change request earlier and allow time for voting before packaging is started, my apologizes.
This will be much appreciated.
+1
Thanks for the explanation!
The Change owners have submitted a Stratis 3.2.0 proposal that supersedes this one. Since this is a leaf package and the differences between 3.1 and 3.2 do not seem significant to our process, I will restart the clock on this vote for the updated proposal instead of starting the whole process over. If any FESCo member objects to this, we can re-start with the announcement step (note that the 3.1 announcement received zero replies).
I have already shared this update on the devel list.
Metadata Update from @dkeefe: - Assignee reset
APPROVED (+8, 0, 0)
Metadata Update from @zbyszek: - Issue tagged with: pending announcement
Announced.
Metadata Update from @kevin: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.