What Repos should be enabled in order to track F15 up to release?

[sillav]

I installed F15 alpha and am wondering what repos should be enabled, so that if I just keep updating I'll eventually have the same system that will eventually be released as F15.

Right now I have the following setup:

[x] Fedora 15 - x86_64
[ ] Fedora 15 - x86_64 - Test Updates
[x] Fedora 15 - x86_64 - Updates
[ ] Fedora - Rawhide - Development packages for the next release

[x] RPM Fusion for Fedora 15 - Free
[ ] RPM Fusion for Fedora 15 - Free - Test Updates
[x] RPM Fusion for Fedora 15 - Free - Updates
[x] RPM Fusion for Fedora 15 - Nonfree
[ ] RPM Fusion for Fedora 15 - Nonfree - Test Updates
[x] RPM Fusion for Fedora 15 - Nonfree - Updates
[ ] RPM Fusion for Fedora Rawhide - Free
[ ] RPM Fusion for Fedora Rawhide - Nonfree

This wasn't what it looked like after a fresh install of alpha, but I disabled test-updates and enabled the others and of course, added the Fusion for the Nvidia driver and gstreamer stuff.

---------- Post added at 04:41 PM ---------- Previous post was at 12:46 PM ----------

I found this link in another thread (http://forums.fedoraforum.org/showthread.php?t=261186) that is very similar, but it unfortunately doesn't answer my question.

http://fedoraproject.org/wiki/Upgrading_from_pre-release_to_final

From reading it, I almost think I ought to enable the rawhide repos.

---------- Post added at 05:14 PM ---------- Previous post was at 04:41 PM ----------

Found the answer here: http://fedoraproject.org/wiki/QA/Updates_Testing

"Starting with the Fedora 13 development, Rawhide has become a permanent development branch. In Fedora 13 development branch and above updates-testing repository is enabled by default for any development release (Alpha, Beta, Nightly builds etc). Package maintainers in Fedora are encouraged to test their updates via this repository first to keep the development branch more robust while providing the latest updates. If you a tester, it is recommended to leave this repository enabled and provide feedback to help make the general release that follows a robust one. In the development branch, packages that are in the updates-testing repository will eventually transition into the base repository instead of the updates repository.

Before release, a fedora-release update will automatically disable the updates-testing repository and enable the updates repository. After the general release, the updates repository will start filling up as more updates gets pushed through but until the release time, updates repository will remain empty. "

[DBelton]

no. the rawhide repos are now what will become Fedora 16. you do not want to enable rawhide unless you are testing F16 or plan on breaking things :D

[sillav]

no. the rawhide repos are now what will become Fedora 16. you do not want to enable rawhide unless you are testing F16 or plan on breaking things :D

Thanks for the confirmation. Most of the threads I found were old-timers expressing frustration at questions like mine. The wiki had the right answer, but it wasn't easy to find. And this is from a 6 year user of Debian testing/sid, so Fedora newb, but know how to use the google. :cool:

[DBelton]

for the Fedora repos:

fedora and fedora updates are the main ones that will bring you up to the release version when it's available. If you have the fedora updates-testing repo enabled, then you get the packages when they are first pushed to the repo, and there is a possibility that one could have some dependency problems, etc.. Once the packages pass some more testing, then they are pushed into the fedora updates repo.

rpmfusion basically follows the same path that fedora does.

new packages are put into updates-testing. once tested and dependency problems are worked out, the package is pushed into the updates repo.

It's a matter of preference and what you wish to deal with if you want to enable the updates-testing repos. If you wish to get the "latest and greatest" updates, and don't mind if you have an occasional package to break something, then you can enable the updates-testing repo. (I certainly wouldn't enable them on a system with critical data on it, though)

[sillav]

That part I understood from previous experience in Fedora, what I didn't understand is that when a version hasn't been released yet, like F15, everything goes to testing-updates and then the day it's released all testing updates are merged into F-15, and updates / testing-updates take on the roles you described.