__
> From: Marcus Sorensen [shadow...@gmail.com]
> Sent: Friday, February 01, 2013 7:06 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Fwd: RE: [ACS41] Actions Required: Getting organized for 4.1.0
>
> I'm a little concerned that the schema change portion of cloudsta
@incubator.apache.org
Subject: Fwd: RE: [ACS41] Actions Required: Getting organized for 4.1.0
I'm a little concerned that the schema change portion of cloudstack-686
won't make it in... I assume this would have the same deadline as the
schema upgrade scripts are worked on after the cut. I ca
a to do so.
-- Forwarded message --
From: "Marcus Sorensen"
Date: Jan 31, 2013 12:15 PM
Subject: RE: [ACS41] Actions Required: Getting organized for 4.1.0
To: "Kishan Kavala"
Cc:
Were we going to get this into the 4.1 schema?
On Jan 24, 2013 3:40 AM, "Kishan Kaval
On Thu, Jan 3, 2013 at 4:38 PM, Chip Childers wrote:
> On Thu, Jan 3, 2013 at 4:29 PM, Alex Huang wrote:
>> How about leaving some time for us procrastinators on the west coast who
>> can't get up at 9a.m. to add a last minute feature? :)
>>
>> --Alex
>
> Oh geeze... I guess. ;-) How about 4
> Also, that reminds me... some of the long running branches (acl,
> events-framework, javelin) seem to be dependencies for some of the
> proposed features. Specifically, I can point to the events-framework
> branch and the snmp trap feature. Are folks planning on proposing
> those changes as pa
>
>Also, that reminds me... some of the long running branches (acl,
>events-framework, javelin) seem to be dependencies for some of the
>proposed features. Specifically, I can point to the events-framework
>branch and the snmp trap feature. Are folks planning on proposing
>those changes as part
From: Chip Childers [mailto:chip.child...@sungard.com]
>> Sent: Thursday, January 03, 2013 1:27 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [ACS41] Actions Required: Getting organized for 4.1.0
>>
>> Follow up reminder on the three actions listed below..
o: cloudstack-dev@incubator.apache.org
> Subject: Re: [ACS41] Actions Required: Getting organized for 4.1.0
>
> Follow up reminder on the three actions listed below...
>
> I'd like to call a freeze any further features / improvements being
> added to the 4.1.0 release *tomorr
Follow up reminder on the three actions listed below...
I'd like to call a freeze any further features / improvements being
added to the 4.1.0 release *tomorrow - mid day EST*.
We'll shift to a conversation about status and risk level for each
feature next week... pulling out those features that
t?
>
> ~kishan
>
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Thursday, 3 January 2013 11:59 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ACS41] Actions Required: Getting organized for 4.1.0
>
> Anyone willin
rs [mailto:chip.child...@sungard.com]
>> Sent: Wednesday, January 02, 2013 4:08 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: [ACS41] Actions Required: Getting organized for 4.1.0
>>
>> Hi all,
>>
>> As discussed previously [1], we're go
t;
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Thursday, 3 January 2013 11:59 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ACS41] Actions Required: Getting organized for 4.1.0
>
> Anyone willing to help me out
On Thu, Jan 3, 2013 at 1:08 AM, Mike Tutkowski
wrote:
> Hi everyone,
>
> I was wondering if we have a roadmap? I'm curious to know if a feature
> doesn't make it into this release when the following release is expected to
> come out (as a best case for thinking ahead to when features that don't g
3 4:08 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: [ACS41] Actions Required: Getting organized for 4.1.0
>
> Hi all,
>
> As discussed previously [1], we're going to start locking down the list of new
> features and improvements that are going to make it into
Subject: Re: [ACS41] Actions Required: Getting organized for 4.1.0
Anyone willing to help me out with 686? This was really a request for
assistance, outlining a simple change with pretty much exactly what I think
needs to be done, but got no response. I'm not sure who really to seek out fo
Anyone willing to help me out with 686? This was really a request for
assistance, outlining a simple change with pretty much exactly what I think
needs to be done, but got no response. I'm not sure who really to seek out
for it, which is why I opened the improvement.
On Jan 2, 2013 8:08 AM, "Chip C
Hi everyone,
I was wondering if we have a roadmap? I'm curious to know if a feature
doesn't make it into this release when the following release is expected to
come out (as a best case for thinking ahead to when features that don't go
into 4.1.0 might make it into a production CloudStack release)
Hi all,
As discussed previously [1], we're going to start locking down the
list of new features and improvements that are going to make it into
the 4.1.0 release. Our schedule has us wrapping up all new feature /
improvement development at the end of January, and obviously we need
to get organize
18 matches
Mail list logo
