Bug 570216 - Should upgrades to the pending release (aka Fedora 13) be offered?
Summary: Should upgrades to the pending release (aka Fedora 13) be offered?
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: preupgrade
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-03 16:28 UTC by James Laska
Modified: 2013-09-02 06:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-03 22:04:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
releases.txt that includes Fedora 13 (3.41 KB, text/plain)
2010-03-03 16:39 UTC, James Laska
no flags Details

Description James Laska 2010-03-03 16:28:27 UTC
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 16:39:25 UTC
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 16:39:53 UTC
Created attachment 397604 [details]
releases.txt that includes Fedora 13

Comment 3 James Laska 2010-03-03 17:55:46 UTC
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 22:04:07 UTC
I just updated releases.txt with James's version, and pushed it out.  It'll hit the web servers in the next few hours.


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