Re: Freeze exceptions: parmetis, ccc, babel, illuminator; please be considerate to busy developers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Adam C Powell IV wrote:
> Greetings,
Hi Adam
[...]
> I must say, as a Debian developer at a US university, I feel this freeze
> process has treated me very inconsiderately. We were told for about
> eight months that a freeze was "on the way", which after four, five, six
> and seven of those months didn't sound credible. Then suddenly in one
> of the two busiest times of year at US universities (final exams in May
> and December), we're given an ultimatum: get your packages done in two
> weeks or they're out of sarge. The pressure has forced me to divert time
> from writing and grading exams (babel in particular took the better part
> of a whole day) and I am not happy about this at all. Because of the
> propensity of academics (students, faculty and staff) to be free
> software developers, and the fraction of Debian developers in the US, I
> am certain I'm not alone in this.
You had 7 months to make sure the packages you uploaded are ready for
sarge... You only have 2 weeks to fix RC bugs that *still* don't make
your package ready for sarge...
> Given that processing of the NEW queue has been extremely slow over the
> past several months (e.g. mpich lib restructuring sat there from Dec 22
> to Feb 19), which only picked up *after* the freeze, how can the release
> team treat developers this way? "Your packages are not important enough
> to process in less than two months, but you *must* turn around your last
> fixes for sarge with just two weeks' notice during the busiest time of
> year for a significant fraction of you."
This problem has nothing to do with the release per se and has been
solved as good as possible for the future.
Cheers
Luk
PS: Please don't see this as an attack or something to start a flame
for. I can understand that you think that the freeze came suddenly, but
on the other hand there was in fact already for 7 months a pseudo freeze...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCiypx5UTeB5t8Mo0RAlyIAJsF2PdBjd6eYpjegY0KICfn+DNNGACgnwfl
hcwfyNDk2vWFoVEns4SdHUQ=
=jSqm
-----END PGP SIGNATURE-----
Reply to: