On Tue, 2009-08-04 at 17:19 +0200, Andre Klapper wrote: > Proposals inline, comments & proofreading by someone having English as > mothertongue welcome. Comments/Improvements inline. > > Am Dienstag, den 04.08.2009, 01:34 +0100 schrieb Susana Pereira: > > Here are the minutes of the meeting. > > Thanks for coming up with them, Susana! > > > > ==== Old untouched bugs ==== > > ACTION: AndreKlapper will do a new stock response for this case. He > > will warn the reporter that he has 6 weeks to respond before the bug > > being closed. > > Proposal for stock answer 'old_untouched' that needs to be added to > bugzilla-newer/template/en/default/bug/edit.html.tmpl: > > >> > This bug was reported against a version that is not supported anymore > nowadays. Developers are no longer working on this version so there will > not be any bug fixes for this version. > Can you please check again if the issue you reported here still happens > in a recent version of GNOME and update this report by adding a comment > and adjusting the \'Version\' field? > > Again thank you for reporting this and sorry that it could not be fixed > for the version you originally used here. > > Without feedback this report will be closed as INCOMPLETE after 6 weeks. > << This bug was reported against a version which is not supported any more. Developers are no longer working on this version so there will not be any bug fixes for it. ... > Note that http://live.gnome.org/Bugsquad/TriageGuide/StockResponses > needs an update after getting this live. > > > > ==== Kill VERIFIED and CLOSED status ==== > > ACTION: AndreKlapper and JavierJardon will update stock responses to > > ask reporters to verify the fix after it has landed in distribution. > > Proposal for adding additional sentence to stock answers 'dupe+fixed', > 'fixed_in_stable', 'fixed_in_head' in > bugzilla-newer/template/en/default/bug/edit.html.tmpl: > > >> > After your distribution has provided the updated package to you and if > you have some time, please feel encouraged to verify the fix by marking > this bug report as VERIFIED. > << After your distribution has provided you with the updated package – and if you have some time – please feel encouraged to verify the fix by marking this report as VERIFIED. If the updated package does not fix the issue, please re-open this bug report. > > ==== What to do with bugs about deprecated modules? ==== > > ACTIONS: > > - AndreKlapper make a "stock email" to contact maintainers > > Proposal: > > >> > Hi, > > according to the AUTHORS/MAINTAINERS file in GIT you maintain the module > mentioned in the subject line. > This module has not seen any updates for a long time. According to the AUTHORS/MAINTAINERS file in git, you maintain the module mentioned in the subject line. This module has not seen any updates for a long time. Andre: By "updates", do we mean "releases" or "commits"? It might be an idea to clarify in the e-mail. > Please respond to this email and inform the GNOME Bugsquad if your > project is still maintained or if it is realistically speaking dead. > If it is dead the GNOME Bugsquad is going to close the remaining open > bug reports and enhancement requests in GNOME Bugzilla and inform the > bug reporters about it. (If you instead prefer to do this yourself, just > say so.) Please respond to this e-mail and inform the GNOME Bugsquad if your project is still maintained or if it is, realistically speaking, dead. ... Andre: Do we want to mention a deadline for replying to the e-mail, and say that if the maintainers don't reply by that date then it'll be assumed their module is dead? Regards, Philip > You can access your module bug statistics by visiting > http://bugzilla.gnome.org/browse.cgi and then choosing the module name > from the "Browse:" dropdown menu. > << > > > -andre
Attachment:
signature.asc
Description: This is a digitally signed message part