So my plan is to let the first RC sit for a few days before calling for a vote. Hopefully an RC being around for testing will be enough for folks to actually go do some testing.
We'll see how that works out. --David On Fri, Dec 5, 2014 at 5:58 PM, Mike Tutkowski <mike.tutkow...@solidfire.com> wrote: > Yeah, I'd love to wait for a formal RC before re-running automated and > manual tests, but sometimes 3 days isn't really long enough. > > On Fri, Dec 5, 2014 at 2:01 PM, Sebastien Goasguen <run...@gmail.com> wrote: > >> >> On Dec 5, 2014, at 3:58 PM, David Nalley <da...@gnsa.us> wrote: >> >> > All of the test results I am aware of are on jenkins.buildacloud.org >> > Generally, people don't start testing until we get RCs ready - hence >> > me trying to push out an RC. I want folks to start testing upgrade >> > paths, etc. >> >> it's one way to go, as long as we don't get frustrated if we re-spin >> several RCs. >> >> >> > >> > I fully suspect we'll find issues with this first attempt. >> > >> > On Fri, Dec 5, 2014 at 3:10 AM, Sebastien Goasguen <run...@gmail.com> >> wrote: >> >> Did we report test results, upgrade paths. >> >> Are release notes ready ? >> >> >> >> -Sebastien >> >> >> >>> On 5 Dec 2014, at 05:16, David Nalley <da...@gnsa.us> wrote: >> >>> >> >>> So we have no blockers currently logged, and are down to 15 critical >> >>> bugs. I am going to try and roll a 4.5.0 release candidate in the next >> >>> day or so. >> >>> >> >>> >> >>> >> >>> --David >> >> > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > <http://solidfire.com/solution/overview/?video=play>*™*
