On Mon 31 Mar 2003 05:09, Steffen Barszus posted as excerpted below: > What about an "alpha release" from time to time ? My biggest problem is > -a to get the beta becaue of bandwidth > - to get the beta before the next beta is out ;)
Isn't this what Cooker is, essentially, at any moment, at least when it isn't in freeze before release (and ack-ing that contribs is never in freeze, so could actually be the alpha branch when cooker is in freeze)? IOW, alpha is certainly not a stage at which a full official ISO burn is really justified. However, once you catch up to cooker and contribs as on the servers using urpmi presumably, updating twice a week to daily effectively keeps an installation in cutting edge alpha release state. Further, a twice a week update, once the initial catch-up is done, anyway, should limit bandwidth to something reasonable, even for dialup, since that both limits the packages that have to be updated each session, and effectively ignores packages multiple-updated in one day, often simply correcting packaging depends or install script errors, controlling that aspect of bandwidth utilization. -- Duncan "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -- Benjamin Franklin
