RN just started, here are regular questions:
1. Do we need a new set of systemvmtemplate?
2. Any special consideration with 4.5?
3. Does new features from this filter is valid for the RN?
https://issues.apache.org/jira/browse/CLOUDSTACK-7739?filter=12329800
4. Does it really contain 188 fixed from
That sounds really good.
I can run my tests on RC0 then. If the vote for that one doesn't pass, I'm
always free then for subsequent RCs to view what's been checked in since
RC0 and determine if I think any of my tests should be re-run on the new RC.
Thanks
On Fri, Dec 5, 2014 at 6:58 PM, David N
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
wrote:
> Yeah, I'd love to wait
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 wrote:
>
> On Dec 5, 2014, at 3:58 PM, David Nalley wrote:
>
> > All of the test results I am aware of are on je
On Dec 5, 2014, at 3:58 PM, David Nalley 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
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.
I fully suspect we'll find issues with this first attempt.
On Fri, Dec 5, 2014 a
Yeah, now that we're getting really close on 4.5, I'd like to rerun my
regression tests early next week.
They're not all automated yet so it generally takes me 2 to 3 days.
On Friday, December 5, 2014, Sebastien Goasguen wrote:
> Did we report test results, upgrade paths.
> Are release notes re
Did we report test results, upgrade paths.
Are release notes ready ?
-Sebastien
> On 5 Dec 2014, at 05:16, David Nalley 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.
>
>
>
Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Thursday, December 04, 2014 8:17 PM
> To: dev@cloudstack.apache.org
> Subject: 4.5.0 status
>
> 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 r
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
On Fri, Sep 19, 2014 at 5:29 AM, David Nalley wrote
a lot of tl;dr
and then
:
> This likely
> means that we'll need a small army of quality fascists who take a
> serious interest in quality, and are liberal with vetoes and reverts
> until we get something that automates gating on quality.
>
On Thu, Sep 18, 2014 at 6:19 AM, Sebastien Goasguen wrote:
>
> On Sep 18, 2014, at 5:08 AM, Daan Hoogland wrote:
>
>> David,
>>
>> What do you plan to do after branching in terms of merge-back and or
>> cherry-picking. We are discussing here (Schuberg-Philis + Rohit + Ian +
>> Wido (+ Sebastien))
On 09/18/2014 11:08 AM, Daan Hoogland wrote:
> David,
>
> What do you plan to do after branching in terms of merge-back and or
> cherry-picking. We are discussing here (Schuberg-Philis + Rohit + Ian +
> Wido (+ Sebastien)) that we would like to branch after getting master
> stable and then when
On Sep 18, 2014, at 5:08 AM, Daan Hoogland wrote:
> David,
>
> What do you plan to do after branching in terms of merge-back and or
> cherry-picking. We are discussing here (Schuberg-Philis + Rohit + Ian +
> Wido (+ Sebastien)) that we would like to branch after getting master
> stable and then
David,
What do you plan to do after branching in terms of merge-back and or
cherry-picking. We are discussing here (Schuberg-Philis + Rohit + Ian +
Wido (+ Sebastien)) that we would like to branch after getting master
stable and then when the real release work is underway branching of 4.5.
All new
Hi folks,
4.3.1 is out the door now, so I am trying to get things lined up around 4.5.0.
Please consider us in feature freeze right now - and my plan is to
branch 4.5.0 this coming weekend. I'd like to see us hit code freeze
by end of October. Right now, we have 4 blocker bugs and 63 critical
bu
16 matches
Mail list logo
