Joe Hart wrote:
According to the documentation, when Etch is made stable, a new testing
will be made (in this case called Lenny), which is a direct clone of
Etch. Packages will migrate from Sid to Lenny at the same pace as usual
for the testing distro.
However, since Etch has been frozen, there are a lot of packages from
Sid that are ready for Testing, but can't go there. Lenny will catch
them when it is created, thus it is possible that the large number of
packages flowing in could cause some stability problems.
Does this clear things up?
Yes, thanks. I believe I understand now.
So if I want to surf the testing edge on my user's machines, then what I
should do is pay close attention to Etch's release, and then once it's
released, hold off on upgrading anything in testing until after the dust
has had a chance to settle a bit. Right?
So, how many Debian administrators out there actually take this kind of
approach?
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
