Bug 1026321

Summary:	Bodhi should inform about freeze
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	bodhi	Assignee:	Randy Barlow <randy>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	a.badger, jreznik, pahan, pfrields, tla
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-18 15:24:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Miro Hrončok 2013-11-04 12:21:58 UTC

Description of problem:
When there is any freeze that prevents the update to be pushed in stable, bodhi should inform about that.

Steps to Reproduce:
1. While there is a freeze, mark an update as stable

Actual results:
Bodhi says:
This update has been submitted for stable by $USERNAME. 

But the update is not pushed, because of the freeze. When the user doesn't know about the freeze, (s)he is confused.

Expected results:
Bodhi says:
This update has been submitted for stable by $USERNAME.
There is an ongoing freeze, this will be pushed to stable after the freeze is over. $LINK_TO_WIKI

Comment 1 Jaroslav Reznik 2013-11-04 15:14:34 UTC

Schedule exported in TJX for other teams - http://fedorapeople.org/groups/schedule/f-20/f-20-key-milestones.tjx could be used for informative message. Look for Alpha/Beta/Final Change Deadline. But I'm not sure how much this could be automatically.

Comment 2 Jaroslav Reznik 2015-03-03 15:11:05 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 3 Fedora End Of Life 2016-07-19 10:33:13 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Jan Kurik 2016-07-26 04:35:36 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 5 Randy Barlow 2016-10-18 15:24:31 UTC

Thanks for the report! I've filed this upstream for you.