Bug 816167 - Alert about pre-release status still present in F17 Final TC1
Summary: Alert about pre-release status still present in F17 Final TC1
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: distribution
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Bill Nottingham
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: F17Blocker, F17FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2012-04-25 11:59 UTC by Martin Krizek
Modified: 2014-03-17 03:30 UTC (History)
7 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2012-04-26 19:25:05 UTC


Attachments (Terms of Use)

Description Martin Krizek 2012-04-25 11:59:44 UTC
Description of problem:
When installing F17 Final TC1 (tried DVD x86_64 and Live KDE x86_64), the alert dialog about pre-release is still present.

Version-Release number of selected component (if applicable):
17.22

How reproducible:
Always

Steps to Reproduce:
1. Run anaconda installer
2. Select language
3. Select keyboard
  
Actual results:
Alert dialog about pre-release is present

Expected results:
Alert dialog about pre-release is not present

Additional info:

Comment 1 Martin Krizek 2012-04-25 12:00:46 UTC
Proposing as F17 Final Blocker per criterion: "No notices or alerts about pre-release status should be present"

Comment 2 Chris Lumens 2012-04-25 13:47:14 UTC
anaconda is no longer in charge of this setting.  It's entirely based upon a pungi command line option, so they just need to make sure to add the right flag when composing the tree.

Comment 3 Tim Flink 2012-04-26 17:27:40 UTC
I thought that the 'beta' flag wasn't changed until final RC1

Either way, +1 blocker

Comment 4 Dennis Gilmore 2012-04-26 19:25:05 UTC
closing not a bug, we only flip the switch for RCs a TC is never to be considered as the final release and as such is a pre-release and the betanag is appropriate.

RC1 for final will not have the betanag.


Note You need to log in before you can comment on or make changes to this bug.