Re: [ovirt-devel] [ANN] Changes to oVirt Bugzilla Process.
Hi,
I assume this applies to oVirt classification only and downstream
clones still need to follow the standard acking/cloning process?
If DS stays the same:
Can I propose one slight change to downstream cloning too? Would
keeping the original target milestone and setting the Z stream flag
(with question mark) only make sense?
Somebody (bot, manager or PM) would trigger the clone job that would
create a cloned bug with no (or manually provided) milestone. We would
then triage the cloned bug as usual. This would avoid the issues with
bugs disappearing from US queries and resetting the target milestone
to the original one after cloning would not be needed.
Martin
On Mon, Oct 31, 2016 at 9:22 AM, Yaniv Dary <ydary(a)redhat.com> wrote:
Hi,
In order to make the process lighter and reduce bureaucracy we will be
making the following changes this Sunday (06/11/16):
- Acks will no longer be needed on bugs, only on RFEs - This means the rules
engine will not add them and you are not required to get them for bugs. RFEs
will still get acks by rules engine and are required for every feature.
- Flags be set automatically according to milestone - This means you will no
longer need to add flags. The rules engine will do this for you according to
milestone. You will still be able to add flags to mark a bug to be tested on
two branches.
- The version flag will not differentiate between major version and z stream
- This change will only apply to 4.1+ flags. For example ovirt-4.1.0 and
ovirt-4.1.z will be merged to ovirt-4.1 flag.
Thanks,
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: ydary(a)redhat.com
IRC : ydary
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel