Bug 570216

Summary: Should upgrades to the pending release (aka Fedora 13) be offered?
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: preupgradeAssignee: Richard Hughes <richard>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dcantrell, jturner, matt_domsch, richard
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-03 17:04:07 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
releases.txt that includes Fedora 13 none

Description James Laska 2010-03-03 11:28:27 EST
Description of problem:

Preupgrade allows the user to specify updating their system to Rawhide.  Given that Rawhide now refers to the next development release (e.g. Fedora 14) [1] [2], should preupgrade also offer the ability to update to the current pending release (e.g. Fedora 13)?

[1] https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal
[2] https://fedoraproject.org/wiki/No_Frozen_Rawhide_Implementation

Version-Release number of selected component (if applicable):
 * preupgrade-1.1.4-1.fc12
Comment 1 James Laska 2010-03-03 11:39:25 EST
Perhaps this issue is more appropriate for whomever maintains the http://mirrors.fedoraproject.org/releases.txt file.

When using a local releases.txt file (see attachment), I'm able to have the pending Fedora 13 release available for preupgrade users.
Comment 2 James Laska 2010-03-03 11:39:53 EST
Created attachment 397604 [details]
releases.txt that includes Fedora 13
Comment 3 James Laska 2010-03-03 12:55:46 EST
I believe Matt Domsch from Fedora Infrastructure may manage the releases.txt file, adding to the cc list.
Comment 4 Matt Domsch 2010-03-03 17:04:07 EST
I just updated releases.txt with James's version, and pushed it out.  It'll hit the web servers in the next few hours.