On Wed, Oct 30, Lubos Kocman wrote:
I'd like to ask you to participate in a following survey concerning Code Submit
Reviews specifically changelog changes:
This survey is concerning package changelog in IBS.
If you bring an example, it would be very helpful what the problem
with that changelog is...
Else, I don't like any of the options.
Listing all the stupid "typo fixed" and similar entries in a changes
file does not make any sense. Dropping changes only because they are too
old also does not make any sense, as this could be the really important
In my opinion, a changes file should contain the user relevant changes,
means important fixes and especially behavioral changes. Nothing more
and nothing less.
**We (core team*) would like to implement one of (or
combination) presented solutions in order to improve current Submit Review Process.
This process currently requires process exceptions in specific cases concerning changelog
Here is list of identified use cases which helped us to form our two proposals
*core team consisted of one or more representatives from following teams got a task to
improve the situation: BuildOPS, SLE Rel-mgmt, LABS, Security, Certification, openSUSE
reviewers, Future Technology, Customer Support, Quality Assurance, Maintenance team.
Your vote matters!
Technical Project Manager SLE | Release Manager for Modules
SUSE Software Solutions Germany, GmbH
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org