On Mon, May 30, 2005 at 05:53:31PM +0200, Jeroen van Wolffelaar wrote:
>
> For http://www.wolffelaar.nl/~sarge, there are already diffs in a
> database that are exactly the diffs between sarge & sid changelogs.
> Anyway, this problem is already long time known, and the solution will
> be implemented post-sarge in the BTS: proper version tracking on the
> bugs. For now, we rely indeed on people testing sarge and the
> maintainers -- after all, it's actually simply up to the maintainers to
> care for the important bugs to be solved in the version of their
> packages targetted for a stable release -- whatever any general group
> like QA or release management does, if a maintainer for example fixes a
> self-discovered RC-bug without actually filing it and ringing any bells
> anywhere that an freeze-exception is needed, how can anyone detect this
> and act on it? We do have maintainers for a reason.
In theory, this would work.
In practice, I doubt it.
After a maximum of how many days do you expect a maintainer to have
fixed a simple RC bug (e.g. "missing build dependency on foo") in one of
his packages in theory?
And does this match the practical observations during the last years?
Debian has 1000 maintainers with a quite big variation in the quality of
package maintaining.
If you base anything on the assumption every single maintainer in Debian
was 100% properly maintaining his packages, you've based it on a false
assumption.
> --Jeroen
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
