[ANN] [QE] Bugzilla updates for oVirt Product
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
--r4QXMf6/kyF/FvJJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable What projects are considered for that? What should be done to add a new one? (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 h= er 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= rt 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --r4QXMf6/kyF/FvJJ Content-Type: application/pgp-signature -----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----- --r4QXMf6/kyF/FvJJ--
On Wed, Sep 9, 2015 at 11:09 AM, David Caro <dcaro@redhat.com> wrote:
What projects are considered for that?
You can see the planning here: https://docs.google.com/spreadsheets/d/1SOJNw1WQHEhE2rVP26qNtu30aKLQIV8JEzPp...
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@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@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
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@redhat.com IRC : ydary On Wed, Sep 9, 2015 at 12:11 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Wed, Sep 9, 2015 at 11:09 AM, David Caro <dcaro@redhat.com> wrote:
What projects are considered for that?
You can see the planning here: https://docs.google.com/spreadsheets/d/1SOJNw1WQHEhE2rVP26qNtu30aKLQIV8JEzPp...
What should be done to add a new one?
Adding Yaniv
For the first stage we will not be adding any additional sub-projects. After the full migration on the existing sub-project we can consider adding additional ones.
(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@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@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
--1ppIqr1kl39GnwQx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 09/09, Yaniv Dary wrote:
Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 =20 Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary =20 =20 On Wed, Sep 9, 2015 at 12:11 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote: =20
On Wed, Sep 9, 2015 at 11:09 AM, David Caro <dcaro@redhat.com> wrote:
What projects are considered for that?
You can see the planning here: https://docs.google.com/spreadsheets/d/1SOJNw1WQHEhE2rVP26qNtu30aKLQIV8=
JEzPp8KqCbwU/edit?usp=3Dsharing
What should be done to add a new one?
Adding Yaniv
=20 For the first stage we will not be adding any additional sub-projects. After the full migration on the existing sub-project we can consider addi= ng additional ones.
mmm, ok, not renaming either? (ovirt-testing-framework is not longer there,= it was moved to lago)
=20 =20
(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 bas= ed 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@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@redhat.com Web: www.redhat.com RHT Global #: 82-62605
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboratio= n. See how it works at redhat.com
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --1ppIqr1kl39GnwQx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJV8BsrAAoJEEBxx+HSYmnDt/gH/3OcfufOzyLmVv+F20Xsef5a W/xxGDxplrN7M9aTW2kLxewSFISAQ4KVokJPHPn+r5eYtitZCpthddjyHsyVgchK fnBav48ZrjChYiDYucSdvUfVxHJ5iX/rqs9Dh5mj9jGF6/eGgHAlZqrBznG5fxje ona/Fj3hN4zJSOf2Hulga/blxiZjXUAfjLN2nPCSfGho9nleDDbcTGVFVTkTU+j7 rwl2c91m/Ud3KuR6epnIKGIQOV6ZbLtoDz46dgV08ddwtwT5NCswuMjY+kouzQ0v XVKRTWZcZmkF53ZjY6AwAzgqC8L8KvdlW0r4qoBwon3I3XdxQlGeqn9SZxcwNDs= =M5C6 -----END PGP SIGNATURE----- --1ppIqr1kl39GnwQx--
Hi, Great to see this alive! How do we open bug for issues in the bugzilla layout? :) How do we add new products? More important for me is how do we add new version/target release? Thanks! Alon ----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: announce@ovirt.org, "users" <users@ovirt.org>, devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Wednesday, September 9, 2015 11:59:27 AM Subject: [ANN] [QE] Bugzilla updates for oVirt Product
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On Wed, Sep 9, 2015 at 11:25 AM, Alon Bar-Lev <alonbl@redhat.com> wrote:
Hi,
Great to see this alive! How do we open bug for issues in the bugzilla layout? :) How do we add new products? More important for me is how do we add new version/target release?
Adding yaniv
Thanks! Alon
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: announce@ovirt.org, "users" <users@ovirt.org>, devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Wednesday, September 9, 2015 11:59:27 AM Subject: [ANN] [QE] Bugzilla updates for oVirt Product
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Wed, Sep 9, 2015 at 11:25 AM, Alon Bar-Lev <alonbl@redhat.com> wrote:
Hi,
Great to see this alive!
+1 - fabian
How do we open bug for issues in the bugzilla layout? :) How do we add new products? More important for me is how do we add new version/target release?
Thanks! Alon
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: announce@ovirt.org, "users" <users@ovirt.org>, devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Wednesday, September 9, 2015 11:59:27 AM Subject: [ANN] [QE] Bugzilla updates for oVirt Product
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Fabian Deutsch <fdeutsch@redhat.com> RHEV Hypervisor Red Hat
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. 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. Please fix your queries to include the classification. Reports based on whiteboard will continue to work. You may also use the milestone\flags to query. 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@redhat.com IRC : ydary On Wed, Sep 9, 2015 at 11:59 AM, Sandro Bonazzola <sbonazzo@redhat.com> 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
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (5)
-
Alon Bar-Lev -
David Caro -
Fabian Deutsch -
Sandro Bonazzola -
Yaniv Dary