Re: Who checks for bugs fixed in unstable but not in sarge?
On Thu, Aug 12, 2004 at 04:06:18PM +0300, Riku Voipio wrote:
> > If such an easy and clearly RC bug as #237071 which is already fixed in
> > unstable isn't adressed in testing until today, something is definitely
> > going wrong. And if it was Jeroen's job as you said, he isn't doing it
> > properly.
> > It will be worse between "28 August 2004" and "16 September 2004"
> > when many hundred packages with a more recent version than in unstable
> > whether sarge have to be evaluated and fixed during only three weeks.
> > This extra work is a price you have to pay for freezing testing, but if
> > it isn't done properly and very fast, it might result in serious delays
> > of the release.
> What would really be needed would be proper version tracking in BTS,
> so that bugs get closed by a specific version, and we could search
> all bugs affecting specific versions of packages.
You will never find all issues in the BTS.
E.g. the BTS doesn't tell you that the unstable package of SpamAssassin
contains a fix for a potential DoS attack.
"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