Re: QA Upload best practices, 2nd draft

2004-07-19 Thread Matthew Palmer
On Mon, Jul 19, 2004 at 03:12:23PM +0100, Martin Michlmayr wrote: > Anyway, I think the scenario is not very likely. I was more thinking > about new upstream released which is normally a bad idea for NMUs but > a good idea for QA uploads (if nobody uploads the new upstream > version, we lag behind

Re: QA Upload best practices, 2nd draft

2004-07-19 Thread Martin Michlmayr
* Matthew Palmer <[EMAIL PROTECTED]> [2004-07-19 13:05]: > Would you encourage people to rewrite the packaging method used (eg > convert from dh_ to cdbs) in a QA upload? I'm thinking that, apart > from fixing hideous bletcherisms of past maintainers (such as making > upstream-available packages D

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Joey Hess
Matthew Palmer wrote: > Would you encourage people to rewrite the packaging method used (eg convert > from dh_ to cdbs) in a QA upload? I'm thinking that, apart from fixing > hideous bletcherisms of past maintainers (such as making upstream-available > packages Debian-native) we would want to avoi

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Matthew Palmer
On Sun, Jul 18, 2004 at 03:41:26PM +0200, Rene Engelhard wrote: > Hi, > > Matthew Palmer wrote: > > * It's also important to ensure that the maintainer address is set > > correctly. > > The address has changed in the past, and some packages haven't had their > > maintainer address changed since

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Matthew Palmer
On Sun, Jul 18, 2004 at 02:06:22PM +0100, Martin Michlmayr wrote: > * Matthew Palmer <[EMAIL PROTECTED]> [2004-07-18 19:59]: > > what's going on. Setting the owner of the bug to you (not the submitter!) > > "Setting the owner of the bug (not the submitter!) to you" makes it > clearer that you're

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Martin Michlmayr
* Rene Engelhard <[EMAIL PROTECTED]> [2004-07-18 15:41]: > > uploads!), so ensure that the maintainer of the package is set to "Debian QA > > Packages <[EMAIL PROTECTED]>". > > Shouldn't it be Debian QA Group <[EMAIL PROTECTED]>? Yes. -- Martin Michlmayr [EMAIL PROTECTED]

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Rene Engelhard
Hi, Matthew Palmer wrote: > * It's also important to ensure that the maintainer address is set correctly. > The address has changed in the past, and some packages haven't had their > maintainer address changed since it's orphaning (even after several QA > uploads!), so ensure that the maintainer

Re: QA Upload best practices, 2nd draft

2004-07-18 Thread Martin Michlmayr
* Matthew Palmer <[EMAIL PROTECTED]> [2004-07-18 19:59]: > what's going on. Setting the owner of the bug to you (not the submitter!) "Setting the owner of the bug (not the submitter!) to you" makes it clearer that you're not setting the submitter as owner. > * In most aspects of preparing a QA u

QA Upload best practices, 2nd draft

2004-07-18 Thread Matthew Palmer
I've incorporated the excellent suggestions from Pierre Machard, Andreas Metzler, and Frank Lichtenheld, to produce this new draft. Further comments appreciated. -8<- QA UPLOAD BEST PRACTICES When making an upload on a package maintained by the QA team, it is important to keep some basi