On Sun, Oct 7, 2012 at 6:35 PM, Alex Huang <alex.hu...@citrix.com> wrote:
> > I have. I think the biggest problem I had with the guide and the VOTE > example you gave on IRC was that it seemed like a VOTE is also a call for > testing because in the email, it seemed you're supposed to VOTE after you > tried out the test procedure. So I jumped a bit on the VOTE call on > Friday, thinking we're late on calling for people to test. Brett gave a > detail explanation why that's not the case. We're currently waiting for > all of the tests to wrap up before calling for a VOTE. Other items, such > as release notes, NEWS, NOTICE, etc, have been assigned to various people > to do. You should find that as tasks on CloudStack's Jira. Ah, I can see your confusion. Yeah, the testing you do as part of a release is a formality, really. You should only call it when you expect it all to work. And the release testing is more about testing the actual release itself. (Though, if you have integrated tests, then those will be included too, as part of "make check" or the equivalent.) Thanks, -- NS
