On Sun, 2006-06-25 at 13:38 +0100, Timothy Murphy wrote: > Rahul Sundaram wrote: > > >> > Here is the announcement which has the details > >> > > >> > http://www.redhat.com/archives/fedora-announce-list/2006- > >> > June/msg00010.html > >> > > >> > Here is a review > >> > > >> > http://www.phoronix.com/scan.php?page=article&item=499 > >> > >> Actually, there seems very little difference to me. > >> For example, it mentions KDE-3.5.3 as one of the new things in FC6t1 > >> but I seem to have that on FC5 from fedora-extras. > > > > KDE is not in Fedora Extras and yes the first test release wouldnt be > > that different from the previous release with updates. Only intrusive > > changes that cannot be backported remain in the new release( and the > > installer related changes ) > > Sorry to pursue the matter, but I am still not entirely clear > about the relation of FC6t1 to updated FC5. > > I take it that FC6t1 contains all the FC5 updates (and extras?), > together with some RPMs from FC5's fedora-updates-testing Fedora updates-testing is for testing out updates before they get pushed into the current general releases(ie) FC4 and FC5 now. They have no direct relationship with the development version. > and fedora-extras-development? Extras development branch is the equivalent of rawhide for Extras. > In other words, a judicious selection of RPMs available under FC5. > Is that a correct understanding? No it isnt. All Fedora versions have different branches.Usually all of the packages available in FC5+Extras have their equivalent development versions and many of them have changes which dont reach FC5 updates at all. > > I realize that sometimes there may be cataclysmic changes, > eg in gcc, which mean that everything has to be changed > in one fell swoop. > But that seems pretty rare to me. Not just GCC,Glibc rebuilds. Development versions of all the major packages like GNOME, KDE, Openoffice etc. Installer related changes, new tools. Anything that is judged by the package maintainers and core developers to be too intrusive to push as updates are retained in the development branch and will only be available in next general release. Test releases are snapshot of the development release which have a short code stabilization period based on the release criteria (blocker and target bugs_. After the second test release, major changes are avoided and the third test release is usually closer to the final one. > > Nb I'm not criticizing the production of test versions, > just trying to clarify the philosophy behind them. > Rahul
