Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-08-08 Thread Jessica Tomechak
gt; > > > > > > > -Original Message- > > > > > > From: Alex Huang [mailto:alex.hu...@citrix.com] > > > > > > Sent: Tuesday, July 30, 2013 2:06 PM > > > > > > To: dev@cloudstack.apache.org > > > > > >

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-08-02 Thread Wido den Hollander
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

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-08-02 Thread Dave Cahill
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

RE: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-08-01 Thread Radhika Puthiyetath
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: > > &

RE: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-08-01 Thread Animesh Chaturvedi
> -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

RE: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-08-01 Thread Animesh Chaturvedi
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

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-08-01 Thread Chip Childers
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

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-08-01 Thread Wido den Hollander
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.

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-08-01 Thread Go Chiba
, 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'

RE: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-07-31 Thread Animesh Chaturvedi
> -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

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-07-31 Thread Chip Childers
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 > >

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-07-31 Thread Go Chiba
+, 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

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-07-31 Thread Chip Childers
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

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-07-30 Thread Prasanna Santhanam
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

RE: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-07-30 Thread Animesh Chaturvedi
> -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

RE: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-07-30 Thread Alex Huang
> 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

Re: [ACS42] Release Status Update: After Code Freeze Next Steps

2013-07-30 Thread Chip Childers
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

[ACS42] Release Status Update: After Code Freeze Next Steps

2013-07-30 Thread Animesh Chaturvedi
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