The extension is welcome! -- Sent from the Delta quadrant using Borg technology!
Nux! www.nux.ro ----- Original Message ----- > From: "Boris Stoyanov" <boris.stoya...@shapeblue.com> > To: "dev" <dev@cloudstack.apache.org> > Sent: Wednesday, 17 January, 2018 18:24:20 > Subject: Re: [VOTE] Apache Cloudstack 4.11.0.0 (LTS) > Yes Rohit, tried other browser and I’m not able to login.. > > I’m +1 on the extend but unfortunately -1 cause of this blocker. > > Bobby. > > > boris.stoya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > On 17 Jan 2018, at 18:24, Rohit Yadav > <rohit.ya...@shapeblue.com<mailto:rohit.ya...@shapeblue.com>> wrote: > > The 72hrs window is more of a guideline than a rule, without lazy consensus I > don't think we've any choice here, so Monday it is. > > Kris - thanks, if we need RC2 and your proposed issues are blocker/critical we > can consider them so meanwhile engage with community to get them reviewed. > > Bobby - can you attempt login in incognito mode or in a different browser > after > upgrading to 4.11 from 4.5, rule out caching issue? > > Regards. > > Get Outlook for Android<https://aka.ms/ghei36> > > ________________________________ > From: Tutkowski, Mike > <mike.tutkow...@netapp.com<mailto:mike.tutkow...@netapp.com>> > Sent: Wednesday, January 17, 2018 8:48:28 PM > To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org> > Subject: Re: [VOTE] Apache Cloudstack 4.11.0.0 (LTS) > > Or perhaps just the first RC should have a longer window? > > On 1/17/18, 8:12 AM, "Tutkowski, Mike" > <mike.tutkow...@netapp.com<mailto:mike.tutkow...@netapp.com>> wrote: > > If all of our testing were completely in an automated fashion, then I would > agree that the 72-hour window is sufficient. However, we don’t have that > kind > of automated coverage and people aren’t always able to immediately begin > testing things out like migrating from their version of CloudStack to the > new > one. That being the case, 72 hours does seem (at least for where we are now > as > a project in terms of automated testing coverage) a bit short. > > On 1/17/18, 7:52 AM, "Daan Hoogland" > <daan.hoogl...@shapeblue.com<mailto:daan.hoogl...@shapeblue.com>> wrote: > > The 72 hours is to make sure all stakeholders had a chance to glance. > Testing is > supposed to have happened before. We have a culture of testing only > after > RC-cut which is part of the problem. The long duration of a single test > run > takes, is another part. And finally, in this case there is the new > mindblow > called meltdown. I think in general we should try to keep the 72 hours > but for > this release it is not realistic. > > On 17/01/2018, 15:48, "Rene Moser" > <m...@renemoser.net<mailto:m...@renemoser.net>> wrote: > > On 01/17/2018 03:34 PM, Daan Hoogland wrote: > People, People, > > a lot of us are busy with meltdown fixes and a full component test takes about > the 72 hours that we have for our voting, I propose to extend the vote period > until at least Monday. > > +1 > > I wonder where this 72 hours windows come from... Is it just be or, > based on the amount of changes and "things" to test, I would like to > expect a window in the size of 7-14 days ...? > > René > > > > daan.hoogl...@shapeblue.com<mailto:daan.hoogl...@shapeblue.com> > > www.shapeblue.com<http://www.shapeblue.com/><http://www.shapeblue.com<http://www.shapeblue.com/>> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > > > > > rohit.ya...@shapeblue.com<mailto:rohit.ya...@shapeblue.com> > www.shapeblue.com<http://www.shapeblue.com/> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue
