IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin. It needs to be tested regularly throughout the releaseĬycle, on the composes that are "nominated for testing". not *only* on the final release candidate, right before we sign off This is only practical if it's going to be tested, and tested regularly > I would prefer for it to remain as it is. > and change the 'milestone' for the test case. > a functional, supported Xen Dom0 and widely used cloud providers
> "The release must boot successfully as Xen DomU with releases providing Perhaps, it's just that it always seemed to be you doing the testing, On that basis, I'm proposing we remove this Final Just check your test-Īnnounce archives for mails with "nominated for testing" in their Testing, and a mail is sent to test-announce. Well, I mean, every few *days* a compose gets nominated for validation > Dariof) seem to get a wind of this at the last minute. > We had been doing the testing, it just that we (or rather me and > For the last couple of releases we really have not had any such testing > that Oracle would provide testing for it (and help fix bugs as they
> the criteria and the validation test case set, on the understanding > Hi, folks! A while ago, Xen virtualization functionality was added to On Thu, at 15:13 -0400, Konrad Rzeszutek Wilk wrote:
0 kommentar(er)
