Folks
We are getting closer to our announced RC date of 8/19 and what a great effort
in just last 2 weeks 260 issues were created and 340 were resolved and over 400
resolved issues were verified . The open blocker and critical count has come
down significantly and we have 2 blocker and 15 criti
gt; >
> > > > > > -Original Message-
> > > > > > From: Alex Huang [mailto:alex.hu...@citrix.com]
> > > > > > Sent: Tuesday, July 30, 2013 2:06 PM
> > > > > > To: dev@cloudstack.apache.org
> > > > > >
Folks
We are now 12 days from ACS 4.2 code RC on 8/19. There is vibrant activity in
filing and fixing issues. Incoming issue continue to be high resulting in
blockers and critical in 80+. In order to clear up our backlog I request you to
help out on aggressively fixing the issues. The unassi
o:chip.child...@sungard.com]
Sent: Wednesday, July 31, 2013 8:44 AM
To: dev@cloudstack.apache.org
Subject: Re: [ACS42] Release Status Update: After Code Freeze Next
Steps
On Thu, Aug 01, 2013 at 12:41:16AM +0900, Go Chiba wrote:
Does it already fixed all 4.2 docs?
If yes, I'd like to upda
CLOUDSTACK-645)
> Doc- Support Multiple Subnets per VLAN (CLOUDSTACK-788)
> Document the ability to use multiple IP ranges (CLOUDSTACK-702)
>
>
> Regards
> -Radhika
>
> -Original Message-
> From: Go Chiba [mailto:go.ch...@gmail.com]
> Sent: Thursday, August 01, 2013
ip.child...@sungard.com]
> > Sent: Wednesday, July 31, 2013 8:44 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [ACS42] Release Status Update: After Code Freeze Next
> > Steps
> >
> > On Thu, Aug 01, 2013 at 12:41:16AM +0900, Go Chiba wrote:
> > &
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Thursday, August 01, 2013 10:25 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [ACS42] Release Status Update: After Code Freeze Next Steps
>
> Besides doc being allowe
rg
> Subject: [ACS42] Release Status Update: After Code Freeze Next Steps
>
>
> Folks code freeze was on 7/29 and starting today we are moving ACS 42 into
> limited updates in preparation for RC on 8/19. Code changes are now
> limited to fixes to blocker and critical bugs only. I
On Thu, Aug 01, 2013 at 04:13:14PM +0200, Wido den Hollander wrote:
> On 07/30/2013 09:25 PM, Animesh Chaturvedi wrote:
> >
> >Folks code freeze was on 7/29 and starting today we are moving ACS 42 into
> >limited updates in preparation for RC on 8/19. Code changes are now limited
> >to fixes to b
On 07/30/2013 09:25 PM, Animesh Chaturvedi wrote:
Folks code freeze was on 7/29 and starting today we are moving ACS 42 into
limited updates in preparation for RC on 8/19. Code changes are now limited to
fixes to blocker and critical bugs only. I need to follow up on doc and
translations.
, July 31, 2013 8:44 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [ACS42] Release Status Update: After Code Freeze Next Steps
> >
> > On Thu, Aug 01, 2013 at 12:41:16AM +0900, Go Chiba wrote:
> > > Does it already fixed all 4.2 docs?
> > > If yes, I'
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Wednesday, July 31, 2013 8:44 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [ACS42] Release Status Update: After Code Freeze Next Steps
>
> On Thu, Aug 01, 2013 at 12:41:16AM
lex Huang [mailto:alex.hu...@citrix.com]
> > > > > Sent: Tuesday, July 30, 2013 2:06 PM
> > > > > To: dev@cloudstack.apache.org
> > > > > Subject: RE: [ACS42] Release Status Update: After Code Freeze Next
> > Steps
> >
+, Animesh Chaturvedi wrote:
> > >
> > >
> > > > -Original Message-
> > > > From: Alex Huang [mailto:alex.hu...@citrix.com]
> > > > Sent: Tuesday, July 30, 2013 2:06 PM
> > > > To: dev@cloudstack.apache.org
&g
esday, July 30, 2013 2:06 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: RE: [ACS42] Release Status Update: After Code Freeze Next Steps
> > >
> > > > The best type of commit for keeping things clean is a cherry-pick.
> > > > Merging into the relea
On Tue, Jul 30, 2013 at 10:03:08PM +, Animesh Chaturvedi wrote:
>
>
> > -Original Message-
> > From: Alex Huang [mailto:alex.hu...@citrix.com]
> > Sent: Tuesday, July 30, 2013 2:06 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [ACS42] Rele
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Tuesday, July 30, 2013 2:06 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [ACS42] Release Status Update: After Code Freeze Next Steps
>
> > The best type of commit for keeping
> The best type of commit for keeping things clean is a cherry-pick.
> Merging into the release branch is messy to track as the RM.
>
That should be a rule for release branches after code freeze.
--Alex
On Tue, Jul 30, 2013 at 07:25:14PM +, Animesh Chaturvedi wrote:
>
> Folks code freeze was on 7/29 and starting today we are moving ACS 42 into
> limited updates in preparation for RC on 8/19. Code changes are now limited
> to fixes to blocker and critical bugs only. I need to follow up on do
Folks code freeze was on 7/29 and starting today we are moving ACS 42 into
limited updates in preparation for RC on 8/19. Code changes are now limited to
fixes to blocker and critical bugs only. I need to follow up on doc and
translations.
There is a tremendous effort going on since last coup
Folks
We are now just 1 week from ACS 4.2 code freeze on 7/29. For the past 2 - 3
week there has been vibrant activity in filing and fixing issues. We have
managed to contain open defects to less than 400 but blockers and critical are
still in 90+. For the days remaining to code freeze, le
Hi John,
Oh, not yet...I am still working on one of your VMware issues. It should be
done today or tomorrow, I expect.
Thanks
On Thu, Jul 18, 2013 at 8:47 AM, John Burwell wrote:
> Mike,
>
> Have you posted the diff with the resolved second round issues for the
> SolidFire patch to Review Boa
Mike,
Have you posted the diff with the resolved second round issues for the
SolidFire patch to Review Board?
Thanks,
-John
On Jun 28, 2013, at 12:49 PM, Mike Tutkowski
wrote:
> Hi John,
>
> OK, this sounds good.
>
> I updated from master yesterday and was resolving some (major) conflicts
Folks
We are now just 2 weeks from ACS 4.2 code freeze on 7/29. For the past week
there has been vibrant activity in filing and fixing issues. 120 new issues
were created and 140 issues were resolved. We managed to contain open defects
to less than 400 but blockers and critical continue to r
Hi John,
OK, this sounds good.
I updated from master yesterday and was resolving some (major) conflicts
last night and this morning. I want to get in some more testing before I
commit.
Sounds good on the points you make. It should be, as you say, easy to
resolve them.
Thanks,
Mike
On Fri, Jun
Mike,
I (finally) completed the review of the patch. The TL;DR is that I am removing
my -1 on the patch so long as a supplemental patch that addresses the issues
raised is submitted to Review Board for a third review . The following items
are concern me, and must be addressed before release:
Hey John,
I know you were at a CloudStack Meetup today, but any thoughts on when we
are going to get Storage QoS (the SolidFire plug-in) merged into master?
Thanks!
On Wed, Jun 26, 2013 at 9:37 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:
> Folks
>
> The status for features o
Folks
The status for features or improvement is depicted in table below
|-+---+---|
| New Features / Improvements | This Week | TwoWeekAgo|
|-+---+---|
| Closed | 8 | 7 |
|
> -Original Message-
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Thursday, June 13, 2013 2:18 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [ACS42] Release Status Update
>
> So, "open" features are theoretically "in p
So, "open" features are theoretically "in progress" but simply not updated
in Jira?
On 6/12/13 4:46 PM, "Animesh Chaturvedi"
wrote:
>Folks
>
>
>The status for features or improvement is depicted in table below
>
>|-+---+---|
>| New Features / Improveme
Folks
The status for features or improvement is depicted in table below
|-+---+---|
| New Features / Improvements | This Week | Last Week |
|-+---+---|
| Closed | 7 | 6 |
> -Original Message-
> From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com]
> Sent: Thursday, June 06, 2013 4:30 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [ACS42] Release Status Update
>
> Animesh,
>
> Couple of things :
>
> - Thinking t
rvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Thursday, June 06, 2013 3:11 PM
To: dev@cloudstack.apache.org
Subject: [ACS42] Release Status Update
Folks
The new feature freeze date is 6/28 and the RC is 8/19
Out of 104 proposed features /improvements, the status is
|-+-|
Folks
The new feature freeze date is 6/28 and the RC is 8/19
Out of 104 proposed features /improvements, the status is
|-+-|
| New Features / Improvements | |
|-+-|
| Closed | 6 |
| Resolved
I would also like to close on the development of the systemvm. AFAIK, it
has been undergoing some level of validation. It is desirable to 'freeze'
the bits of the system vm image as early as possible.
The only 'unfreeze' I anticipate is when HAProxy returns to wheezy. As of
today the system vm con
Folks
We are 9 days from ACS 42 feature freeze
Out of 98 proposed features /improvements, the status is
Closed: 5
Resolved: 33
In Progress: 15
Reopened: 1:
Ready to review: 2
Open: 42
We have not made much progress in updating the tickets last week. Given that we
are just a few days away fro
Folks
We are 15 days from ACS 42 feature freeze
Out of 98 proposed features /improvements, the status is
Closed: 5
Resolved: 32
In Progress: 15
Reopened: 1:
Ready to review: 2
Open: 43
For the issues that are Open I will ask to take a moment to update the jira
items assigned to you with "In
37 matches
Mail list logo
