The oVirt team is pleased to announce that today oVirt moved to its own classification within our Bugzilla system as previously anticipated [1]. No longer limited as a set of sub-projects, each building block (sub-project) of oVirt will be a Bugzilla product. This will allow tracking of package versions and target releases based on their own versioning schema. Each maintainer, for example, will have administrative rights on his or h=

Bugzilla sub-project and will be able to change flags, versions, targets, and components. =20 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]. The changes will go into affect in stages, please review the wiki for more details. =20 We invite you to review the new tracking system and get involved with oVi=

QA [3] to make oVirt better than ever! =20 [1] http://community.redhat.com/blog/2015/06/moving-focus-to-the-upstream/ [2] http://www.ovirt.org/Bugzilla_rework [3] http://www.ovirt.org/OVirt_Quality_Assurance =20 --=20 Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

_______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJV7/cwAAoJEEBxx+HSYmnDM04H/i5Qz2Xh1BqLmmBXJCPT8AeK 6EJMxNUGtx2Jt+xRSVoJ7jpcakaJXbecZg4ZlUycQS3atojwudPnkqpfDJEF9wDS lsmagRV6uU1xgxYIciZW4cRE0DCIDGubHCywwKbNO0YL8Tp2kEp3dG6BRht/RSQx AB5i7rMZucVXu7YSxXO5Lpk5CvRtA5gJj1UVuS/7g0b2TLyopPP0QJI1NLbE3sqd JjhLeLf72p7m6udCp+e14rtNYNtVj3LN/ws7eFqDn7T9wrPJLNc+yzH12v1Pf4qT QiaKH9pkwqfNW3zqYku5O6dI2gTzlCntNAKFDf7dzQqjiGGZ8Z9+35nJLjUxd9w= =pPeR -----END PGP SIGNATURE-----

On Wed, Sep 9, 2015 at 11:09 AM, David Caro <dcaro(a)redhat.com&gt; wrote: > > What projects are considered for that? You can see the planning here: https://docs.google.com/spreadsheets/d/1SOJNw1WQHEhE2rVP26qNtu30aKLQIV8JE... > What should be done to add a new one? > > Adding Yaniv

> (for example, the repoman or similar are also there?) > > On 09/09, Sandro Bonazzola wrote: > > The oVirt team is pleased to announce that today oVirt moved to its own > > classification within our Bugzilla system as previously anticipated [1]. > > No longer limited as a set of sub-projects, each building block > > (sub-project) of oVirt will be a Bugzilla product. > > This will allow tracking of package versions and target releases based > on > > their own versioning schema. > > Each maintainer, for example, will have administrative rights on his or > her > > Bugzilla sub-project and will be able to change flags, > > versions, targets, and components. > > > > 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]. > > The changes will go into affect in stages, please review the wiki for > more > > details. > > > > We invite you to review the new tracking system and get involved with > oVirt > > QA [3] to make oVirt better than ever! > > > > [1] > http://community.redhat.com/blog/2015/06/moving-focus-to-the-upstream/ > > [2] http://www.ovirt.org/Bugzilla_rework > > [3] http://www.ovirt.org/OVirt_Quality_Assurance > > > > -- > > Sandro Bonazzola > > Better technology. Faster innovation. Powered by community > collaboration. > > See how it works at redhat.com > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > David Caro > > Red Hat S.L. > Continuous Integration Engineer - EMEA ENG Virtualization R&D > > Tel.: +420 532 294 605 > Email: dcaro(a)redhat.com > Web: www.redhat.com > RHT Global #: 82-62605 > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

The oVirt team is pleased to announce that today oVirt moved to its own classification within our Bugzilla system as previously anticipated [1]. No longer limited as a set of sub-projects, each building block (sub-project) of oVirt will be a Bugzilla product. This will allow tracking of package versions and target releases based on their own versioning schema. Each maintainer, for example, will have administrative rights on his or her Bugzilla sub-project and will be able to change flags, versions, targets, and components. 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]. The changes will go into affect in stages, please review the wiki for more details. We invite you to review the new tracking system and get involved with oVirt QA [3] to make oVirt better than ever! [1] http://community.redhat.com/blog/2015/06/moving-focus-to-the-upstream/ [2] http://www.ovirt.org/Bugzilla_rework [3] http://www.ovirt.org/OVirt_Quality_Assurance -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users