<div dir="ltr"><div><div>I have just finished moving all the bugs from the old tracker to the new one for all 3.6.0 and above RFEs and bugs.<br></div>You
are requested to use the new classification from this point on. 3.5.z
bug should be moved by their assignee to the correct target once you
make sure, you can fill the target\version\milestone in the new tracker.<br><br></div><div>Please fix your queries to include the classification. Reports based on whiteboard will continue to work.<br></div>You may also use the milestone\flags to query.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><pre cols="72"><span style="font-family:arial,helvetica,sans-serif">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: <a href="mailto:ydary@redhat.com" target="_blank">ydary@redhat.com</a>
IRC : ydary</span></pre>
</div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Sep 9, 2015 at 11:59 AM, Sandro Bonazzola <span dir="ltr"><<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>The oVirt team is pleased to announce that today oVirt moved to its own classification within our Bugzilla system as previously anticipated [1].</div><div>No longer limited as a set of sub-projects, each building block (sub-project) of oVirt will be a Bugzilla product.</div><div>This will allow tracking of package versions and target releases based on their own versioning schema.</div><div>Each maintainer, for example, will have administrative rights on his or her Bugzilla sub-project and will be able to change flags,</div><div>versions, targets, and components.</div><div><br></div><div>As part of the improvements of the Bugzilla tracking system, a flag system has been added to the oVirt product in order to ease its management [2].</div><div>The changes will go into affect in stages, please review the wiki for more details.</div><div><br></div><div>We invite you to review the new tracking system and get involved with oVirt QA [3] to make oVirt better than ever!</div><div><br></div><div>[1] <a href="http://community.redhat.com/blog/2015/06/moving-focus-to-the-upstream/" target="_blank">http://community.redhat.com/blog/2015/06/moving-focus-to-the-upstream/</a></div><div>[2] <a href="http://www.ovirt.org/Bugzilla_rework" target="_blank">http://www.ovirt.org/Bugzilla_rework</a></div><div>[3] <a href="http://www.ovirt.org/OVirt_Quality_Assurance" target="_blank">http://www.ovirt.org/OVirt_Quality_Assurance</a></div><span class="HOEnZb"><font color="#888888"><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</font></span></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>