Le lun, 21/06/2004 à 10:21 +0200, Kilian Krause a écrit : > Hi Damien, > > Am Mo, den 21.06.2004 schrieb Damien Sandras um 9:26: > > I will ask to Cédric, perhaps that the snapshots should be moved to > > Gnomemeeting.org, they have more bandwidth, everything is saved, and > > that would be more logical for users. > > hehe, we already have 3 mirrors for the snapshots (4 when counting my > home box which does do a debian mirror too). So it's barely possible to > "loose" a snapshot. I just ran out of space on the buildd server so i > had to cut down the archive to now 10 days. If bandwidth is a problem, > we should point more users to the join mirror, which is supposed to have > plenty. > Ill try to see what's possible to do with rsync on gnomemeeting.org > About the unstable releases, i somewhat doubt it's a good idea as the > overhead is quite exhaustive (unless we do invent a flag in the buildd > to have the new releases just "drop right out of it"). This idea was > already foreseen in the original planning of the buildd, but has not yet > been realized (and even then it requires quite some effort to make this > work seamlessly). So if there's a point in "unstable" releases, then > let's make them "testing" releases with a little more preparation and > move the whole 1.2 schedule forward a bit.. Somewhat i tend to agree > with Snark that our snapshots are already pretty stable, so we could > just copy out certain packages when we're satisfied with them to a > "recommended unstable beta".. This could oppose the "bleeding edge cvs - > may be broken" of daily snapshots. > Perhaps that new idea is the best one... > _______________________________________________ > Gnomemeeting-devel-list mailing list > Gnomemeeting-devel-list gnome org > http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list -- _ Damien Sandras (o- GnomeMeeting: http://www.gnomemeeting.org/ //\ FOSDEM : http://www.fosdem.org v_/_ H.323 phone : callto:ils.seconix.com/dsandras seconix com
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=