Mailinglist Archive: opensuse-packaging (174 mails)
< Previous | Next > |
Re: [opensuse-packaging] factory-auto will start checking bnc# visibility
- From: Robert Schweikert <rjschwei@xxxxxxxx>
- Date: Fri, 22 Nov 2013 11:30:53 -0500
- Message-id: <528F86BD.5030304@suse.com>
On 11/22/2013 10:07 AM, Dominique Leuenberger a.k.a. Dimstar wrote:
This should be addressed by "No private initial description allowed". We expect information about the bug and reproduction steps in the initial description. None of that should be "private" sensitive data.
Later,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
Public Cloud Architect
rjschwei@xxxxxxxx
rschweik@xxxxxxxxxx
781-464-8147
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
Quoting Andreas Jaeger <aj@xxxxxxxx>:
On 11/22/2013 03:33 PM, Adrian Schröter wrote:
If we really want the SUSE developers to fix the bugs, we have to live
with some private bugs. Yes, we should ask for clear descriptions and
not just "fix bnc#xxxx",
Which is something 'we' devel project maintainers can do (and do!).
Most of the time I run into 'closed' issues when it comes to identify if
a patch is still valid; a clear 'bug statement and how to reproduce the
bug' is often missing (or references to test documents).
This is not something I'd expect to be all put into the .changes...
This should be addressed by "No private initial description allowed". We expect information about the bug and reproduction steps in the initial description. None of that should be "private" sensitive data.
Later,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
Public Cloud Architect
rjschwei@xxxxxxxx
rschweik@xxxxxxxxxx
781-464-8147
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
< Previous | Next > |