On 05/28/2018 01:31 PM, Anton Aylward wrote:
On 28/05/18 12:12 PM, Simon Lees wrote:
.... or if a community member would like to make changes to a certain package and are wondering why a change was made in a certain way.
That doesn't sound a like "bug report' to me but the sort of question that might be asked on the factory-, application specific or even main lists.
The issue being address is when a bug report already exists. Customer A files a bug in bugzilla.suse.com. By default this bug is not visible to openSUSE contributors. But as a result of this bug a package needs to be changed, patch added, other changes, and what happens is that (bsc#xyz) shows up in the changelog. A non SUSE employee cannot see this bug, this is a problem when trying to understand the changes in the package. SO the idea is that if someone needs the bug information to work on a given package they send a request to the new list. If you are not a developer this is mostly immaterial to you. This makes it easier for maintainers to get needed context. As long as there enough people that can review the requests and the bugs and mark them public if appropriate. Hopefully the example clarifies the situation. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Architect LINUX Team Lead Public Cloud rjschwei@suse.com IRC: robjo