On Thu, 2010-02-11 at 01:00 +0000, Mat Booth wrote: > On 11 February 2010 00:49, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > > Mat Booth wrote: > >> To be fair, it seems like you are updating KDE constantly. If the spin > >> contains the packages available at the time it was spun, I'm not sure > >> what more you can ask for. > > > > The packages available at the time it was released. ;-) I.e. not preparing > > the spin 3 days before a KDE update goes out, considering that testing the > > spin apparently takes 9 days. But nobody at Fedora Unity ever talks to us > > about KDE update schedules. Having to download another 100 MB worth of > > updates even when installing the day of the respin's release kinda defeats > > the point of the respin. Yet this is happening at every single respin, they > > somehow always magically manage to hit the window where a KDE update will go > > out during their testing week. > > > > (My recommendation: just install from the F12 GA KDE Live CD and get the > > updates, you'll have to update all of KDE anyway, even if you use those > > installer-DVD-only respins, and installing from the KDE Live CD is > > recommended.) > > > > Meh. > > If you insist on putting out major updates for released Fedoras it > will never a good time to do a re-spin. Oh well. Oh seriously, a little communication between the Unity team and the KDE team wouldn't hurt here. If the Unity team said "hey, we're going to do a spin on March 6th" but the KDE team wanted to slip that a few days to get some new packages in, that wouldn't end the world. Obviously if the KDE team's testing runs too late, you can just ship what's already in the repos because they didn't hit the agreed-upon target. But it would be curteous to at least make an effort to line up schedules. Dan -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
