-Pradeep
>
>
>
>
>
> From: Mike Tutkowski
> To: "dev@cloudstack.apache.org" ; Pradeep
> Cloudstack
> Cc: Chiradeep Vittal ; Animesh Chaturvedi
>
> Sent: Thursday, March 20, 2014 10:34 AM
> Subject: Re: 4.4 Feature Freeze
>
>
Yes Mike
-Pradeep
From: Mike Tutkowski
To: "dev@cloudstack.apache.org" ; Pradeep Cloudstack
Cc: Chiradeep Vittal ; Animesh Chaturvedi
Sent: Thursday, March 20, 2014 10:34 AM
Subject: Re: 4.4 Feature Freeze
It looks like your code is e
Pradeep
>>
>>
>>
>>
>>
>> From: Sudha Ponnaganti
>> To: "dev@cloudstack.apache.org" ; Pradeep
>> Cloudstack ; Chiradeep Vittal <
>> chiradeep.vit...@citrix.com>; Animesh Chaturvedi <
>>
oudstack.apache.org" ; Pradeep
> Cloudstack ; Chiradeep Vittal <
> chiradeep.vit...@citrix.com>; Animesh Chaturvedi <
> animesh.chaturv...@citrix.com>
> Sent: Thursday, March 20, 2014 10:04 AM
> Subject: RE: 4.4 Feature Freeze
>
>
> It is too late already - All mer
; Chiradeep Vittal ;
Animesh Chaturvedi
Sent: Thursday, March 20, 2014 10:04 AM
Subject: RE: 4.4 Feature Freeze
It is too late already - All merges are done last week. It can go in to 4.5
(Master)
-Original Message-
From: Pradeep Cloudstack [mailto:pradeepcloudst...@yahoo.com]
Sent:
>
>
>
>
>
> From: Mike Tutkowski
> To: "dev@cloudstack.apache.org" ; Pradeep
> Cloudstack
> Sent: Thursday, March 20, 2014 9:52 AM
> Subject: Re: 4.4 Feature Freeze
>
>
> I'm not sure if we have a "code freeze
: 4.4 Feature Freeze
Hi Mike,
the following feature
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
is there under 4.4 Design documents.
How do I check if this feature is part of 4.4 ?
I had sent out a Proposal sometime back about this feature
-Pradeep
From: Mike Tutkowski
To: "dev@cloudstack.apache.org" ; Pradeep Cloudstack
Sent: Thursday, March 20, 2014 9:52 AM
Subject: Re: 4.4 Feature Freeze
I'm not sure if we have a "code freeze" per se, but "feature freeze" was
last week Friday. Technically all feat
ge-
> From: Marcus [mailto:shadow...@gmail.com]
> Sent: Friday, March 14, 2014 7:40 AM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> It may even just be a behavioral change or something simple I missed that
> is now required with a recent check-in. Obviou
issue is fixed.
As long as BVTs are good then it can be opened up for further check ins. Just
a suggestion.
-Original Message-
From: Marcus [mailto:shadow...@gmail.com]
Sent: Friday, March 14, 2014 7:40 AM
To: dev@cloudstack.apache.org
Subject: Re: 4.4 Feature Freeze
It may even just
onnaga...@citrix.com]
> Sent: Wednesday, March 19, 2014 5:46 PM
> To: dev@cloudstack.apache.org
> Cc: Hugo Trippaers (htrippa...@schubergphilis.com)
> Subject: [ACS 4.4] RE: 4.4 Feature Freeze
>
> Hi,
>
> I have copied one of the project pages from prior release for ACS 4.4[1]. Wi
[mailto:sudha.ponnaga...@citrix.com]
Sent: Tuesday, March 11, 2014 2:18 PM
To: dev@cloudstack.apache.org
Subject: RE: 4.4 Feature Freeze
Hugo,
Is it possible to setup Project page [1] on cwiki ? I am interested to post
some of the QA artifacts there related to ACS 4.4. I can also copy one from
prior
issue is
>> fixed. As long as BVTs are good then it can be opened up for further check
>> ins. Just a suggestion.
>>
>> -Original Message-
>> From: Marcus [mailto:shadow...@gmail.com]
>> Sent: Friday, March 14, 2014 7:40 AM
>> To: dev@cloudstack.apa
@cloudstack.apache.org
Subject: Re: 4.4 Feature Freeze
It may even just be a behavioral change or something simple I missed that is
now required with a recent check-in. Obviously I don't feel comfortable merging
in my feature branch though when I pull from master and can no longer run my
own fe
nal Message-
> From: Marcus [mailto:shadow...@gmail.com]
> Sent: Friday, March 14, 2014 7:40 AM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> It may even just be a behavioral change or something simple I missed that
> is now required with a recent check-in. Obviou
Marcus [mailto:shadow...@gmail.com]
>> Sent: Friday, March 14, 2014 6:36 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: 4.4 Feature Freeze
>>
>> Will be doing it today, however it seems that there have been some new
>> issues that have cropped up in master that break b
t; To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> Will be doing it today, however it seems that there have been some new
> issues that have cropped up in master that break basic functionality.
> I'm not sure if anyone should merge or not while that is the case.
, March 14, 2014 6:36 AM
To: dev@cloudstack.apache.org
Subject: Re: 4.4 Feature Freeze
Will be doing it today, however it seems that there have been some new issues
that have cropped up in master that break basic functionality.
I'm not sure if anyone should merge or not while that is the cas
Will be doing it today, however it seems that there have been some new
issues that have cropped up in master that break basic functionality.
I'm not sure if anyone should merge or not while that is the case. I
was attempting to validate that the latest merges played well in my
branch, but I couldn
On 11.03.2014 15:28, Hugo Trippaers wrote:
Hey guys,
I didn’t go and tally all the +1s and -1s for the shift of the
feature freeze, but with so many reactions i feel sticking to the
schedule is the only way to go. We should only change dates if there
is a consensus and there clearly is none at t
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> Hey guys,
>
> I didn't go and tally all the +1s and -1s for the shift of the feature
> freeze, but
> with so many reactions i feel sticking to the schedule is the only way to go.
> We should only change dates if
-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Tuesday, March 11, 2014 8:28 AM
To: dev@cloudstack.apache.org
Subject: Re: 4.4 Feature Freeze
Hey guys,
I didn't go and tally all the +1s and -1s for the shift of the feature freeze,
but with so
in.
>>
>> If that means that 4.4 needs to ship with fewer features. So be it
>>
>>
>>
>> Kind Regards
>> Giles
>>
>> D: +44 20 3603 0541 | M: +44 796 111 2055
>> giles.sir...@shapeblue.com
>>
>>
>>
>>
>> -Ori
Hey guys,
I didn’t go and tally all the +1s and -1s for the shift of the feature freeze,
but with so many reactions i feel sticking to the schedule is the only way to
go. We should only change dates if there is a consensus and there clearly is
none at the moment. Let’s take this discussion to t
> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com]
> Sent: Tuesday, March 04, 2014 4:45 AM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
>
> On Mar 3, 2014, at 8:18 PM, Animesh Chaturvedi
> wrote:
>
>
t: Re: 4.4 Feature Freeze
Animesh, You are doing a great job as guard on our present release and I don't
recall features slipping in either. instead those should now be added to the
master branch. If Sebastien made it sound that way it is probably because of
something else that is bot
age-
From: Sebastien Goasguen [mailto:run...@gmail.com]
Sent: 02 March 2014 18:08
To: dev@cloudstack.apache.org
Subject: Re: 4.4 Feature Freeze
On Feb 26, 2014, at 10:44 PM, Sudha Ponnaganti
wrote:
+1 to move feature freeze date in this case as 4.3 closure has impact on the
next release cycle.
les
>
> D: +44 20 3603 0541 | M: +44 796 111 2055
> giles.sir...@shapeblue.com
>
>
>
>
> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com]
> Sent: 02 March 2014 18:08
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Free
oudstack.apache.org
Subject: Re: 4.4 Feature Freeze
On Feb 26, 2014, at 10:44 PM, Sudha Ponnaganti
wrote:
> +1 to move feature freeze date in this case as 4.3 closure has impact on the
> next release cycle. There are 14 features targeted for 4.4 and all of them
> are in open stat
> From: Sebastien Goasguen [mailto:run...@gmail.com]
>>> Sent: Sunday, March 02, 2014 10:13 AM
>>> To: dev@cloudstack.apache.org
>>> Subject: Re: 4.4 Feature Freeze
>>>
>>> My take is that we are slipping on RC and re-voting because we are forcing
>&g
On Mar 3, 2014, at 8:18 PM, Animesh Chaturvedi
wrote:
>
>
>> -Original Message-
>> From: Sebastien Goasguen [mailto:run...@gmail.com]
>> Sent: Sunday, March 02, 2014 10:13 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: 4.4 Feature Freeze
>&
This list is not containing CLOUDSTACK-6105
Looks like I did not set Fix Versions Properly for this ticket..
Thanks & Regards
Damodar/
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Friday, February 28, 2014 7:40 PM
To:
Subject: Re: 4.4 Feature Freeze
i&#
Daan,
Since you are the 4.4 RM we will respect your decision.
-abhi
On 03/03/14 2:11 pm, "Daan Hoogland" wrote:
>Abhinandan, first one compromis-proposal, please.
>
>Can we not postpone but allow for this one feature (CLOUDSTACK-6161)
>this one time (4.4) to go in after feature freeze. If
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Friday, February 28, 2014 6:10 AM
To:
Subject: Re: 4.4 Feature Freeze
i'm all for being flexible, but i find a lot of the arguments used here
debatable.
"It causes developers to rush their development t
> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com]
> Sent: Sunday, March 02, 2014 10:13 AM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> My take is that we are slipping on RC and re-voting because we are forcing
&g
Behalf Of Hugo Trippaers
Sent: Friday, February 28, 2014 6:10 AM
To:
Subject: Re: 4.4 Feature Freeze
i'm all for being flexible, but i find a lot of the arguments used here
debatable.
"It causes developers to rush their development to meet the deadline." This
will happen anyway, e
e these rock solid and
well documented features for 4.5
> Regards,
> Devdeep
>
>
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Friday, February 28, 2014 7:40 PM
> To:
> Subject: Re: 4.4 Feature Freeze
>
> i’m all for being flexib
7:40 PM
To:
Subject: Re: 4.4 Feature Freeze
i'm all for being flexible, but i find a lot of the arguments used here
debatable.
"It causes developers to rush their development to meet the deadline." This
will happen anyway, every time we've extended the deadline we got new f
Abhinandan, first one compromis-proposal, please.
Can we not postpone but allow for this one feature (CLOUDSTACK-6161)
this one time (4.4) to go in after feature freeze. If this is the only
one and we don't consider this jurisprudence we could allow for it.
@Hugo: say what?
On Mon, Mar 3, 2014
I think there is no consensus on feature freeze date yet ?
Daan,
Shall we call for a vote on this ?
-abhi
On 03/03/14 6:11 am, "Mike Tutkowski" wrote:
>I believe March 14th is Feature Freeze and, as such, when the 4.4 branch
>is
>cut.
>
>
>On Sun, Mar 2, 2014 at 11:12 AM, Sebastien Goasguen
>
On Fri, Feb 28, 2014 at 7:39 PM, Hugo Trippaers wrote:
>
> This is the list of current features targeted for 4.4 according to our
> Jira. Which features would be impacted if we don't move the feature freeze?
>
> [image: New Feature] CLOUDSTACK-6161
> distributed routing and network ACL with OVS p
One serious problem we are having at the time being is the inability to add
XenServer hosts to CloudStack 4.4.
Does anyone know of a solution or workaround for this as it is probably
blocking development for several people?
https://issues.apache.org/jira/browse/CLOUDSTACK-6193
On Sun, Mar 2, 20
On that note, we need to be careful *how* we merge features, otherwise
it can be painful to revert.
On Sun, Mar 2, 2014 at 11:12 AM, Sebastien Goasguen wrote:
>
> On Feb 28, 2014, at 9:09 AM, Hugo Trippaers wrote:
>
>> i'm all for being flexible, but i find a lot of the arguments used here
>> d
I believe March 14th is Feature Freeze and, as such, when the 4.4 branch is
cut.
On Sun, Mar 2, 2014 at 11:12 AM, Sebastien Goasguen wrote:
>
> On Feb 28, 2014, at 9:09 AM, Hugo Trippaers wrote:
>
> > i'm all for being flexible, but i find a lot of the arguments used here
> debatable.
> >
> > "
On Feb 28, 2014, at 9:09 AM, Hugo Trippaers wrote:
> i’m all for being flexible, but i find a lot of the arguments used here
> debatable.
>
> “It causes developers to rush their development to meet the deadline." This
> will happen anyway, every time we’ve extended the deadline we got new
>
ginal Message-
> From: John Kinsella [mailto:j...@stratosec.co]
> Sent: Wednesday, February 26, 2014 7:22 PM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> I don't see not moving the freeze date as a penalty. If a feature doesn't
> make t
I don't know. I do think we should stick to a schedule, but I also
think that the track record has shown that there are far too many
features stuffed into our releases to have such short release cycles.
Part of the point of short release cycles (assuming you consider 4
months to be short, with a ch
As Mike said, due to our long RC process, maintain the original
timeline is basically means PENALTY for people working on current
release: if people works on testing/fixing the previous release, then
the time left for them into new release would be much shorter. In our
current case, likely 2 weeks.
[mailto:mike.tutkow...@solidfire.com]
Sent: Friday, February 28, 2014 3:31 PM
To: dev@cloudstack.apache.org
Subject: Re: 4.4 Feature Freeze
Again...it's not going to break my heart personally if we keep the current
feature freeze date or not (my code should be in soon), but I do think we nee
Again...it's not going to break my heart personally if we keep the current
feature freeze date or not (my code should be in soon), but I do think we
need to get a bit real if we expect anyone who's working on a future
release to help out testing RC builds.
I expect most people would prefer you hel
tch...@shapeblue.com
-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: 28 February 2014 20:13
To: dev@cloudstack.apache.org
Subject: Re: 4.4 Feature Freeze
I agree that postponing should not be the norm.
I think we need to figure out from a process standpo
I’m completely in-line with Hugo on this. Was actually going to make similar
comments about the…solidness of the arguments to move.
On Feb 28, 2014, at 6:09 AM, Hugo Trippaers
mailto:h...@trippaers.nl>> wrote:
i’m all for being flexible, but i find a lot of the arguments used here
debatable.
> make the current deadline, it moves to the next release, which is
> > > still a
> > > > > few months away. For significant issues, it's not uncommon for us
> to
> > > > allow
> > > > > them in late.
> > > > >
> > > >
shifting a date, by several
> > orders
> > > > of magnitude, is understanding why the RC process took so long and
> what
> > > we
> > > > can do in the future to make that not so painful.
> > > >
> > > > For the record I'm +0 on moving the fe
> > > John
> > >
> > > On Feb 26, 2014, at 7:10 PM, Ram Ganesh wrote:
> > >
> > > > I share it too. Many developers in the community went out of their
> way
> > > to get a cleaner RC and thereby impacting their feature development
&g
process took so long and
>>what
>> we
>> > can do in the future to make that not so painful.
>> >
>> > For the record I'm +0 on moving the feature freeze date.
>> >
>> > John
>> >
>> > On Feb 26, 2014, at 7:10 PM, Ram G
; to get a cleaner RC and thereby impacting their feature development
> > efforts. We shouldn't be penalizing them with this 2 week's feature
> freeze
> > schedule
> > >
> > > Thanks,
> > > RamG
> > >
> > >> -Original Message
i’m all for being flexible, but i find a lot of the arguments used here debatable.“It causes developers to rush their development to meet the deadline." This will happen anyway, every time we’ve extended the deadline we got new features coming in at the last minute. Actually i’m under the impressio
t; -Original Message-
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: 28 February 2014 01:27
>> To: dev@cloudstack.apache.org
>> Subject: Re: 4.4 Feature Freeze
>>
>> I'm not sure I would say that not moving the feature-freeze date
On Fri, Feb 28, 2014 at 07:26:10AM +, Ram Ganesh wrote:
> Yes. I can only agree with you on this. When we come up with dates
> we have to be cognizant about slips in prior releases (we had 6 RC
> re-spins and counting) which would have had impact which is the
> case now. We have to be bit
nal Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: 28 February 2014 01:27
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> I'm not sure I would say that not moving the feature-freeze date is a penalty,
> but it does have co
; efforts. We shouldn't be penalizing them with this 2 week's feature freeze
> schedule
> >
> > Thanks,
> > RamG
> >
> >> -Original Message-
> >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> >> Sent: 27 February 2014 03:00
>
later!
-Original Message-
From: Marcus [mailto:shadow...@gmail.com]
Sent: Thursday, February 27, 2014 10:54 AM
To: dev@cloudstack.apache.org
Subject: Re: 4.4 Feature Freeze
Perhaps we just need to reduce overlap. Most people work on 4.3 until it's out
the door, I think. Personally, I h
the community went out of their way
>> > to get a cleaner RC and thereby impacting their feature development
>> > efforts. We shouldn't be penalizing them with this 2 week's feature
>> > freeze schedule
>> >
>> > Thanks,
>> > RamG
>>
Sent: 27 February 2014 08:52
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> I don't see not moving the freeze date as a penalty. If a feature doesn't
> make the current deadline, it moves to the next release, which is still a few
> months away. For significant
results in poor
quality code.
Thanks
/sudha
-Original Message-
From: John Kinsella [mailto:j...@stratosec.co]
Sent: Wednesday, February 26, 2014 7:22 PM
To: dev@cloudstack.apache.org
Subject: Re: 4.4 Feature Freeze
I don't see not moving the freeze date as a penalty. If a feature do
Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> Sent: 27 February 2014 03:00
>> To: dev@cloudstack.apache.org
>> Subject: RE: 4.4 Feature Freeze
>>
>> Mike I share your opinion most of us have been pretty much on 4.3 until
>> now, and pushing out the re
imesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: 27 February 2014 03:00
> To: dev@cloudstack.apache.org
> Subject: RE: 4.4 Feature Freeze
>
> Mike I share your opinion most of us have been pretty much on 4.3 until
> now, and pushing out the release seems reasonable.
nal Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Wednesday, February 26, 2014 7:29 AM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> I think we're having this discussion after every release because we're
> begi
a single go.
> >>
> >> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star wrote:
> >>> +1
> >>>
> >>>
> >>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> >> abhinandan.prat...@citrix.com
> >>>> :
> >>>
> >>
;>
>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>> abhinandan.prat...@citrix.com
>>>> :
>>>
>>>> +1 for 4.4 feature freeze on 3/28.
>>>>
>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>>>>
gt;
> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star wrote:
> > +1
> >
> >
> > 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> abhinandan.prat...@citrix.com
> >>:
> >
> >> +1 for 4.4 feature freeze on 3/28.
> >>
> >>
ek >:
>
>> +1 for 4.4 feature freeze on 3/28.
>>
>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>> wrote:
>>
>> >> -Original Message-
>> >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> >> Sen
+1
2014-02-26 20:01 GMT+08:00 Abhinandan Prateek :
> +1 for 4.4 feature freeze on 3/28.
>
> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> wrote:
>
> >> -Original Message-
> >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>
+1 for 4.4 feature freeze on 3/28.
On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
wrote:
>> -Original Message-
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: 26 February 2014 04:46
>> To: dev@cloudstack.apache.org
>> Subjec
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: 26 February 2014 04:46
> To: dev@cloudstack.apache.org
> Subject: Re: 4.4 Feature Freeze
>
> I think this is a good idea, Animesh (to push out feature freeze to 3/28).
+1 to mo
feature freeze to 3/28 from 3/14
> and all the other dates likewise.
>
>
> Thanks
> Animesh
>
> > -Original Message-
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > Sent: Tuesday, February 25, 2014 1:05 PM
> > To: dev@cloudsta
out feature freeze to 3/28 from 3/14 and
all the other dates likewise.
Thanks
Animesh
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Tuesday, February 25, 2014 1:05 PM
> To: dev@cloudstack.apache.org
> Subject: RE: 4.4
f Hugo Trippaers
> Sent: Tuesday, February 25, 2014 8:50 AM
> To:
> Subject: Re: 4.4 Feature Freeze
>
> Hey,
>
> If we stick to our 4 month release schedule the feature freeze is four months
> after the feature freeze of 4.3. The feature freeze of 4.3 was 8 Nov 2013.
>
>
>> Cheers,
>>>
>>> Hugo
>>>
>>>
>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am also looking for feature freeze dates for 4.4. Can RM post those?
>>
king for feature freeze dates for 4.4. Can RM post those?
>>>
>>> Thanks
>>> /Sudha
>>>
>>> -Original Message-
>>> From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
>>> Sent: Tuesday, February 25, 2014 7:00 AM
>>> To
> >
> > Cheers,
> >
> > Hugo
> >
> >
> > On 25 feb. 2014, at 16:35, Sudha Ponnaganti >
> > wrote:
> >
> > > Hi,
> > >
> > > I am also looking for feature freeze dates for 4.4. Can RM post those?
> > >
>
t; > /Sudha
> >
> > -Original Message-
> > From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
> > Sent: Tuesday, February 25, 2014 7:00 AM
> > To: dev@cloudstack.apache.org
> > Subject: 4.4 Feature Freeze
> >
> > All,
> >
> &
post those?
>>
>> Thanks
>> /Sudha
>>
>> -Original Message-
>> From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
>> Sent: Tuesday, February 25, 2014 7:00 AM
>> To: dev@cloudstack.apache.org
>> Subject: 4.4 Feature Freeze
>>
essage-
> From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
> Sent: Tuesday, February 25, 2014 7:00 AM
> To: dev@cloudstack.apache.org
> Subject: 4.4 Feature Freeze
>
> All,
>
> I know the 4.3 isn't quite out the door yet, but is there a timetable
> somewhere
Hi,
I am also looking for feature freeze dates for 4.4. Can RM post those?
Thanks
/Sudha
-Original Message-
From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
Sent: Tuesday, February 25, 2014 7:00 AM
To: dev@cloudstack.apache.org
Subject: 4.4 Feature Freeze
All,
I know the 4.3
All,
I know the 4.3 isn't quite out the door yet, but is there a timetable somewhere
stating when the feature freeze for 4.4 will be?
I would like to submit a feature and want to ensure that It's prepared in time.
Many thanks,
Alex
Regards,
Alex Hitchins
VP Software Engineering
D: +44 1892
87 matches
Mail list logo
