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