Bug#484805: marked as done (developers-reference: please make clone to tech-ctte the default)
control: reopen -1 control: retitle -1 dev-ref: tech-ctte prefers fresh bug reports with a summary thanks On Sat, Jan 26, 2019 at 12:34:46PM -0700, Sean Whitton wrote: > ISTM that it would be useful to have this in dev-ref, yes. I'm not sure > whether it should be a reopening or a new bug though :) I will leave > this in the package maintainer's hands ;) heh, thanks! -- tschüß, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#484805: marked as done (developers-reference: please make clone to tech-ctte the default)
Hello, On Sat 26 Jan 2019 at 12:11AM +00, Holger Levsen wrote: > On Fri, Jan 25, 2019 at 04:56:09PM -0700, Sean Whitton wrote: >> > which IMO is as good as it is. It also explicitly points to >> > http://www.debian.org/devel/tech-ctte for detailed information. >> At least for Policy bugs referred to the TC, they prefer a fresh bug >> where the first message is a summary of the situation, rather than a clone. > > so you suggest a reopening of this bug? > > (yes or no as an answer would be great, even greater in the case of > 'yes' would obviously be a patch, but many thanks already for this > feedback, we can write the patch later, if needed?!) ISTM that it would be useful to have this in dev-ref, yes. I'm not sure whether it should be a reopening or a new bug though :) I will leave this in the package maintainer's hands ;) -- Sean Whitton signature.asc Description: PGP signature
Bug#484805: marked as done (developers-reference: please make clone to tech-ctte the default)
On Fri, Jan 25, 2019 at 04:56:09PM -0700, Sean Whitton wrote: > > which IMO is as good as it is. It also explicitly points to > > http://www.debian.org/devel/tech-ctte for detailed information. > At least for Policy bugs referred to the TC, they prefer a fresh bug > where the first message is a summary of the situation, rather than a clone. so you suggest a reopening of this bug? (yes or no as an answer would be great, even greater in the case of 'yes' would obviously be a patch, but many thanks already for this feedback, we can write the patch later, if needed?!) -- tschüß, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#484805: marked as done (developers-reference: please make clone to tech-ctte the default)
Hello, On Fri 25 Jan 2019 at 07:21PM +00, Debian Bug Tracking System wrote: > i'm closing this bug report because the wording has been improved > compared to when this bug was filed. It now says: > > if this situation is > unacceptable, you (or the submitter) may want to require a decision of the > technical committee by reassigning the bug to role="package">tech-ctte (you may use the clone command of the > BTS > if you wish to keep it reported against your package). Before doing so, > please > read the recommended > procedure. > > which IMO is as good as it is. It also explicitly points to > http://www.debian.org/devel/tech-ctte for detailed information. At least for Policy bugs referred to the TC, they prefer a fresh bug where the first message is a summary of the situation, rather than a clone. -- Sean Whitton signature.asc Description: PGP signature
