Re: Debian v2.0 ("Hamm") Release (RSN)
-----BEGIN PGP SIGNED MESSAGE-----
On 20 Jul 1998, Manoj Srivastava wrote:
> Santiago> If yes, then perhaps I should volunteer for being a
> Santiago> co-maintainer for ftp.debian.org also, so that we do not
> Santiago> repeat this mess with slink.
>
> Actually, if you are so willing to make changes so deep in the
> freeze, I would object to you tempramental suitability to be ftp
> archive co-maintainer. Intemprate actions are not what is required of
> the ftp team.
I think you may have misunderstood my words.
Bug #21688 was reported nearly two months ago, when hamm freeze was not as
"deep" as it is now. Were this bug be fixed then, we would have a
consistent base section now. Fortunately ftp.debian.org has three
maintainers now, and this is unlikely to happen again in slink, so no, I
don't really think that ftp.debian.org needs even more maintainers.
I expect bugs against such an important package to be fixed "soon enough",
not only "important" ones. I trust the current ftp.debian.org maintainers
to do this in slink before it is too late.
Although it may be true that doing this change now may have risks, I think
that Brian should have fixed (or tell the maintainers to fix) all
ftp.debian.org bugs (at least the ones about hamm) before deciding about
the release date.
Could we make policy (for slink) that all bugs against ftp.debian.org
should be fixed before deciding about the release date and before entering
in the "deep freeze"?
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
iQCVAgUBNbRzTCqK7IlOjMLFAQEEwgP/Z1JrCvC05KsmqK9BR7TtVkmZFOiTfCCJ
dc2WZalbMAeuJmg+wXnRWie8tWrqRPdlxNkpTrGvqdSrbd7TbkYZgEDk59oQNSjs
jx2j0eceL50iHUBnUgG+RzViGYHLLHdvPQ548eTk36hJUnSLbipscVe4ZhZ5P2QS
GZ7fK9rB1so=
=OYJK
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: