Re: Stable and unstable

[bruce@pixar.com (Bruce Perens)]

One of the major concerns regarding "stable" and "unstable" is that
it's important to not overwhelm the mirror sites by copying 1GB in a day.
They tend to take a long time to catch up with that, and operator
intervention is often required. This is why we have the symbolic link to
code-named directory scheme. We can slowly fill a directory named
"bo", for example, and then have a symlink "Debian-1.2" to "bo" appear
once all of the FTP sites have caught up.

The way I currently understnand this is that one day soon the directory
"rex" will be symbolicaly linked to "codefreeze". The directory "bo" will
be created, and will be populated entirely with symbolic links to "rex".
"bo" will be symbolic-linked to "unstable", replacing "rex" in that role.
As files in "unstable" are updated, they will replace the symbolic links
in "bo". On release day, "Debian-1.2" will be linked to "bo", and
"codefreeze", will be removed. Perhaps about a week later, "buzz" and
other Debian 1.1 stuff will be removed.

	Thanks

	Bruce

--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com