On Thu, 2017-07-06 at 15:13 -0400, Konrad Rzeszutek Wilk wrote:
On Thu, Jul 06, 2017 at 11:59:01AM -0700, Adam Williamson wrote:
Hi, folks! A while ago, Xen virtualization functionality was added to the criteria and the validation test case set, on the understanding that Oracle would provide testing for it (and help fix bugs as they arose).
For the last couple of releases we really have not had any such testing
We had been doing the testing, it just that we (or rather me and Dariof) seem to get a wind of this at the last minute. Not sure exactly how to fix that thought.
Well, I mean, every few *days* a compose gets nominated for validation testing, and a mail is sent to test-announce. Just check your test- announce archives for mails with "nominated for testing" in their subject lines, and you'll see dozens. Is this not sufficient notification?
from Oracle. On that basis, I'm proposing we remove this Final criterion:
s/Oracle/Xen Project/ I believe?
Perhaps, it's just that it always seemed to be you doing the testing, so they got a bit conflated :)
"The release must boot successfully as Xen DomU with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen."
and change the 'milestone' for the test case - https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Xen_Para_Virt - from Final to Optional.
Thoughts? Comments? Thanks!
I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested regularly - not *only* on the final release candidate, right before we sign off on the release. It needs to be tested regularly throughout the release cycle, on the composes that are "nominated for testing".
Thanks!
Posting from gmail, so hopefully it doesn't send it as HTML..
On Thu, Jul 6, 2017 at 3:45 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Thu, 2017-07-06 at 15:13 -0400, Konrad Rzeszutek Wilk wrote:
On Thu, Jul 06, 2017 at 11:59:01AM -0700, Adam Williamson wrote:
Hi, folks! A while ago, Xen virtualization functionality was added to the criteria and the validation test case set, on the understanding that Oracle would provide testing for it (and help fix bugs as they arose).
For the last couple of releases we really have not had any such testing
We had been doing the testing, it just that we (or rather me and Dariof) seem to get a wind of this at the last minute. Not sure exactly how to fix that thought.
Well, I mean, every few *days* a compose gets nominated for validation testing, and a mail is sent to test-announce. Just check your test- announce archives for mails with "nominated for testing" in their subject lines, and you'll see dozens. Is this not sufficient notification?
That is it. I just hadn't know about it.
from Oracle. On that basis, I'm proposing we remove this Final criterion:
s/Oracle/Xen Project/ I believe?
Perhaps, it's just that it always seemed to be you doing the testing, so they got a bit conflated :)
"The release must boot successfully as Xen DomU with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen."
and change the 'milestone' for the test case - https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Xen_Para_Virt - from Final to Optional.
Thoughts? Comments? Thanks!
I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested regularly
- not *only* on the final release candidate, right before we sign off
on the release. It needs to be tested regularly throughout the release cycle, on the composes that are "nominated for testing".
Right, which is why I am happy that you have pointed me to the right place so I can be up-to-date.
Thanks!
Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net
Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
On Thu, 2017-07-06 at 15:59 -0400, Konrad Rzeszutek Wilk wrote:
I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested regularly
- not *only* on the final release candidate, right before we sign off
on the release. It needs to be tested regularly throughout the release cycle, on the composes that are "nominated for testing".
Right, which is why I am happy that you have pointed me to the right place so I can be up-to-date.
Great, thanks. So let's leave it as it is for now, but we'll keep an eye on this during F27 cycle. If we get to, say, Beta and there are no results for the test, that's gonna be a problem. Thanks!
On Thu, 2017-07-06 at 13:19 -0700, Adam Williamson wrote:
On Thu, 2017-07-06 at 15:59 -0400, Konrad Rzeszutek Wilk wrote:
I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested regularly
- not *only* on the final release candidate, right before we sign off
on the release. It needs to be tested regularly throughout the release cycle, on the composes that are "nominated for testing".
Right, which is why I am happy that you have pointed me to the right place so I can be up-to-date.
Great, thanks. So let's leave it as it is for now, but we'll keep an eye on this during F27 cycle. If we get to, say, Beta and there are no results for the test, that's gonna be a problem. Thanks!
So, for Fedora 30, this was not tested throughout the whole cycle. I think we can consider the proposal to remove the criterion active again.
Since F24, I haven't seen or heard of anyone who uses Xen over KVM anywhere other than this thread... I'm +1 for making this test an "Optional" one.
Geoff Marr IRC: coremodule
On Fri, Apr 26, 2019 at 10:33 AM Adam Williamson adamwill@fedoraproject.org wrote:
On Thu, 2017-07-06 at 13:19 -0700, Adam Williamson wrote:
On Thu, 2017-07-06 at 15:59 -0400, Konrad Rzeszutek Wilk wrote:
I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested
regularly
- not *only* on the final release candidate, right before we sign off
on the release. It needs to be tested regularly throughout the
release
cycle, on the composes that are "nominated for testing".
Right, which is why I am happy that you have pointed me to the right place so I can be up-to-date.
Great, thanks. So let's leave it as it is for now, but we'll keep an eye on this during F27 cycle. If we get to, say, Beta and there are no results for the test, that's gonna be a problem. Thanks!
So, for Fedora 30, this was not tested throughout the whole cycle. I think we can consider the proposal to remove the criterion active again. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Yup +1 from my side too. Xen is hardly tested since a lot of time.
On Fri, Apr 26, 2019 at 10:07 PM Geoffrey Marr gmarr@redhat.com wrote:
Since F24, I haven't seen or heard of anyone who uses Xen over KVM anywhere other than this thread... I'm +1 for making this test an "Optional" one.
Geoff Marr IRC: coremodule
On Fri, Apr 26, 2019 at 10:33 AM Adam Williamson < adamwill@fedoraproject.org> wrote:
On Thu, 2017-07-06 at 13:19 -0700, Adam Williamson wrote:
On Thu, 2017-07-06 at 15:59 -0400, Konrad Rzeszutek Wilk wrote:
I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested
regularly
- not *only* on the final release candidate, right before we sign
off
on the release. It needs to be tested regularly throughout the
release
cycle, on the composes that are "nominated for testing".
Right, which is why I am happy that you have pointed me to the right place so I can be up-to-date.
Great, thanks. So let's leave it as it is for now, but we'll keep an eye on this during F27 cycle. If we get to, say, Beta and there are no results for the test, that's gonna be a problem. Thanks!
So, for Fedora 30, this was not tested throughout the whole cycle. I think we can consider the proposal to remove the criterion active again. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
+1
On Fri, Apr 26, 2019 at 6:53 PM Sumantro Mukherjee sumukher@redhat.com wrote:
Yup +1 from my side too. Xen is hardly tested since a lot of time.
On Fri, Apr 26, 2019 at 10:07 PM Geoffrey Marr gmarr@redhat.com wrote:
Since F24, I haven't seen or heard of anyone who uses Xen over KVM anywhere other than this thread... I'm +1 for making this test an "Optional" one.
Geoff Marr IRC: coremodule
On Fri, Apr 26, 2019 at 10:33 AM Adam Williamson < adamwill@fedoraproject.org> wrote:
On Thu, 2017-07-06 at 13:19 -0700, Adam Williamson wrote:
On Thu, 2017-07-06 at 15:59 -0400, Konrad Rzeszutek Wilk wrote:
> I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested
regularly
- not *only* on the final release candidate, right before we sign
off
on the release. It needs to be tested regularly throughout the
release
cycle, on the composes that are "nominated for testing".
Right, which is why I am happy that you have pointed me to the right place so I can be up-to-date.
Great, thanks. So let's leave it as it is for now, but we'll keep an eye on this during F27 cycle. If we get to, say, Beta and there are no results for the test, that's gonna be a problem. Thanks!
So, for Fedora 30, this was not tested throughout the whole cycle. I think we can consider the proposal to remove the criterion active again. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
-- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED https://redhat.com/trusted _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
On Fri, Apr 26, 2019 at 10:33 AM Adam Williamson adamwill@fedoraproject.org wrote:
On Thu, 2017-07-06 at 13:19 -0700, Adam Williamson wrote:
On Thu, 2017-07-06 at 15:59 -0400, Konrad Rzeszutek Wilk wrote:
I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested regularly
- not *only* on the final release candidate, right before we sign off
on the release. It needs to be tested regularly throughout the release cycle, on the composes that are "nominated for testing".
Right, which is why I am happy that you have pointed me to the right place so I can be up-to-date.
Great, thanks. So let's leave it as it is for now, but we'll keep an eye on this during F27 cycle. If we get to, say, Beta and there are no results for the test, that's gonna be a problem. Thanks!
So, for Fedora 30, this was not tested throughout the whole cycle. I think we can consider the proposal to remove the criterion active again.
Is this the criterion in question? https://fedoraproject.org/wiki/Fedora_30_Final_Release_Criteria#Xen_DomU
I'm +1 to dropping it for the Fedora 31 cycle.
On Sat, 2019-04-27 at 14:46 -0600, Chris Murphy wrote:
On Fri, Apr 26, 2019 at 10:33 AM Adam Williamson adamwill@fedoraproject.org wrote:
On Thu, 2017-07-06 at 13:19 -0700, Adam Williamson wrote:
On Thu, 2017-07-06 at 15:59 -0400, Konrad Rzeszutek Wilk wrote:
I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested regularly
- not *only* on the final release candidate, right before we sign off
on the release. It needs to be tested regularly throughout the release cycle, on the composes that are "nominated for testing".
Right, which is why I am happy that you have pointed me to the right place so I can be up-to-date.
Great, thanks. So let's leave it as it is for now, but we'll keep an eye on this during F27 cycle. If we get to, say, Beta and there are no results for the test, that's gonna be a problem. Thanks!
So, for Fedora 30, this was not tested throughout the whole cycle. I think we can consider the proposal to remove the criterion active again.
Is this the criterion in question? https://fedoraproject.org/wiki/Fedora_30_Final_Release_Criteria#Xen_DomU
Yes, that's the one.
On Thu, Jul 06, 2017 at 12:45:25PM -0700, Adam Williamson wrote:
This is only practical if it's going to be tested, and tested regularly
- not *only* on the final release candidate, right before we sign off
on the release. It needs to be tested regularly throughout the release cycle, on the composes that are "nominated for testing".
Yeah, in general, we need the RC validation testing to be a last sanity check, rather than the point where we discover all of the problems.
-
Adam Williamson -
Chris Murphy -
Geoffrey Marr -
Josef Skladanka -
Konrad Rzeszutek Wilk -
Matthew Miller -
Sumantro Mukherjee