This is a dynamic query to Bugzilla showing all tracking bugs for Changes not at least in ON_QA state expressing the 100% completeness.
I already contacted all the Change owners on the list above requesting a status update. I am going to provide a static query to Bugzilla with all the Changes not 100% implemented just before the FESCo meeting on 2018-Mar-09.
1534532 nmavrogi@redhat.com MODIFIED Strong crypto settings 1537246 pbrezina@redhat.com MODIFIED Make authselect default tool instead of authconfig 1537249 rharwood@redhat.com MODIFIED Kerberos in Python modernization 1537261 besser82@fedoraproject.org MODIFIED Replace glibc's libcrypt with libxcrypt 1534594 ckellner@redhat.com MODIFIED Thunderbolt Enablement 1537245 jkonecny@redhat.com MODIFIED Anaconda modularization
I think all of those are now partially implemented, and there is no big problem if they are not fully implemented. I think we should encourage Change Owners to wrap the changes up during beta freeze.
1547235 ksinny@gmail.com ASSIGNED Atomic, Cloud and Container images for s390x 1537253 sgallagh@redhat.com ASSIGNED Add-On Modularity
Those two are a bit problematic, but stuff is happening. More information would be great.
1520901 lemenkov@gmail.com MODIFIED Erlang 20 1534542 mrunge@redhat.com MODIFIED Django 2.0
Those two are problematic — unless the Change is fully implemented, we'll end up with uninstallable packages.
Of the two, I'm more worried about erlang, because there are build failures, and in important packages like couchdb and wings.
With django, various packages are being retired, so we just need some time for maintainers to respond, or updated, which mostly doesn't look too complicated.
Both erlang and django are "leaf" packages, so I think it's OK if they are updated a bit later in the cycle.
I'll invite the two Change Owners to the FESCo meeting.
I wouldn't consider Erlang or Django to be leaf packages. Erlang in particular is tricky because it has arch-dependent dependencies (i.e., things link against it). The tiny bit of the Erlang stack I maintain has been built against Erlang 20 and seems to be working, but I'm not familiar with the status of the rest of the stack (couchdb/wings, as you mentioned).
@peter can you comment on the status of Erlang 20?
"leaf" in the sense that the rest of the distro doesn't depend that much on them. But as a group, they are of course connected.
I wouldn't consider Erlang or Django to be leaf packages. Erlang in particular is tricky because it has arch-dependent dependencies (i.e., things link against it). The tiny bit of the Erlang stack I maintain has been built against Erlang 20 and seems to be working, but I'm not familiar with the status of the rest of the stack (couchdb/wings, as you mentioned). @peter can you comment on the status of Erlang 20?
I consider Erlang 20 as in "ON_QA" state. Except CouchDB which has a very time-sensitive test (which triggers build error very easy) and erlang-hyper, everything else is installable. I'll rebuild these two soon.
Wings is blocked by erlang-cl which was rebuilt recently and available in updates-testing already.
On 03/08/2018 10:34 AM, Zbigniew Jędrzejewski-Szmek wrote:
Fair.
From bugzilla.redhat.com/1534542 : there are 7 non-closed bugs blocking this change: 3 of them require package updates:
One is in ON_QA,
3 packages should be retired
Those packages are dead upstream, and haven't been touched for years. Besides the package in ON_QA, I'd even argue, all of them should be retired.
Miro Hrončok sent heads-up/reminders to package owners on Jan 16, Feb 20, and on Mar 02.
If FESCO decides to drop the packages, I'd go ahead and retire them.
Here is the static list of F28 Change proposals not marked as 100% completed:
Django 2.0
Make authselect default tool instead of authconfig
Kerberos in Python modernization
Add-On Modularity
Replace glibc's libcrypt with libxcrypt
Atomic, Cloud and Container images for s390x
I don't know why people keep not responding... but libcrypt → libxcrypt change is done. And authselect thing is done too.
@ignatenkobrain I think that literally means "hasn't responded on Bugzilla", which is different from not responding.
Regarding Add-On Modularity, it's a bit of a scramble. We didn't have the necessary bits from rel-eng until last week, which means we couldn't tell where what needed to be fixed until this week. A lot of people on a lot of teams are putting a lot of effort into landing this as soon as possible. A lot of stuff has come together this week, so I think we're "yellow bordering on green" for being ready for the scheduled Beta release at this point. If trouble comes up, we may consider petitioning FESCo to permit us one extra week (invoking the Beta "rain date") to finish, but right now we don't anticipate this.
AGREED: Django packages which are incompatible with Django2.0 will be retired after one more week (+5, 0, 0) AGREED: Wait another week for changes not in ON_QA status (+6, 0, -0)
EDIT: Actually it was +6 on both, one vote came in after my tally
AGREED: Django packages which are incompatible with Django2.0 will be retired after one more week
This is awesome news. Sorry for not being at the meeting, I'm on my way from PyCon SK and this is first time I check e-mail since ~Wednesday.
Sorry for not being at the meeting
There was no need.
Can you retire the packages that need retiring, next Friday?
Will do.
Updated list for the FESCo meeting on 2018-Mar-16:
These last four items were discussed in today's FESCo meeting.
Kerberos in Python modernization: AGREED: (+1:6,+0:0,-1:0) - ask change owner to update change with what will be shipped in f28 and file any later changes in an F29 change request
Add-On Modularity: AGREED: The critieria posted in comments 6 and 7 at https://bugzilla.redhat.com/show_bug.cgi?id=1537253 are required for modularity (+8, 0, -0) @sgallagh will inform the QA team
glibc libcrypt -> libxcrypt: Appears to be mostly done.
Atomic, Cloud and Container images for s390X: ACCEPTED: we let nirik work some koji magic to try get the cloud images done, by next week we ask that ksinny has updated the change to reflect reality and punt the rest to f29 (+8, 0, -0)
Metadata Update from @jsmith: - Issue untagged with: meeting - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Let's keep this open so we remember to check if all actions have been taken.
Metadata Update from @zbyszek: - Issue status updated to: Open (was: Closed) - Issue tagged with: meeting
@bowlofeggs posted to the QA list to ask what they thought about the ppp FTBFS.
This was discussed in the last meeting (2018-03-23):
Kerberos in Python modernization: https://meetbot.fedoraproject.org/sresults/fesco.2018-03-23-15.00.log.html#l-32 https://fedoraproject.org/wiki/Changes/kerberos-in-python-modernization (tyll, 15:04:02) https://bugzilla.redhat.com/show_bug.cgi?id=1537249 (tyll, 15:04:05) ACTION: zbyszek to reach out to the change owner (zbyszek, 15:05:15) nothing happened since last meeting, will discuss it again next meeting (tyll, 15:05:53)
Add-On Modularity: nothing to discuss
Replace glibc's libcrypt with libxcrypt https://meetbot-raw.fedoraproject.org/teams/fesco/fesco.2018-03-23-15.00.log.html#l-74 ACTION: bowlofeggs will notify QA that ppp might be a beta blocker (tyll, 15:49:53) ACTION: bowlofeggs will notify QA about https://bugzilla.redhat.com/show_bug.cgi?id=1556132 (bowlofeggs, 15:49:54) ACTION: msekleta will test pppoe with a VM setup (tyll, 15:50:08) AGREED: make it a final blocker and everyone will try to test it to see if it breaks PPPoE/3g devices (+7, 0, -0) (tyll, 15:54:03) ACTION: bowlofeggs will mark it as a final blocker (bowlofeggs, 15:57:35)
Atomic, Cloud and Container images for s390x change can be tested now
Kerberos in Python modernization:
Change owner summarized current status in https://fedoraproject.org/w/index.php?title=Changes%2Fkerberos-in-python-modernization&type=revision&diff=514015&oldid=511996. The Change is not complete, but it's in progress, and there is no breakage, everything looks good.
Add-On Modularity:
Moving along.
ppp was ported and tested and all issues are solved.
python35 is being worked on, patches have been posted (https://src.fedoraproject.org/rpms/python35/pull-request/2).
Mostly done, afaict.
FESCo Meeting (2018-04-06):
FESCo is satisfied with the current state of the Changes
Metadata Update from @sgallagh: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.