Bug 1191053

*** Bug 1191075 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 22 Change Checkpoint: Completion deadline (testable) is on 2015-02-24 [1].

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 so enabled at Change Completion deadline.

This bug should be set at least to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. Fedora 22 is going to be strictly time based release. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon. 

In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you.

[1] https://fedoraproject.org/wiki/Releases/22/Schedule

Django project still has Django-1.8 alpha 1. It was released Jan 17th.

Currently 1 single release blocker bug:
https://code.djangoproject.com/query?status=assigned&status=new&version=master&severity=Release+blocker

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.

If the following is true, I'd wait for the beta instead of pushing an alpha version.
-----------------

Subject: 	Re: status of 1.8 release blockers
Date: 	Tue, 24 Feb 2015 17:08:39 -0800 (PST)
From: 	Tim Graham <timograham>
Reply-To: 	django-developers
To: 	django-developers



Zero blockers as of this writing. If we survive the next 12 hours with
no new ones, I'll release the beta around then (famous last words).

Just built python-django-1.8-0.5.b1.fc23 in rawhide.

Proposed as a Freeze Exception for 22-alpha by Fedora user mrunge using the blocker tracking app because:

 Django-1.8 beta was released 1 day after alpha freeze.
It's now included in rawhide and should be allowed to be pushed to f22.
It is NOT build for f22

python-django-1.8-0.5.b1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/python-django-1.8-0.5.b1.fc22

Package python-django-1.8-0.5.b1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-django-1.8-0.5.b1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-2756/python-django-1.8-0.5.b1.fc22
then log in and leave karma (feedback).

Discussed at today's blocker review meeting [1].

This bug was rejected as Freeze Exception - This package doesn't come included on any release media and can be fixed with an update at a later date. No need for FE status.

http://meetbot.fedoraproject.org/fedora-blocker-review/2015-03-02/

I've written some stuff at https://fedoraproject.org/wiki/Documentation_Development_Web_Beat#Django_1.8 to cover this change. Matthias, feel free to edit or ping me if you see room for change or improvement.

python-django-1.8-0.5.b1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

(In reply to Pete Travis from comment #11)
> I've written some stuff at
> https://fedoraproject.org/wiki/Documentation_Development_Web_Beat#Django_1.8
> to cover this change. Matthias, feel free to edit or ping me if you see room
> for change or improvement.

Thank you Pete, very much appreciated!

python-django-1.8-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/python-django-1.8-1.fc22

python-django-1.8-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.