Re: Report from Debconf's QA BOF

2008-11-27 Thread tim hall
Raphael Geissert wrote: If nobody cares enough to report anything then why should we keep them? I think that's the main rationale here. Of course, making it a release goal (as in terms of RC, not RG) would allow anyone to know that if nothing happens it won't be shipped, thereby making people

Re: Report from Debconf's QA BOF

2008-11-27 Thread Raphael Geissert
Lucas Nussbaum wrote: On 25/11/08 at 20:42 -0600, Raphael Geissert wrote: The default policy is going to be: orphaned packages are not candidates in Err s/The default policy is going to be/The proposed policy is shape for a release; but as Luk said, the severity might be lowered if needed

Re: Report from Debconf's QA BOF

2008-08-22 Thread Lucas Nussbaum
On 21/08/08 at 23:13 +0200, Holger Levsen wrote: Hi, On Friday 15 August 2008 05:16, Steve Langasek wrote: (you might want to check the video when it will be available) From experience, there seems to be a several-month delay before videos become available after DebConf.

Re: Report from Debconf's QA BOF

2008-08-21 Thread Holger Levsen
Hi, On Friday 15 August 2008 05:16, Steve Langasek wrote: (you might want to check the video when it will be available) From experience, there seems to be a several-month delay before videos become available after DebConf.

Re: Report from Debconf's QA BOF

2008-08-21 Thread Steve Langasek
On Thu, Aug 21, 2008 at 11:13:38PM +0200, Holger Levsen wrote: On Friday 15 August 2008 05:16, Steve Langasek wrote: (you might want to check the video when it will be available) From experience, there seems to be a several-month delay before videos become available after DebConf.

Re: Report from Debconf's QA BOF

2008-08-17 Thread Enrico Zini
On Fri, Aug 15, 2008 at 05:45:52PM +0200, Frank S. Thomas wrote: I think it would also be nice if wnpp-alert could sort packages by popcon score so that developers know which packages are more worth adopting. Anyone interested in creating infrastructure to bring popcon data into a system and

Re: Report from Debconf's QA BOF

2008-08-15 Thread Martin Michlmayr
* Lucas Nussbaum [EMAIL PROTECTED] [2008-08-14 18:16]: The idea of having a script inside devscripts that lists the RC-buggy and orphaned packages that are locally installed was proposed. I filed a bug about that. See #495152 These are included already: wnpp-alert - check for installed

Re: Report from Debconf's QA BOF

2008-08-15 Thread Lucas Nussbaum
On 15/08/08 at 09:21 +0300, Martin Michlmayr wrote: * Lucas Nussbaum [EMAIL PROTECTED] [2008-08-14 18:16]: The idea of having a script inside devscripts that lists the RC-buggy and orphaned packages that are locally installed was proposed. I filed a bug about that. See #495152 These are

Re: Report from Debconf's QA BOF

2008-08-15 Thread Lucas Nussbaum
On 15/08/08 at 05:49 +0200, Luk Claes wrote: Steve Langasek wrote: On Fri, Aug 15, 2008 at 12:01:26AM -0300, Lucas Nussbaum wrote: - O: bugs are now RC, so packages are removed from testing using the release team's existing policies. Which means that some O: packages might stay in testing

Re: Report from Debconf's QA BOF

2008-08-15 Thread Stefano Zacchiroli
On Fri, Aug 15, 2008 at 09:21:30AM +0300, Martin Michlmayr wrote: These are included already: wnpp-alert - check for installed packages up for adoption or orphaned rc-alert - check for installed packages with release-critical bugs Ah, according to #495152 you want cronjobs around those

Re: Report from Debconf's QA BOF

2008-08-15 Thread Frank S. Thomas
On Friday 15 August 2008 15:52:55 Stefano Zacchiroli wrote: On Fri, Aug 15, 2008 at 09:21:30AM +0300, Martin Michlmayr wrote: These are included already: wnpp-alert - check for installed packages up for adoption or orphaned rc-alert - check for installed packages with release-critical

Re: Report from Debconf's QA BOF

2008-08-15 Thread Adam D. Barratt
On Fri, 2008-08-15 at 17:45 +0200, Frank S. Thomas wrote: [...] I think it would also be nice if wnpp-alert could sort packages by popcon score so that developers know which packages are more worth adopting. That would be #478835. Adam (who really should be packing and not reading mail :-)

Re: Report from Debconf's QA BOF

2008-08-15 Thread Joey Hess
Lucas Nussbaum wrote: Sure, Luk was here, and didn't express any disagreement. Actually, I tried hard to give several opportunities to raise concerns, but everybody apparently really agreed with the proposal. (you might want to check the video when it will be available) That wasn't really my

Re: Report from Debconf's QA BOF

2008-08-15 Thread Lucas Nussbaum
On 15/08/08 at 12:30 -0400, Joey Hess wrote: Lucas Nussbaum wrote: Sure, Luk was here, and didn't express any disagreement. Actually, I tried hard to give several opportunities to raise concerns, but everybody apparently really agreed with the proposal. (you might want to check the video

Report from Debconf's QA BOF

2008-08-14 Thread Lucas Nussbaum
Hi, Here is a list of what was discussed/agreed upon during Debconf's QA BOF. Handling of orphaned packages = After lenny release, the handling of O, ITA and RFA bugs will be changed. - O:, ITA: and RFA: are reassigned to the package they are about. - They are marked

Re: Report from Debconf's QA BOF

2008-08-14 Thread Lucas Nussbaum
On 14/08/08 at 19:41 -0700, Steve Langasek wrote: On Thu, Aug 14, 2008 at 06:16:43PM -0300, Lucas Nussbaum wrote: Here is a list of what was discussed/agreed upon during Debconf's QA BOF. Handling of orphaned packages = After lenny release, the handling of

Re: Report from Debconf's QA BOF

2008-08-14 Thread Steve Langasek
On Fri, Aug 15, 2008 at 12:01:26AM -0300, Lucas Nussbaum wrote: - O: bugs are now RC, so packages are removed from testing using the release team's existing policies. Which means that some O: packages might stay in testing for a longer time because they are dependencies of other

Re: Report from Debconf's QA BOF

2008-08-14 Thread Luk Claes
Steve Langasek wrote: On Fri, Aug 15, 2008 at 12:01:26AM -0300, Lucas Nussbaum wrote: - O: bugs are now RC, so packages are removed from testing using the release team's existing policies. Which means that some O: packages might stay in testing for a longer time because they are