Re: [ovirt-users] [ovirt-devel] possible 3.4.1 blocker
Am 02.05.2014 17:05, schrieb Sven Kieske:
May I ask what the point of RC testing is, when discovered regressions get retargeted for the next release? I thought the policy was to not release something with a known regression? This does not encourage users to test release candidates at all, if found bugs don't get fixed. Maybe the next RCs can have a greater timeframe, so regressions found can get fixed before a release is made GA? Otherwise I don't see a point in testing RCs anymore. I did test it as soon as possible after it was announced in order to sort out possible regression bugs _before_ 3.4.1 gets released, as I'd like to use 3.4.1 in production. Can someone please enlighten me, what the release process is? I really thought regressions get fixed before a release. I'd also be happy if someone can tell me, that it's no regression but a fault on my side, so I can fix that. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
Il 05/05/2014 09:28, Sven Kieske ha scritto:
Am 02.05.2014 17:05, schrieb Sven Kieske:
May I ask what the point of RC testing is, when discovered regressions get retargeted for the next release?
I thought the policy was to not release something with a known regression?
Yes, and due to that policy the bug has been re-targeted back to 3.4.1 and re-added to the 3.4.1 blocker list. http://www.ovirt.org/OVirt_3.4_release-management#MUST MUST: No regressions from 3.3 Release
This does not encourage users to test release candidates at all, if found bugs don't get fixed.
Found bugs will be surely addressed according to above release criteria. If the bug is identified as blocker (and regressions are blockers) it must be fixed before GA.
Maybe the next RCs can have a greater timeframe, so regressions found can get fixed before a release is made GA?
If blockers (including regressions) are found, GA will be postponed until they will be fixed.
Otherwise I don't see a point in testing RCs anymore.
I did test it as soon as possible after it was announced in order to sort out possible regression bugs _before_ 3.4.1 gets released, as I'd like to use 3.4.1 in production.
And I really thank you for your testing!
Can someone please enlighten me, what the release process is?
I really thought regressions get fixed before a release.
I'd also be happy if someone can tell me, that it's no regression but a fault on my side, so I can fix that.
I can't judge about if the above bug is a real regression or not, added a comment in the BZ. I hope to have answered your questions. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
As always, thanks for the fast response. And thanks for re-adding as a blocker and the clarification. I still hope the bug is on my side, so 3.4.1 has not to be delayed much longer. It would be cool if some REST gurus could review my json code, and tell me if it is correct, or not. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
participants (2)
-
Sandro Bonazzola -
Sven Kieske