> Q: how long should users expect between your announcement of a new version > and when it actually appears on a download site,
Both Tux and UTK pull with rsync fairly often (at least once a day, probably more). Which one gets it first depends on their schedule; ibiblio will have it in /pub/linux/Incoming very soon after I upload it to /incoming/Linux, *if* I in fact upload it there- which is not true of all releases, see below, then somewhat later they will move it into /pub/linux/system/recovery. Tucows/Linuxberg I gave up figuring out how to keep in the loop, eventually I probably send them an email. > and where should eager users go to download a release when you first > make it available (rather than waiting for mirrors to refresh)? There is no such place. There was an incident where I had to pay extra money to an ISP because of a mirror in a loop, and I really am not trying to encourage pulling the newest of everything unless you read the release notes in the FAQ and think you really want the newest. You have to wait until it appears on a mirror. Um... let met check... ah, there is a permissions problem in the rsync source, that is why it is taking so long. > 2.0.23 is what's current on the mirrors. Ah well. As noted in the release notes, the change between 2.0.23 and 2.0.27 was purely in the *removal* of functionality, freeing up 20 sectors, into which I have not yet put any new functionality... so, unless you want space on the root filesystem to put some 10K onto, you may *want* to stick with 2.0.23. I didn't even upload a newer one to ibiblio yet, I tend to do that somewhat less often, although in fact they may have it available first in the cases where I do upload it there. -Tom
