This is a list of Changes at risk for Fedora 22 as the deadline is later today (2015-02-24).
Placeholder for now to add it to the meeting agenda, I'm working with last few Change owners on status updates for Wednesday meeting.
http://bit.ly/f22-not-ready and expected state is MODIFIED or commented status in BZ.
So far known statutes of Changes still not in testable state:
1181557 Preupgrade Assistant * waiting for package review
1191053 Django18 * waiting for final upstream release
1194577 Python 3 Migration Improvements * it turns out that policycoreutils-python3 exists, but doesn't work - https://bugzilla.redhat.com/show_bug.cgi?id=1195139#c1 - (not fully, anyway). That means that we won't be able to achieve python2-free minimal cloud image or atomic host and the change has to be reverted. I'll make sure we only have Python 2 on both atomic host and in minimal cloud image and note in this image when I've reverted everything properly. Packages that are not in atomic host and minimal cloud image still can freely port for F22, but the rest should only port for F23.
Replying to [comment:1 jreznik]:
https://fedoraproject.org/wiki/Changes/Django18 says that is expected at the start of April; so ''nothing'' will land before either of the Change checkpoints?
Ah, https://bugzilla.redhat.com/show_bug.cgi?id=1191053#c4 :
After discussing this on irc, I will push the latest alpha to rawhide on Feb. 25th. If possible, I'll do the same for f22 branch.
After discussing this on irc, I will push the latest alpha to rawhide on Feb. 25th.
If possible, I'll do the same for f22 branch.
Right, I spoke with the Change owner earlier today about this. He was expecting the Django 1.8 Beta to be released last week (as it was scheduled to). The original plan was to land that for Fedora Alpha, but since it didn't make it in time, I convinced him to land the Alpha or a git snapshot soon so that dependent packages will have time to adapt throughout the Fedora Beta process.
I had a quick look at the Preupgrade Assistant review request today, and there's a modest amount of packaging work required. No reason to get it done in a few hours between with a dedicated reviewer. OTOH, the software itself seems to require a lot of work, at least to finish all features.
1184894 Wine to use mesa Direct3D * no update/reply from Change owner
1191525 Vagrant Box for Fedora Atomic and Fedora Cloud * to be consolidated with Atomic Host change
1191543 Minglish - New input method for Marathi Language * waiting for upstream acceptance but could be patched directly in Fedora; waiting for time estimate
1194589 Atomic Host * blocked on https://bugzilla.redhat.com/show_bug.cgi?id=1195761
Replying to [comment:2 mitr]:
Replying to [comment:1 jreznik]: 1191053 Django18 * waiting for final upstream release https://fedoraproject.org/wiki/Changes/Django18 says that is expected at the start of April; so ''nothing'' will land before either of the Change checkpoints?
Based on communication in bug, there's possibility Beta will be released soon and it will be packaged this week. Otherwise, Alpha will be packaged.
Replying to [comment:7 jreznik]:
m17n-db-1.7.0-2.fc22 has been submitted as an update for Fedora 22
Reopening as Change Checkpoint: 100% Code Complete Deadline is today for 2015-04-01 FESCo meeting. I'm working on the last few status updates, we're looking good so far. I'll update it later today/early tomorrow.
1194589 Atomic Host & 1194590 RpmOstree - Server side composes and atomic upgrades * blocked on https://fedorahosted.org/rel-eng/ticket/6119
Agreed on today’s FESCo meeting
1) Ask Change owners to revisit the contingency plans and clarify 2) Don’t enact contingency plans today 3) Revisit next week, invite QA for an opinion on hard deadline
(1) refers primarily to https://fedoraproject.org/wiki/Changes/AtomicHost#Contingency_Plan:
some upgrade mechanism for Fedora 21 Atomic Cloud Image users would need to be evaluated )
We decided that it is done during the FESCo meeting.
Login to comment on this ticket.