This is a tracking bug for Change: Kerberos in Python modernization
For more details, see: https://fedoraproject.org/wiki/Changes/kerberos-in-python-modernization
Replace usage of python-krbV and pykerberos with python-gssapi in all Fedora packages to enable their removal from Fedora. rharwood will author all necessary code changes; no new code from maintainers is required.
On 2018-Feb-20, we have reached the Fedora 28 Change Checkpoint: Completion deadline (testable).
At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be enabled at Change Completion deadline as well.
Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.
Incomplete and non testable Changes will be reported to FESCo for 2018-Feb-23 meeting.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.
Uh... per https://fedoraproject.org/wiki/Changes/Policy#Change_Checkpoint:_100.25_code_complete_deadline and https://fedoraproject.org/wiki/Releases/28/Schedule I thought I had until March 6 for this?
Today the Change should be in "Testable" state, which means the coding should be ready for a testing. However there is a time till March 6th, when the Change proposal should be "100% completed", which means the code is not only testable, but it is fully completed.
I guess MODIFIED means testable here?
On 2018-Mar-08 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 28 release. At this point all the Changes not at least in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review.
Alright, well: it's not complete. It's fine to ship incomplete, as per my original proposal. I'll keep working on it, of course.
This was discussed in FESCo meeting on 2018-03-16:
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
Can you update the Change page to reflect what was done in F28?
Updated. Please let me know if you need anything else.