| 1 |
On Monday 25 January 2010 23:11:18 Nikos Chantziaras wrote: |
| 2 |
> > Today it is finally released. I don't know why it took so long. :) |
| 3 |
> |
| 4 |
> It's a bit sad though that an open source project keeps secrets... I |
| 5 |
> found out that the tarballs were available for days now but only for |
| 6 |
> maintainers of KDE packages of various distros. For example Arch Linux |
| 7 |
> had RC2 binaries available in its [kde-unstable] repo since Jan 21, but |
| 8 |
> no one would give a link to the tarballs used to build the sources |
| 9 |
> because they are "secret". |
| 10 |
> |
| 11 |
> Am I the only one to find this frustrating (to say the least)? |
| 12 |
|
| 13 |
There's nothing secret here. Nothing to see, move along folks. |
| 14 |
|
| 15 |
The code is always available in svn, if you wanted it that bad you could have |
| 16 |
checked it out. It's common release engineering practice to build a tarball |
| 17 |
from the repo and provide limited access to *those* files to distros and |
| 18 |
mirrors to give them time to sync and build their binaries before making them |
| 19 |
available to the public. I mirror Ubuntu and Fedora. The deal is that I get |
| 20 |
the rpms and debs two days before the public does. This is so that every |
| 21 |
official mirror on the planet is ready to simultaneously publish the release |
| 22 |
*all*at*the*same*time*. |
| 23 |
|
| 24 |
This is a very excellent way of working. You have no idea how much chaos |
| 25 |
thousands of eager beaver users cause pounding away at my inbox if I don't |
| 26 |
have the latest Ubuntu for them the day it is released because sharks bit the |
| 27 |
undersea cable to London and the inbound bandwidth slows to a crawl. I'm not |
| 28 |
making this up - stuff like this happens. |
| 29 |
|
| 30 |
Gentoo erred in publishing ebuilds for tarballs that were not generally |
| 31 |
available yet. |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
alan dot mckinnon at gmail dot com |
Archives