You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Alex Hitchins <al...@shapeblue.com> on 2014/02/25 15:59:42 UTC
4.4 Feature Freeze
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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M: +44<tel:+447968161581> 7788 423 969
ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments.
Apache CloudStack Bootcamp training courses
**NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/>
18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/>
17th-23rd March 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
24th-28th March 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
16th-20th June 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
23rd-27th June 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
RE: 4.4 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo Trippaers
Sent: Friday, February 28, 2014 6:10 AM
To: <de...@cloudstack.apache.org>
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 features coming in at the last minute. Actually i'm under the impression that when we move the deadline people will actually try to get more features in instead of working on stabilizing existing features.
[Animesh] Keep a feature freeze deadline closer don't extend it too far out. That's what we did for 4.3 when 4.2 took longer then planned.
"We can't deliver features on the roadmap." There is validity to this point, but on the other hand we already know the entire release schedule way ahead, this feature freeze date should not come as a surprise. But as i mentioned in an earlier mail, lets have this discussion. Post which features might not make it into the release so we can have a discussion if we should slip the release date to get this feature in. I think we all now that there are commercial parties working with this software to build releases and have customers demanding features, but if we don't discuss that on list it's hard for us to take it into account.
[Animesh] I agree with you but I think the PROPOSAL expectation is to have FS ready, with most folks working on 4.3 they did not have sufficient time to finish it up.
"Feature freeze wasn't called" True, i wasn't even aware that this was a requirement. We should add this to the procedure here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so release managers know this is expected of them. It should not impact the dates as the dates are already fixed by the release schedule (every 4 months)
I'm still -1 on extending the feature freeze. I would rather extend the test/stability phase to we have some more time to fix issues before we get into the RC spinning.
[Animesh] Hugo one thing I do want to call out which David and I discussed today offline was if several of these features do not make into 4.4 many of these folks will move onto working on these in master and as a community we will not have the full focus on 4.4 as we should have for the current release. IMHO 2 weeks is a reasonable compromise after all of these folks were working hard on 4.3.
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?
ASF JIRA
Project: CloudStack
Type: New Feature
Fix Version: 4.4.0
Resolution: Unresolved
Sorted by: Updated descending
1-15 of 15 as at: 28/Feb/14 15:07
T Key Summary Assignee Reporter P Status Resolution Created Updated Due
[New Feature] CLOUDSTACK-6181
Root resize
Unassigned Nux [Major] [Open] Open Unresolved 27/Feb/14 27/Feb/14
[New Feature] CLOUDSTACK-6161
distributed routing and network ACL with OVS plug-in
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 24/Feb/14 24/Feb/14
[New Feature] CLOUDSTACK-6092
Storage OverProvisioning as a Per Primary Basis
Saksham Srivastava Saksham Srivastava [Major] [Open] Open Unresolved 13/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6144
HA for guest VMs running Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6143
Storage Live-Migration support for Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6142
Zone Wide Primary Store in Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6104
PVLAN support for CloudStack deployment over Nexus 1000v in VMware environment
Sateesh Chodapuneedi Sateesh Chodapuneedi [Major] [Open] Open Unresolved 14/Feb/14 15/Feb/14
[New Feature] CLOUDSTACK-6109
Support of iSCSI as primary store in Hyper-V
Rajesh Battala Rajesh Battala [Major] [Open] Open Unresolved 14/Feb/14 14/Feb/14
[New Feature] CLOUDSTACK-6106
Support of VPC in HyperV
Rajesh Battala Rajesh Battala [Major] [Open] Open Unresolved 14/Feb/14 14/Feb/14
[New Feature] CLOUDSTACK-6090
Virtual Router Service Failure Alerting
Harikrishna Patnala Harikrishna Patnala [Major] [Open] Open Unresolved 13/Feb/14 13/Feb/14
[New Feature] CLOUDSTACK-6052
List VM enhancement to support querying with multiple VM IDs
Koushik Das Koushik Das [Major] [Open] Open Unresolved 07/Feb/14 07/Feb/14
[New Feature] CLOUDSTACK-5569
enhance OVS plug-in to support region level VPC and guest networks that span zones
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5568
introduce notion of guest network that spans multiple zones
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5567
enable VPC at region level
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5398
Cloudstack network-element plugin to orchestrate Juniper's switches
Unassigned Pradeep H Krishnamurthy [Major] [Open] Open Unresolved 06/Dec/13 06/Dec/13
Cheers,
Hugo
On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org>> wrote:
On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
But you do agree that the re-spins uncovered bugs/issues that needed
to be fixed? Is it perhaps a mismatch in when the artifacts start
getting tested by the users+devs as opposed to when company-x might be
satisfied with their testing? More than 90% of the re-spins are
bugs/issues uncovered by users who needed RC candidates and weren't
testing artifacts on a daily basis (I could be wrong here). I don't
think someone with a large test engineering team would wait for the
RCs to get rolling. May be if we addressed that mismatch in timing we
could have smaller RC phases. Something like a soft-freeze and a
hard-freeze.
post soft-freeze : users+devs do a daily test (mostly manually for
features they care about)
post hard-freeze : everyone only looks at a daily automated test
report and if all looks good, we release?
--
Prasanna.,
------------------------
Powered by BigRock.com<http://BigRock.com>
RE: 4.4 Feature Freeze
Posted by Prachi Damle <Pr...@citrix.com>.
Hugo,
Just wanted to inform that myself and Min had proposed https://issues.apache.org/jira/browse/CLOUDSTACK-5920
which was not listed below due to wrong ticket type it had.
I updated the type and now it should show in your list.
Thanks,
Prachi
From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo Trippaers
Sent: Friday, February 28, 2014 6:10 AM
To: <de...@cloudstack.apache.org>
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 features coming in at the last minute. Actually i'm under the impression that when we move the deadline people will actually try to get more features in instead of working on stabilizing existing features.
"We can't deliver features on the roadmap." There is validity to this point, but on the other hand we already know the entire release schedule way ahead, this feature freeze date should not come as a surprise. But as i mentioned in an earlier mail, lets have this discussion. Post which features might not make it into the release so we can have a discussion if we should slip the release date to get this feature in. I think we all now that there are commercial parties working with this software to build releases and have customers demanding features, but if we don't discuss that on list it's hard for us to take it into account.
"Feature freeze wasn't called" True, i wasn't even aware that this was a requirement. We should add this to the procedure here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so release managers know this is expected of them. It should not impact the dates as the dates are already fixed by the release schedule (every 4 months)
I'm still -1 on extending the feature freeze. I would rather extend the test/stability phase to we have some more time to fix issues before we get into the RC spinning.
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?
ASF JIRA
Project: CloudStack
Type: New Feature
Fix Version: 4.4.0
Resolution: Unresolved
Sorted by: Updated descending
1-15 of 15 as at: 28/Feb/14 15:07
T Key Summary Assignee Reporter P Status Resolution Created Updated Due
[New Feature] CLOUDSTACK-6181
Root resize
Unassigned Nux [Major] [Open] Open Unresolved 27/Feb/14 27/Feb/14
[New Feature] CLOUDSTACK-6161
distributed routing and network ACL with OVS plug-in
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 24/Feb/14 24/Feb/14
[New Feature] CLOUDSTACK-6092
Storage OverProvisioning as a Per Primary Basis
Saksham Srivastava Saksham Srivastava [Major] [Open] Open Unresolved 13/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6144
HA for guest VMs running Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6143
Storage Live-Migration support for Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6142
Zone Wide Primary Store in Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6104
PVLAN support for CloudStack deployment over Nexus 1000v in VMware environment
Sateesh Chodapuneedi Sateesh Chodapuneedi [Major] [Open] Open Unresolved 14/Feb/14 15/Feb/14
[New Feature] CLOUDSTACK-6109
Support of iSCSI as primary store in Hyper-V
Rajesh Battala Rajesh Battala [Major] [Open] Open Unresolved 14/Feb/14 14/Feb/14
[New Feature] CLOUDSTACK-6106
Support of VPC in HyperV
Rajesh Battala Rajesh Battala [Major] [Open] Open Unresolved 14/Feb/14 14/Feb/14
[New Feature] CLOUDSTACK-6090
Virtual Router Service Failure Alerting
Harikrishna Patnala Harikrishna Patnala [Major] [Open] Open Unresolved 13/Feb/14 13/Feb/14
[New Feature] CLOUDSTACK-6052
List VM enhancement to support querying with multiple VM IDs
Koushik Das Koushik Das [Major] [Open] Open Unresolved 07/Feb/14 07/Feb/14
[New Feature] CLOUDSTACK-5569
enhance OVS plug-in to support region level VPC and guest networks that span zones
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5568
introduce notion of guest network that spans multiple zones
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5567
enable VPC at region level
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5398
Cloudstack network-element plugin to orchestrate Juniper's switches
Unassigned Pradeep H Krishnamurthy [Major] [Open] Open Unresolved 06/Dec/13 06/Dec/13
Cheers,
Hugo
On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org>> wrote:
On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
But you do agree that the re-spins uncovered bugs/issues that needed
to be fixed? Is it perhaps a mismatch in when the artifacts start
getting tested by the users+devs as opposed to when company-x might be
satisfied with their testing? More than 90% of the re-spins are
bugs/issues uncovered by users who needed RC candidates and weren't
testing artifacts on a daily basis (I could be wrong here). I don't
think someone with a large test engineering team would wait for the
RCs to get rolling. May be if we addressed that mismatch in timing we
could have smaller RC phases. Something like a soft-freeze and a
hard-freeze.
post soft-freeze : users+devs do a daily test (mostly manually for
features they care about)
post hard-freeze : everyone only looks at a daily automated test
report and if all looks good, we release?
--
Prasanna.,
------------------------
Powered by BigRock.com<http://BigRock.com>
Re: 4.4 Feature Freeze
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Mar 3, 2014, at 5:34 AM, Devdeep Singh <de...@citrix.com> wrote:
> I was looking into adding support for iSCSI (CLOUDSTACK-6109) and HA of guest vms (CLOUDSTACK-6144) for hyper-v. I don’t think I’ll be able to finish it by 14th.
>
then it looks like you will have plenty of time to make these rock solid and well documented features for 4.5
> Regards,
> Devdeep
>
>
> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Friday, February 28, 2014 7:40 PM
> To: <de...@cloudstack.apache.org>
> 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 features coming in at the last minute. Actually i’m under the impression that when we move the deadline people will actually try to get more features in instead of working on stabilizing existing features.
>
> “We can’t deliver features on the roadmap.” There is validity to this point, but on the other hand we already know the entire release schedule way ahead, this feature freeze date should not come as a surprise. But as i mentioned in an earlier mail, lets have this discussion. Post which features might not make it into the release so we can have a discussion if we should slip the release date to get this feature in. I think we all now that there are commercial parties working with this software to build releases and have customers demanding features, but if we don’t discuss that on list it’s hard for us to take it into account.
>
> “Feature freeze wasn’t called” True, i wasn’t even aware that this was a requirement. We should add this to the procedure here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so release managers know this is expected of them. It should not impact the dates as the dates are already fixed by the release schedule (every 4 months)
>
>
> I’m still -1 on extending the feature freeze. I would rather extend the test/stability phase to we have some more time to fix issues before we get into the RC spinning.
>
>
> 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?
>
> ASF JIRA
> Project: CloudStack
> Type: New Feature
> Fix Version: 4.4.0
> Resolution: Unresolved
> Sorted by: Updated descending
> 1–15 of 15 as at: 28/Feb/14 15:07
> T Key Summary Assignee Reporter P Status Resolution Created Updated Due
> CLOUDSTACK-6181
> Root resize
> Unassigned Nux Open Unresolved 27/Feb/14 27/Feb/14
> CLOUDSTACK-6161
> distributed routing and network ACL with OVS plug-in
> Murali Reddy Murali Reddy Open Unresolved 24/Feb/14 24/Feb/14
> CLOUDSTACK-6092
> Storage OverProvisioning as a Per Primary Basis
> Saksham Srivastava Saksham Srivastava Open Unresolved 13/Feb/14 20/Feb/14
> CLOUDSTACK-6144
> HA for guest VMs running Hyper-V
> Unassigned Rajesh Battala Open Unresolved 20/Feb/14 20/Feb/14
> CLOUDSTACK-6143
> Storage Live-Migration support for Hyper-V
> Unassigned Rajesh Battala Open Unresolved 20/Feb/14 20/Feb/14
> CLOUDSTACK-6142
> Zone Wide Primary Store in Hyper-V
> Unassigned Rajesh Battala Open Unresolved 20/Feb/14 20/Feb/14
> CLOUDSTACK-6104
> PVLAN support for CloudStack deployment over Nexus 1000v in VMware environment
> Sateesh Chodapuneedi Sateesh Chodapuneedi Open Unresolved 14/Feb/14 15/Feb/14
> CLOUDSTACK-6109
> Support of iSCSI as primary store in Hyper-V
> Rajesh Battala Rajesh Battala Open Unresolved 14/Feb/14 14/Feb/14
> CLOUDSTACK-6106
> Support of VPC in HyperV
> Rajesh Battala Rajesh Battala Open Unresolved 14/Feb/14 14/Feb/14
> CLOUDSTACK-6090
> Virtual Router Service Failure Alerting
> Harikrishna Patnala Harikrishna Patnala Open Unresolved 13/Feb/14 13/Feb/14
> CLOUDSTACK-6052
> List VM enhancement to support querying with multiple VM IDs
> Koushik Das Koushik Das Open Unresolved 07/Feb/14 07/Feb/14
> CLOUDSTACK-5569
> enhance OVS plug-in to support region level VPC and guest networks that span zones
> Murali Reddy Murali Reddy Open Unresolved 19/Dec/13 19/Dec/13
> CLOUDSTACK-5568
> introduce notion of guest network that spans multiple zones
> Murali Reddy Murali Reddy Open Unresolved 19/Dec/13 19/Dec/13
> CLOUDSTACK-5567
> enable VPC at region level
> Murali Reddy Murali Reddy Open Unresolved 19/Dec/13 19/Dec/13
> CLOUDSTACK-5398
> Cloudstack network-element plugin to orchestrate Juniper's switches
> Unassigned Pradeep H Krishnamurthy Open Unresolved 06/Dec/13 06/Dec/13
>
>
>
> Cheers,
>
> Hugo
>
> On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org> wrote:
>
>
> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>
>
> But you do agree that the re-spins uncovered bugs/issues that needed
> to be fixed? Is it perhaps a mismatch in when the artifacts start
> getting tested by the users+devs as opposed to when company-x might be
> satisfied with their testing? More than 90% of the re-spins are
> bugs/issues uncovered by users who needed RC candidates and weren't
> testing artifacts on a daily basis (I could be wrong here). I don't
> think someone with a large test engineering team would wait for the
> RCs to get rolling. May be if we addressed that mismatch in timing we
> could have smaller RC phases. Something like a soft-freeze and a
> hard-freeze.
>
> post soft-freeze : users+devs do a daily test (mostly manually for
> features they care about)
> post hard-freeze : everyone only looks at a daily automated test
> report and if all looks good, we release?
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
>
RE: 4.4 Feature Freeze
Posted by Devdeep Singh <de...@citrix.com>.
I was looking into adding support for iSCSI (CLOUDSTACK-6109) and HA of guest vms (CLOUDSTACK-6144) for hyper-v. I don't think I'll be able to finish it by 14th.
Regards,
Devdeep
From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo Trippaers
Sent: Friday, February 28, 2014 7:40 PM
To: <de...@cloudstack.apache.org>
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 features coming in at the last minute. Actually i'm under the impression that when we move the deadline people will actually try to get more features in instead of working on stabilizing existing features.
"We can't deliver features on the roadmap." There is validity to this point, but on the other hand we already know the entire release schedule way ahead, this feature freeze date should not come as a surprise. But as i mentioned in an earlier mail, lets have this discussion. Post which features might not make it into the release so we can have a discussion if we should slip the release date to get this feature in. I think we all now that there are commercial parties working with this software to build releases and have customers demanding features, but if we don't discuss that on list it's hard for us to take it into account.
"Feature freeze wasn't called" True, i wasn't even aware that this was a requirement. We should add this to the procedure here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so release managers know this is expected of them. It should not impact the dates as the dates are already fixed by the release schedule (every 4 months)
I'm still -1 on extending the feature freeze. I would rather extend the test/stability phase to we have some more time to fix issues before we get into the RC spinning.
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?
ASF JIRA
Project: CloudStack
Type: New Feature
Fix Version: 4.4.0
Resolution: Unresolved
Sorted by: Updated descending
1-15 of 15 as at: 28/Feb/14 15:07
T Key Summary Assignee Reporter P Status Resolution Created Updated Due
[New Feature] CLOUDSTACK-6181
Root resize
Unassigned Nux [Major] [Open] Open Unresolved 27/Feb/14 27/Feb/14
[New Feature] CLOUDSTACK-6161
distributed routing and network ACL with OVS plug-in
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 24/Feb/14 24/Feb/14
[New Feature] CLOUDSTACK-6092
Storage OverProvisioning as a Per Primary Basis
Saksham Srivastava Saksham Srivastava [Major] [Open] Open Unresolved 13/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6144
HA for guest VMs running Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6143
Storage Live-Migration support for Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6142
Zone Wide Primary Store in Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6104
PVLAN support for CloudStack deployment over Nexus 1000v in VMware environment
Sateesh Chodapuneedi Sateesh Chodapuneedi [Major] [Open] Open Unresolved 14/Feb/14 15/Feb/14
[New Feature] CLOUDSTACK-6109
Support of iSCSI as primary store in Hyper-V
Rajesh Battala Rajesh Battala [Major] [Open] Open Unresolved 14/Feb/14 14/Feb/14
[New Feature] CLOUDSTACK-6106
Support of VPC in HyperV
Rajesh Battala Rajesh Battala [Major] [Open] Open Unresolved 14/Feb/14 14/Feb/14
[New Feature] CLOUDSTACK-6090
Virtual Router Service Failure Alerting
Harikrishna Patnala Harikrishna Patnala [Major] [Open] Open Unresolved 13/Feb/14 13/Feb/14
[New Feature] CLOUDSTACK-6052
List VM enhancement to support querying with multiple VM IDs
Koushik Das Koushik Das [Major] [Open] Open Unresolved 07/Feb/14 07/Feb/14
[New Feature] CLOUDSTACK-5569
enhance OVS plug-in to support region level VPC and guest networks that span zones
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5568
introduce notion of guest network that spans multiple zones
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5567
enable VPC at region level
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5398
Cloudstack network-element plugin to orchestrate Juniper's switches
Unassigned Pradeep H Krishnamurthy [Major] [Open] Open Unresolved 06/Dec/13 06/Dec/13
Cheers,
Hugo
On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org>> wrote:
On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
But you do agree that the re-spins uncovered bugs/issues that needed
to be fixed? Is it perhaps a mismatch in when the artifacts start
getting tested by the users+devs as opposed to when company-x might be
satisfied with their testing? More than 90% of the re-spins are
bugs/issues uncovered by users who needed RC candidates and weren't
testing artifacts on a daily basis (I could be wrong here). I don't
think someone with a large test engineering team would wait for the
RCs to get rolling. May be if we addressed that mismatch in timing we
could have smaller RC phases. Something like a soft-freeze and a
hard-freeze.
post soft-freeze : users+devs do a daily test (mostly manually for
features they care about)
post hard-freeze : everyone only looks at a daily automated test
report and if all looks good, we release?
--
Prasanna.,
------------------------
Powered by BigRock.com<http://BigRock.com>
RE: 4.4 Feature Freeze
Posted by Damoder Reddy <Da...@citrix.com>.
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:trippie@gmail.com] On Behalf Of Hugo Trippaers
Sent: Friday, February 28, 2014 7:40 PM
To: <de...@cloudstack.apache.org>
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 features coming in at the last minute. Actually i'm under the impression that when we move the deadline people will actually try to get more features in instead of working on stabilizing existing features.
"We can't deliver features on the roadmap." There is validity to this point, but on the other hand we already know the entire release schedule way ahead, this feature freeze date should not come as a surprise. But as i mentioned in an earlier mail, lets have this discussion. Post which features might not make it into the release so we can have a discussion if we should slip the release date to get this feature in. I think we all now that there are commercial parties working with this software to build releases and have customers demanding features, but if we don't discuss that on list it's hard for us to take it into account.
"Feature freeze wasn't called" True, i wasn't even aware that this was a requirement. We should add this to the procedure here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so release managers know this is expected of them. It should not impact the dates as the dates are already fixed by the release schedule (every 4 months)
I'm still -1 on extending the feature freeze. I would rather extend the test/stability phase to we have some more time to fix issues before we get into the RC spinning.
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?
ASF JIRA
Project: CloudStack
Type: New Feature
Fix Version: 4.4.0
Resolution: Unresolved
Sorted by: Updated descending
1-15 of 15 as at: 28/Feb/14 15:07
T Key Summary Assignee Reporter P Status Resolution Created Updated Due
[New Feature] CLOUDSTACK-6181
Root resize
Unassigned Nux [Major] [Open] Open Unresolved 27/Feb/14 27/Feb/14
[New Feature] CLOUDSTACK-6161
distributed routing and network ACL with OVS plug-in
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 24/Feb/14 24/Feb/14
[New Feature] CLOUDSTACK-6092
Storage OverProvisioning as a Per Primary Basis
Saksham Srivastava Saksham Srivastava [Major] [Open] Open Unresolved 13/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6144
HA for guest VMs running Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6143
Storage Live-Migration support for Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6142
Zone Wide Primary Store in Hyper-V
Unassigned Rajesh Battala [Major] [Open] Open Unresolved 20/Feb/14 20/Feb/14
[New Feature] CLOUDSTACK-6104
PVLAN support for CloudStack deployment over Nexus 1000v in VMware environment
Sateesh Chodapuneedi Sateesh Chodapuneedi [Major] [Open] Open Unresolved 14/Feb/14 15/Feb/14
[New Feature] CLOUDSTACK-6109
Support of iSCSI as primary store in Hyper-V
Rajesh Battala Rajesh Battala [Major] [Open] Open Unresolved 14/Feb/14 14/Feb/14
[New Feature] CLOUDSTACK-6106
Support of VPC in HyperV
Rajesh Battala Rajesh Battala [Major] [Open] Open Unresolved 14/Feb/14 14/Feb/14
[New Feature] CLOUDSTACK-6090
Virtual Router Service Failure Alerting
Harikrishna Patnala Harikrishna Patnala [Major] [Open] Open Unresolved 13/Feb/14 13/Feb/14
[New Feature] CLOUDSTACK-6052
List VM enhancement to support querying with multiple VM IDs
Koushik Das Koushik Das [Major] [Open] Open Unresolved 07/Feb/14 07/Feb/14
[New Feature] CLOUDSTACK-5569
enhance OVS plug-in to support region level VPC and guest networks that span zones
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5568
introduce notion of guest network that spans multiple zones
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5567
enable VPC at region level
Murali Reddy Murali Reddy [Major] [Open] Open Unresolved 19/Dec/13 19/Dec/13
[New Feature] CLOUDSTACK-5398
Cloudstack network-element plugin to orchestrate Juniper's switches
Unassigned Pradeep H Krishnamurthy [Major] [Open] Open Unresolved 06/Dec/13 06/Dec/13
Cheers,
Hugo
On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org>> wrote:
On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
But you do agree that the re-spins uncovered bugs/issues that needed
to be fixed? Is it perhaps a mismatch in when the artifacts start
getting tested by the users+devs as opposed to when company-x might be
satisfied with their testing? More than 90% of the re-spins are
bugs/issues uncovered by users who needed RC candidates and weren't
testing artifacts on a daily basis (I could be wrong here). I don't
think someone with a large test engineering team would wait for the
RCs to get rolling. May be if we addressed that mismatch in timing we
could have smaller RC phases. Something like a soft-freeze and a
hard-freeze.
post soft-freeze : users+devs do a daily test (mostly manually for
features they care about)
post hard-freeze : everyone only looks at a daily automated test
report and if all looks good, we release?
--
Prasanna.,
------------------------
Powered by BigRock.com<http://BigRock.com>
Re: 4.4 Feature Freeze
Posted by Marcus <sh...@gmail.com>.
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 chunk of that being frozen from commits) is
to roll fewer, incremental changes often rather than a large number of
changes. We seem to have a lot of changes that by the time they're
merged *mostly* work, and then we spend 3-4 months just fixing the
bugs and then talk about pushing out the next release. This has
happened every release since I've been a part of the project. A year
ago this month we were talking about Spring, and arguments were being
made that not including spring in 4.1 at the last moment would punish
those who worked so hard on it, and then 4.1 got delayed for several
months due to that and other issues. We have to move beyond the
'punishment' mentality if we do actually still want to stick to a
schedule, because it promotes pushing unfinished code into a release.
It's not that I don't understand wanting to merge a feature early, or
not work on it for several releases. Huge swaths of code get changed
every release, and not just due to features. Sometimes it seems as
though there are a few people whose job is just to reorganize/split
classes :-) It's very difficult to keep a feature branch working and
up-to-date with master, and it's telling I think that features are
generally started and merged in the same window (the one exception I
can remember is the storage refactor). I wouldn't expect that with
such a complex piece of software, but when core components change
every release it's difficult to develop across cycles.
I think if we mess with the timeline it may not do much good until we
figure out how to stop breaking things/introducing bugs when we merge
features. If we stretch out testing, people still won't play with it
until RC time. Playing with the merge window will only adjust how bad
it is (which perhaps is better than nothing) when we go to RC.
On Fri, Feb 28, 2014 at 5:46 PM, Sheng Yang <sh...@yasker.org> wrote:
> 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. I don't think it would make any sense.
>
> Also, keep the current schedule in the future would also means
> discourage people from testing RC release - if I need to choose only
> one between developing my feature in the new release(which bound to a
> timeline) or testing current release's RC(which can last two month
> without anyone see the end, due to various reason), who would do the
> latter? I believe many developers/companies involved here would have
> feature/timeline for release.
>
> I don't want to say it's correct or not for now to stick with our "4
> month release cycle" since we once agreed on it, but please do put the
> RC process into consideration. How many weeks we have after 4.2
> release for new features in 4.3? How many weeks after 4.3 release for
> new features in 4.4? I don't believe we want to discourage people from
> testing the current release by any meanings, but that's the point our
> current schedule implies.
>
> --Sheng
>
> On Fri, Feb 28, 2014 at 3:31 PM, Mike Tutkowski
> <mi...@solidfire.com> wrote:
>> 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 help out on testing RC builds rather
>> than you move forward with development on master. However, in the current
>> model, you're incented a bit to ignore the RC builds and continue on with
>> development on master if testing RCs is going to stop you from getting a
>> feature into the next release. It's especially easy to ignore testing RC
>> builds when there are six of them.
>>
>>
>> On Fri, Feb 28, 2014 at 2:08 PM, John Kinsella <jl...@stratosec.co> wrote:
>>
>>> 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 <hugo@trippaers.nl<mailto:
>>> hugo@trippaers.nl>> 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
>>> features coming in at the last minute. Actually i'm under the impression
>>> that when we move the deadline people will actually try to get more
>>> features in instead of working on stabilizing existing features.
>>>
>>> "We can't deliver features on the roadmap." There is validity to this
>>> point, but on the other hand we already know the entire release schedule
>>> way ahead, this feature freeze date should not come as a surprise. But as i
>>> mentioned in an earlier mail, lets have this discussion. Post which
>>> features might not make it into the release so we can have a discussion if
>>> we should slip the release date to get this feature in. I think we all now
>>> that there are commercial parties working with this software to build
>>> releases and have customers demanding features, but if we don't discuss
>>> that on list it's hard for us to take it into account.
>>>
>>> "Feature freeze wasn't called" True, i wasn't even aware that this was a
>>> requirement. We should add this to the procedure here
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so
>>> release managers know this is expected of them. It should not impact the
>>> dates as the dates are already fixed by the release schedule (every 4
>>> months)
>>>
>>>
>>> I'm still -1 on extending the feature freeze. I would rather extend the
>>> test/stability phase to we have some more time to fix issues before we get
>>> into the RC spinning.
>>>
>>>
>>> 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?
>>>
>>> ASF JIRA
>>> Project: CloudStack
>>> Type: New Feature
>>> Fix Version: 4.4.0
>>> Resolution: Unresolved
>>> Sorted by: Updated descending
>>> 1-15 of 15 as at: 28/Feb/14 15:07
>>> T Key Summary Assignee Reporter P Status Resolution Created Updated Due
>>> <newfeature.png> CLOUDSTACK-6181
>>> Root resize
>>> Unassigned Nux <major.png> <open.png> Open Unresolved 27/Feb/14 27/Feb/14
>>> <newfeature.png> CLOUDSTACK-6161
>>> distributed routing and network ACL with OVS plug-in
>>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 24/Feb/14
>>> 24/Feb/14
>>> <newfeature.png> CLOUDSTACK-6092
>>> Storage OverProvisioning as a Per Primary Basis
>>> Saksham Srivastava Saksham Srivastava <major.png> <open.png> Open
>>> Unresolved 13/Feb/14 20/Feb/14
>>> <newfeature.png> CLOUDSTACK-6144
>>> HA for guest VMs running Hyper-V
>>> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14
>>> 20/Feb/14
>>> <newfeature.png> CLOUDSTACK-6143
>>> Storage Live-Migration support for Hyper-V
>>> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14
>>> 20/Feb/14
>>> <newfeature.png> CLOUDSTACK-6142
>>> Zone Wide Primary Store in Hyper-V
>>> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14
>>> 20/Feb/14
>>> <newfeature.png> CLOUDSTACK-6104
>>> PVLAN support for CloudStack deployment over Nexus 1000v in VMware
>>> environment
>>> Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png> <open.png> Open
>>> Unresolved 14/Feb/14 15/Feb/14
>>> <newfeature.png> CLOUDSTACK-6109
>>> Support of iSCSI as primary store in Hyper-V
>>> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved
>>> 14/Feb/14 14/Feb/14
>>> <newfeature.png> CLOUDSTACK-6106
>>> Support of VPC in HyperV
>>> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved
>>> 14/Feb/14 14/Feb/14
>>> <newfeature.png> CLOUDSTACK-6090
>>> Virtual Router Service Failure Alerting
>>> Harikrishna Patnala Harikrishna Patnala <major.png> <open.png> Open
>>> Unresolved 13/Feb/14 13/Feb/14
>>> <newfeature.png> CLOUDSTACK-6052
>>> List VM enhancement to support querying with multiple VM IDs
>>> Koushik Das Koushik Das <major.png> <open.png> Open Unresolved 07/Feb/14
>>> 07/Feb/14
>>> <newfeature.png> CLOUDSTACK-5569
>>> enhance OVS plug-in to support region level VPC and guest networks that
>>> span zones
>>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
>>> 19/Dec/13
>>> <newfeature.png> CLOUDSTACK-5568
>>> introduce notion of guest network that spans multiple zones
>>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
>>> 19/Dec/13
>>> <newfeature.png> CLOUDSTACK-5567
>>> enable VPC at region level
>>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
>>> 19/Dec/13
>>> <newfeature.png> CLOUDSTACK-5398
>>> Cloudstack network-element plugin to orchestrate Juniper's switches
>>> Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open Unresolved
>>> 06/Dec/13 06/Dec/13
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Hugo
>>>
>>> On 28 feb. 2014, at 10:17, Prasanna Santhanam <tsp@apache.org<mailto:
>>> tsp@apache.org>> wrote:
>>>
>>> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>>>
>>>
>>> But you do agree that the re-spins uncovered bugs/issues that needed
>>> to be fixed? Is it perhaps a mismatch in when the artifacts start
>>> getting tested by the users+devs as opposed to when company-x might be
>>> satisfied with their testing? More than 90% of the re-spins are
>>> bugs/issues uncovered by users who needed RC candidates and weren't
>>> testing artifacts on a daily basis (I could be wrong here). I don't
>>> think someone with a large test engineering team would wait for the
>>> RCs to get rolling. May be if we addressed that mismatch in timing we
>>> could have smaller RC phases. Something like a soft-freeze and a
>>> hard-freeze.
>>>
>>> post soft-freeze : users+devs do a daily test (mostly manually for
>>> features they care about)
>>> post hard-freeze : everyone only looks at a daily automated test
>>> report and if all looks good, we release?
>>>
>>> --
>>> Prasanna.,
>>>
>>> ------------------------
>>> Powered by BigRock.com<http://bigrock.com/>
>>>
>>>
>>>
>>> Stratosec<http://stratosec.co/> - Compliance as a Service
>>> o: 415.315.9385
>>> @johnlkinsella<http://twitter.com/johnlkinsella>
>>>
>>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud<http://solidfire.com/solution/overview/?video=play>
>> *(tm)*
Re: 4.4 Feature Freeze
Posted by Sheng Yang <sh...@yasker.org>.
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. I don't think it would make any sense.
Also, keep the current schedule in the future would also means
discourage people from testing RC release - if I need to choose only
one between developing my feature in the new release(which bound to a
timeline) or testing current release's RC(which can last two month
without anyone see the end, due to various reason), who would do the
latter? I believe many developers/companies involved here would have
feature/timeline for release.
I don't want to say it's correct or not for now to stick with our "4
month release cycle" since we once agreed on it, but please do put the
RC process into consideration. How many weeks we have after 4.2
release for new features in 4.3? How many weeks after 4.3 release for
new features in 4.4? I don't believe we want to discourage people from
testing the current release by any meanings, but that's the point our
current schedule implies.
--Sheng
On Fri, Feb 28, 2014 at 3:31 PM, Mike Tutkowski
<mi...@solidfire.com> wrote:
> 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 help out on testing RC builds rather
> than you move forward with development on master. However, in the current
> model, you're incented a bit to ignore the RC builds and continue on with
> development on master if testing RCs is going to stop you from getting a
> feature into the next release. It's especially easy to ignore testing RC
> builds when there are six of them.
>
>
> On Fri, Feb 28, 2014 at 2:08 PM, John Kinsella <jl...@stratosec.co> wrote:
>
>> 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 <hugo@trippaers.nl<mailto:
>> hugo@trippaers.nl>> 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
>> features coming in at the last minute. Actually i'm under the impression
>> that when we move the deadline people will actually try to get more
>> features in instead of working on stabilizing existing features.
>>
>> "We can't deliver features on the roadmap." There is validity to this
>> point, but on the other hand we already know the entire release schedule
>> way ahead, this feature freeze date should not come as a surprise. But as i
>> mentioned in an earlier mail, lets have this discussion. Post which
>> features might not make it into the release so we can have a discussion if
>> we should slip the release date to get this feature in. I think we all now
>> that there are commercial parties working with this software to build
>> releases and have customers demanding features, but if we don't discuss
>> that on list it's hard for us to take it into account.
>>
>> "Feature freeze wasn't called" True, i wasn't even aware that this was a
>> requirement. We should add this to the procedure here
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so
>> release managers know this is expected of them. It should not impact the
>> dates as the dates are already fixed by the release schedule (every 4
>> months)
>>
>>
>> I'm still -1 on extending the feature freeze. I would rather extend the
>> test/stability phase to we have some more time to fix issues before we get
>> into the RC spinning.
>>
>>
>> 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?
>>
>> ASF JIRA
>> Project: CloudStack
>> Type: New Feature
>> Fix Version: 4.4.0
>> Resolution: Unresolved
>> Sorted by: Updated descending
>> 1-15 of 15 as at: 28/Feb/14 15:07
>> T Key Summary Assignee Reporter P Status Resolution Created Updated Due
>> <newfeature.png> CLOUDSTACK-6181
>> Root resize
>> Unassigned Nux <major.png> <open.png> Open Unresolved 27/Feb/14 27/Feb/14
>> <newfeature.png> CLOUDSTACK-6161
>> distributed routing and network ACL with OVS plug-in
>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 24/Feb/14
>> 24/Feb/14
>> <newfeature.png> CLOUDSTACK-6092
>> Storage OverProvisioning as a Per Primary Basis
>> Saksham Srivastava Saksham Srivastava <major.png> <open.png> Open
>> Unresolved 13/Feb/14 20/Feb/14
>> <newfeature.png> CLOUDSTACK-6144
>> HA for guest VMs running Hyper-V
>> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14
>> 20/Feb/14
>> <newfeature.png> CLOUDSTACK-6143
>> Storage Live-Migration support for Hyper-V
>> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14
>> 20/Feb/14
>> <newfeature.png> CLOUDSTACK-6142
>> Zone Wide Primary Store in Hyper-V
>> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14
>> 20/Feb/14
>> <newfeature.png> CLOUDSTACK-6104
>> PVLAN support for CloudStack deployment over Nexus 1000v in VMware
>> environment
>> Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png> <open.png> Open
>> Unresolved 14/Feb/14 15/Feb/14
>> <newfeature.png> CLOUDSTACK-6109
>> Support of iSCSI as primary store in Hyper-V
>> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved
>> 14/Feb/14 14/Feb/14
>> <newfeature.png> CLOUDSTACK-6106
>> Support of VPC in HyperV
>> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved
>> 14/Feb/14 14/Feb/14
>> <newfeature.png> CLOUDSTACK-6090
>> Virtual Router Service Failure Alerting
>> Harikrishna Patnala Harikrishna Patnala <major.png> <open.png> Open
>> Unresolved 13/Feb/14 13/Feb/14
>> <newfeature.png> CLOUDSTACK-6052
>> List VM enhancement to support querying with multiple VM IDs
>> Koushik Das Koushik Das <major.png> <open.png> Open Unresolved 07/Feb/14
>> 07/Feb/14
>> <newfeature.png> CLOUDSTACK-5569
>> enhance OVS plug-in to support region level VPC and guest networks that
>> span zones
>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
>> 19/Dec/13
>> <newfeature.png> CLOUDSTACK-5568
>> introduce notion of guest network that spans multiple zones
>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
>> 19/Dec/13
>> <newfeature.png> CLOUDSTACK-5567
>> enable VPC at region level
>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
>> 19/Dec/13
>> <newfeature.png> CLOUDSTACK-5398
>> Cloudstack network-element plugin to orchestrate Juniper's switches
>> Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open Unresolved
>> 06/Dec/13 06/Dec/13
>>
>>
>>
>> Cheers,
>>
>> Hugo
>>
>> On 28 feb. 2014, at 10:17, Prasanna Santhanam <tsp@apache.org<mailto:
>> tsp@apache.org>> wrote:
>>
>> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>>
>>
>> But you do agree that the re-spins uncovered bugs/issues that needed
>> to be fixed? Is it perhaps a mismatch in when the artifacts start
>> getting tested by the users+devs as opposed to when company-x might be
>> satisfied with their testing? More than 90% of the re-spins are
>> bugs/issues uncovered by users who needed RC candidates and weren't
>> testing artifacts on a daily basis (I could be wrong here). I don't
>> think someone with a large test engineering team would wait for the
>> RCs to get rolling. May be if we addressed that mismatch in timing we
>> could have smaller RC phases. Something like a soft-freeze and a
>> hard-freeze.
>>
>> post soft-freeze : users+devs do a daily test (mostly manually for
>> features they care about)
>> post hard-freeze : everyone only looks at a daily automated test
>> report and if all looks good, we release?
>>
>> --
>> Prasanna.,
>>
>> ------------------------
>> Powered by BigRock.com<http://bigrock.com/>
>>
>>
>>
>> Stratosec<http://stratosec.co/> - Compliance as a Service
>> o: 415.315.9385
>> @johnlkinsella<http://twitter.com/johnlkinsella>
>>
>>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
RE: 4.4 Feature Freeze
Posted by Prachi Damle <Pr...@citrix.com>.
+1 for pushing out the feature freeze to 3/28.
Most of us have been busy with 4.3 and so it will be good to have some extra room to focus fully on our 4.4 features.
Myself and Min are working on the IAM feature (https://issues.apache.org/jira/browse/CLOUDSTACK-5920) and I feel that 3/28 will give us some room to test our code and add better integration tests.
Current integration tests do not focus on testing IAM functionality with default roles (user/domainadmin/admin) at all. So it is good to cover as many as we could.
Thanks,
Prachi
-----Original Message-----
From: Mike Tutkowski [mailto:mike.tutkowski@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 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 help out on testing RC builds rather than you move forward with development on master. However, in the current model, you're incented a bit to ignore the RC builds and continue on with development on master if testing RCs is going to stop you from getting a feature into the next release. It's especially easy to ignore testing RC builds when there are six of them.
On Fri, Feb 28, 2014 at 2:08 PM, John Kinsella <jl...@stratosec.co> wrote:
> 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 <hugo@trippaers.nl<mailto:
> hugo@trippaers.nl>> 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 features coming in at the last minute. Actually i'm under the
> impression that when we move the deadline people will actually try to
> get more features in instead of working on stabilizing existing features.
>
> "We can't deliver features on the roadmap." There is validity to this
> point, but on the other hand we already know the entire release
> schedule way ahead, this feature freeze date should not come as a
> surprise. But as i mentioned in an earlier mail, lets have this
> discussion. Post which features might not make it into the release so
> we can have a discussion if we should slip the release date to get
> this feature in. I think we all now that there are commercial parties
> working with this software to build releases and have customers
> demanding features, but if we don't discuss that on list it's hard for us to take it into account.
>
> "Feature freeze wasn't called" True, i wasn't even aware that this was
> a requirement. We should add this to the procedure here
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so
> release managers know this is expected of them. It should not impact
> the dates as the dates are already fixed by the release schedule
> (every 4
> months)
>
>
> I'm still -1 on extending the feature freeze. I would rather extend
> the test/stability phase to we have some more time to fix issues
> before we get into the RC spinning.
>
>
> 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?
>
> ASF JIRA
> Project: CloudStack
> Type: New Feature
> Fix Version: 4.4.0
> Resolution: Unresolved
> Sorted by: Updated descending
> 1-15 of 15 as at: 28/Feb/14 15:07
> T Key Summary Assignee Reporter P Status Resolution Created Updated
> Due <newfeature.png> CLOUDSTACK-6181 Root resize Unassigned Nux
> <major.png> <open.png> Open Unresolved 27/Feb/14 27/Feb/14
> <newfeature.png> CLOUDSTACK-6161 distributed routing and network ACL
> with OVS plug-in Murali Reddy Murali Reddy <major.png> <open.png> Open
> Unresolved 24/Feb/14
> 24/Feb/14
> <newfeature.png> CLOUDSTACK-6092
> Storage OverProvisioning as a Per Primary Basis Saksham Srivastava
> Saksham Srivastava <major.png> <open.png> Open Unresolved 13/Feb/14
> 20/Feb/14 <newfeature.png> CLOUDSTACK-6144 HA for guest VMs running
> Hyper-V Unassigned Rajesh Battala <major.png> <open.png> Open
> Unresolved 20/Feb/14
> 20/Feb/14
> <newfeature.png> CLOUDSTACK-6143
> Storage Live-Migration support for Hyper-V Unassigned Rajesh Battala
> <major.png> <open.png> Open Unresolved 20/Feb/14
> 20/Feb/14
> <newfeature.png> CLOUDSTACK-6142
> Zone Wide Primary Store in Hyper-V
> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved
> 20/Feb/14
> 20/Feb/14
> <newfeature.png> CLOUDSTACK-6104
> PVLAN support for CloudStack deployment over Nexus 1000v in VMware
> environment Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png>
> <open.png> Open Unresolved 14/Feb/14 15/Feb/14 <newfeature.png>
> CLOUDSTACK-6109 Support of iSCSI as primary store in Hyper-V Rajesh
> Battala Rajesh Battala <major.png> <open.png> Open Unresolved
> 14/Feb/14 14/Feb/14
> <newfeature.png> CLOUDSTACK-6106
> Support of VPC in HyperV
> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved
> 14/Feb/14 14/Feb/14
> <newfeature.png> CLOUDSTACK-6090
> Virtual Router Service Failure Alerting Harikrishna Patnala
> Harikrishna Patnala <major.png> <open.png> Open Unresolved 13/Feb/14
> 13/Feb/14 <newfeature.png> CLOUDSTACK-6052 List VM enhancement to
> support querying with multiple VM IDs Koushik Das Koushik Das
> <major.png> <open.png> Open Unresolved 07/Feb/14
> 07/Feb/14
> <newfeature.png> CLOUDSTACK-5569
> enhance OVS plug-in to support region level VPC and guest networks
> that span zones Murali Reddy Murali Reddy <major.png> <open.png> Open
> Unresolved 19/Dec/13
> 19/Dec/13
> <newfeature.png> CLOUDSTACK-5568
> introduce notion of guest network that spans multiple zones Murali
> Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
> 19/Dec/13
> <newfeature.png> CLOUDSTACK-5567
> enable VPC at region level
> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved
> 19/Dec/13
> 19/Dec/13
> <newfeature.png> CLOUDSTACK-5398
> Cloudstack network-element plugin to orchestrate Juniper's switches
> Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open
> Unresolved
> 06/Dec/13 06/Dec/13
>
>
>
> Cheers,
>
> Hugo
>
> On 28 feb. 2014, at 10:17, Prasanna Santhanam <tsp@apache.org<mailto:
> tsp@apache.org>> wrote:
>
> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>
>
> But you do agree that the re-spins uncovered bugs/issues that needed
> to be fixed? Is it perhaps a mismatch in when the artifacts start
> getting tested by the users+devs as opposed to when company-x might be
> satisfied with their testing? More than 90% of the re-spins are
> bugs/issues uncovered by users who needed RC candidates and weren't
> testing artifacts on a daily basis (I could be wrong here). I don't
> think someone with a large test engineering team would wait for the
> RCs to get rolling. May be if we addressed that mismatch in timing we
> could have smaller RC phases. Something like a soft-freeze and a
> hard-freeze.
>
> post soft-freeze : users+devs do a daily test (mostly manually for
> features they care about) post hard-freeze : everyone only looks at a
> daily automated test report and if all looks good, we release?
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com<http://bigrock.com/>
>
>
>
> Stratosec<http://stratosec.co/> - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella<http://twitter.com/johnlkinsella>
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
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 help out on testing RC builds rather
than you move forward with development on master. However, in the current
model, you're incented a bit to ignore the RC builds and continue on with
development on master if testing RCs is going to stop you from getting a
feature into the next release. It's especially easy to ignore testing RC
builds when there are six of them.
On Fri, Feb 28, 2014 at 2:08 PM, John Kinsella <jl...@stratosec.co> wrote:
> 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 <hugo@trippaers.nl<mailto:
> hugo@trippaers.nl>> 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
> features coming in at the last minute. Actually i'm under the impression
> that when we move the deadline people will actually try to get more
> features in instead of working on stabilizing existing features.
>
> "We can't deliver features on the roadmap." There is validity to this
> point, but on the other hand we already know the entire release schedule
> way ahead, this feature freeze date should not come as a surprise. But as i
> mentioned in an earlier mail, lets have this discussion. Post which
> features might not make it into the release so we can have a discussion if
> we should slip the release date to get this feature in. I think we all now
> that there are commercial parties working with this software to build
> releases and have customers demanding features, but if we don't discuss
> that on list it's hard for us to take it into account.
>
> "Feature freeze wasn't called" True, i wasn't even aware that this was a
> requirement. We should add this to the procedure here
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so
> release managers know this is expected of them. It should not impact the
> dates as the dates are already fixed by the release schedule (every 4
> months)
>
>
> I'm still -1 on extending the feature freeze. I would rather extend the
> test/stability phase to we have some more time to fix issues before we get
> into the RC spinning.
>
>
> 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?
>
> ASF JIRA
> Project: CloudStack
> Type: New Feature
> Fix Version: 4.4.0
> Resolution: Unresolved
> Sorted by: Updated descending
> 1-15 of 15 as at: 28/Feb/14 15:07
> T Key Summary Assignee Reporter P Status Resolution Created Updated Due
> <newfeature.png> CLOUDSTACK-6181
> Root resize
> Unassigned Nux <major.png> <open.png> Open Unresolved 27/Feb/14 27/Feb/14
> <newfeature.png> CLOUDSTACK-6161
> distributed routing and network ACL with OVS plug-in
> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 24/Feb/14
> 24/Feb/14
> <newfeature.png> CLOUDSTACK-6092
> Storage OverProvisioning as a Per Primary Basis
> Saksham Srivastava Saksham Srivastava <major.png> <open.png> Open
> Unresolved 13/Feb/14 20/Feb/14
> <newfeature.png> CLOUDSTACK-6144
> HA for guest VMs running Hyper-V
> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14
> 20/Feb/14
> <newfeature.png> CLOUDSTACK-6143
> Storage Live-Migration support for Hyper-V
> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14
> 20/Feb/14
> <newfeature.png> CLOUDSTACK-6142
> Zone Wide Primary Store in Hyper-V
> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14
> 20/Feb/14
> <newfeature.png> CLOUDSTACK-6104
> PVLAN support for CloudStack deployment over Nexus 1000v in VMware
> environment
> Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png> <open.png> Open
> Unresolved 14/Feb/14 15/Feb/14
> <newfeature.png> CLOUDSTACK-6109
> Support of iSCSI as primary store in Hyper-V
> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved
> 14/Feb/14 14/Feb/14
> <newfeature.png> CLOUDSTACK-6106
> Support of VPC in HyperV
> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved
> 14/Feb/14 14/Feb/14
> <newfeature.png> CLOUDSTACK-6090
> Virtual Router Service Failure Alerting
> Harikrishna Patnala Harikrishna Patnala <major.png> <open.png> Open
> Unresolved 13/Feb/14 13/Feb/14
> <newfeature.png> CLOUDSTACK-6052
> List VM enhancement to support querying with multiple VM IDs
> Koushik Das Koushik Das <major.png> <open.png> Open Unresolved 07/Feb/14
> 07/Feb/14
> <newfeature.png> CLOUDSTACK-5569
> enhance OVS plug-in to support region level VPC and guest networks that
> span zones
> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
> 19/Dec/13
> <newfeature.png> CLOUDSTACK-5568
> introduce notion of guest network that spans multiple zones
> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
> 19/Dec/13
> <newfeature.png> CLOUDSTACK-5567
> enable VPC at region level
> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13
> 19/Dec/13
> <newfeature.png> CLOUDSTACK-5398
> Cloudstack network-element plugin to orchestrate Juniper's switches
> Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open Unresolved
> 06/Dec/13 06/Dec/13
>
>
>
> Cheers,
>
> Hugo
>
> On 28 feb. 2014, at 10:17, Prasanna Santhanam <tsp@apache.org<mailto:
> tsp@apache.org>> wrote:
>
> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>
>
> But you do agree that the re-spins uncovered bugs/issues that needed
> to be fixed? Is it perhaps a mismatch in when the artifacts start
> getting tested by the users+devs as opposed to when company-x might be
> satisfied with their testing? More than 90% of the re-spins are
> bugs/issues uncovered by users who needed RC candidates and weren't
> testing artifacts on a daily basis (I could be wrong here). I don't
> think someone with a large test engineering team would wait for the
> RCs to get rolling. May be if we addressed that mismatch in timing we
> could have smaller RC phases. Something like a soft-freeze and a
> hard-freeze.
>
> post soft-freeze : users+devs do a daily test (mostly manually for
> features they care about)
> post hard-freeze : everyone only looks at a daily automated test
> report and if all looks good, we release?
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com<http://bigrock.com/>
>
>
>
> Stratosec<http://stratosec.co/> - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella<http://twitter.com/johnlkinsella>
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by John Kinsella <jl...@stratosec.co>.
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 <hu...@trippaers.nl>> 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 features coming in at the last minute. Actually i’m under the impression that when we move the deadline people will actually try to get more features in instead of working on stabilizing existing features.
“We can’t deliver features on the roadmap.” There is validity to this point, but on the other hand we already know the entire release schedule way ahead, this feature freeze date should not come as a surprise. But as i mentioned in an earlier mail, lets have this discussion. Post which features might not make it into the release so we can have a discussion if we should slip the release date to get this feature in. I think we all now that there are commercial parties working with this software to build releases and have customers demanding features, but if we don’t discuss that on list it’s hard for us to take it into account.
“Feature freeze wasn’t called” True, i wasn’t even aware that this was a requirement. We should add this to the procedure here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so release managers know this is expected of them. It should not impact the dates as the dates are already fixed by the release schedule (every 4 months)
I’m still -1 on extending the feature freeze. I would rather extend the test/stability phase to we have some more time to fix issues before we get into the RC spinning.
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?
ASF JIRA
Project: CloudStack
Type: New Feature
Fix Version: 4.4.0
Resolution: Unresolved
Sorted by: Updated descending
1–15 of 15 as at: 28/Feb/14 15:07
T Key Summary Assignee Reporter P Status Resolution Created Updated Due
<newfeature.png> CLOUDSTACK-6181
Root resize
Unassigned Nux <major.png> <open.png> Open Unresolved 27/Feb/14 27/Feb/14
<newfeature.png> CLOUDSTACK-6161
distributed routing and network ACL with OVS plug-in
Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 24/Feb/14 24/Feb/14
<newfeature.png> CLOUDSTACK-6092
Storage OverProvisioning as a Per Primary Basis
Saksham Srivastava Saksham Srivastava <major.png> <open.png> Open Unresolved 13/Feb/14 20/Feb/14
<newfeature.png> CLOUDSTACK-6144
HA for guest VMs running Hyper-V
Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14 20/Feb/14
<newfeature.png> CLOUDSTACK-6143
Storage Live-Migration support for Hyper-V
Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14 20/Feb/14
<newfeature.png> CLOUDSTACK-6142
Zone Wide Primary Store in Hyper-V
Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14 20/Feb/14
<newfeature.png> CLOUDSTACK-6104
PVLAN support for CloudStack deployment over Nexus 1000v in VMware environment
Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png> <open.png> Open Unresolved 14/Feb/14 15/Feb/14
<newfeature.png> CLOUDSTACK-6109
Support of iSCSI as primary store in Hyper-V
Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved 14/Feb/14 14/Feb/14
<newfeature.png> CLOUDSTACK-6106
Support of VPC in HyperV
Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved 14/Feb/14 14/Feb/14
<newfeature.png> CLOUDSTACK-6090
Virtual Router Service Failure Alerting
Harikrishna Patnala Harikrishna Patnala <major.png> <open.png> Open Unresolved 13/Feb/14 13/Feb/14
<newfeature.png> CLOUDSTACK-6052
List VM enhancement to support querying with multiple VM IDs
Koushik Das Koushik Das <major.png> <open.png> Open Unresolved 07/Feb/14 07/Feb/14
<newfeature.png> CLOUDSTACK-5569
enhance OVS plug-in to support region level VPC and guest networks that span zones
Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13 19/Dec/13
<newfeature.png> CLOUDSTACK-5568
introduce notion of guest network that spans multiple zones
Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13 19/Dec/13
<newfeature.png> CLOUDSTACK-5567
enable VPC at region level
Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13 19/Dec/13
<newfeature.png> CLOUDSTACK-5398
Cloudstack network-element plugin to orchestrate Juniper's switches
Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open Unresolved 06/Dec/13 06/Dec/13
Cheers,
Hugo
On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org>> wrote:
On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
But you do agree that the re-spins uncovered bugs/issues that needed
to be fixed? Is it perhaps a mismatch in when the artifacts start
getting tested by the users+devs as opposed to when company-x might be
satisfied with their testing? More than 90% of the re-spins are
bugs/issues uncovered by users who needed RC candidates and weren't
testing artifacts on a daily basis (I could be wrong here). I don't
think someone with a large test engineering team would wait for the
RCs to get rolling. May be if we addressed that mismatch in timing we
could have smaller RC phases. Something like a soft-freeze and a
hard-freeze.
post soft-freeze : users+devs do a daily test (mostly manually for
features they care about)
post hard-freeze : everyone only looks at a daily automated test
report and if all looks good, we release?
--
Prasanna.,
------------------------
Powered by BigRock.com<http://bigrock.com/>
Stratosec<http://stratosec.co/> - Compliance as a Service
o: 415.315.9385
@johnlkinsella<http://twitter.com/johnlkinsella>
Re: 4.4 Feature Freeze
Posted by murali reddy <mu...@gmail.com>.
On Fri, Feb 28, 2014 at 7:39 PM, Hugo Trippaers <hu...@trippaers.nl> 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 plug-in
> Murali Reddy Murali Reddy [image: Major] [image: Open] Open Unresolved
> 24/Feb/14 24/Feb/14
>
This feature proposed for 4.4 would be impacted if feature freeze is not
extended. I will be short of a weeks time to send out a merge request by
10th March.
Re: 4.4 Feature Freeze
Posted by Marcus <sh...@gmail.com>.
The build is not broken. I, personally, just cannot start VMs in my
environment, even after starting afresh. It may still be something I'm
doing (like a missed behavioral change), but I've seen at least one
bug submitted overnight that looks like a stack trace I got. It would
be nice to see if anyone else is seeing issues.
On Fri, Mar 14, 2014 at 8:45 AM, Mike Tutkowski
<mi...@solidfire.com> wrote:
> Yes, having a temp freeze of the codebase while a build is broken is
> standard procedure at several places I've worked at.
>
> We should probably employ such a technique here, too.
>
> It's nothing enforced by the VCS - just something devs control when they
> see such an e-mail.
>
>
> On Fri, Mar 14, 2014 at 8:42 AM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com> wrote:
>
>> Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel comfortable
>> merging in my feature branch though when I pull from master and can no
>> longer run my own feature tests.
>>
>> On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
>> > I'm not sure what the offending ones are at the moment, and there was
>> > recently a feature merge that was not squashed, so it might be a
>> > little difficult to weed through.
>> >
>> > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
>> > <su...@citrix.com>
>> > wrote:
>> >>
>> >> Can the offending check-ins be reverted or master be blocked for
>> >> further check-ins till blocking issue is fixed.
>> >> Talluri is running BVTs and can that be taken as basic passing
>> >> criteria to re-enable check-ins.
>> >>
>> >> -----Original Message-----
>> >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
>> >> and I see that while I was sleeping others have reported some of the
>> >> issues I was seeing as well.
>> >>
>> >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
>> >> > 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 the moment.
>> >> >> Let's take this discussion to the 4.5 release if we need to or
>> >> >> focus on doing a high quality release for 4.4 so we can focus on
>> >> >> features again in 4.4
>> >> >>
>> >> >> This means that the feature freeze would be this friday and i
>> >> >> intend to cut the 4.4 branch around 14:00 CET
>> >> >>
>> >> >> As we have a 72 hour window for MERGE requests, please make sure
>> >> >> they are in today (if the feature is ready).
>> >> >>
>> >> >>
>> >> >> Cheers,
>> >> >>
>> >> >> Hugo
>> >> >
>> >> >
>> >> > Can someone confirm if this has made it in?
>> >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>> >> >
>> >> > Marcus requested the MERGE a couple of days ago.
>> >> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
>> >> >
>> >> > Lucian
>> >> >
>> >> > --
>> >> > Sent from the Delta quadrant using Borg technology!
>> >> >
>> >> > Nux!
>> >> > www.nux.ro
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
Yes, having a temp freeze of the codebase while a build is broken is
standard procedure at several places I've worked at.
We should probably employ such a technique here, too.
It's nothing enforced by the VCS - just something devs control when they
see such an e-mail.
On Fri, Mar 14, 2014 at 8:42 AM, Sudha Ponnaganti <
sudha.ponnaganti@citrix.com> wrote:
> Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel comfortable
> merging in my feature branch though when I pull from master and can no
> longer run my own feature tests.
>
> On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> > I'm not sure what the offending ones are at the moment, and there was
> > recently a feature merge that was not squashed, so it might be a
> > little difficult to weed through.
> >
> > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
> > <su...@citrix.com>
> > wrote:
> >>
> >> Can the offending check-ins be reverted or master be blocked for
> >> further check-ins till blocking issue is fixed.
> >> Talluri is running BVTs and can that be taken as basic passing
> >> criteria to re-enable check-ins.
> >>
> >> -----Original Message-----
> >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
> >> and I see that while I was sleeping others have reported some of the
> >> issues I was seeing as well.
> >>
> >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> >> > 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 the moment.
> >> >> Let's take this discussion to the 4.5 release if we need to or
> >> >> focus on doing a high quality release for 4.4 so we can focus on
> >> >> features again in 4.4
> >> >>
> >> >> This means that the feature freeze would be this friday and i
> >> >> intend to cut the 4.4 branch around 14:00 CET
> >> >>
> >> >> As we have a 72 hour window for MERGE requests, please make sure
> >> >> they are in today (if the feature is ready).
> >> >>
> >> >>
> >> >> Cheers,
> >> >>
> >> >> Hugo
> >> >
> >> >
> >> > Can someone confirm if this has made it in?
> >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> >> >
> >> > Marcus requested the MERGE a couple of days ago.
> >> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
> >> >
> >> > Lucian
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Hugo Trippaers <hu...@trippaers.nl>.
Hey Pradeep,
Mike did a good job explaining the process. The 4.4 branch is now in what we call “Feature Freeze”, this means that no new features will be added. You can commit your feature to the master branch now and it will be included in the next (4.5 probably) release.
The 4.4 branch will be limited to bug fixes and stability improvements on existing features.
The feature freeze for 4.5 is estimated at friday may 16 with a possible release date two months later.
Cheers,
Hugo
On 20 mrt. 2014, at 09:58, Pradeep Cloudstack <pr...@yahoo.com> wrote:
> Yes Mike
>
> -Pradeep
>
>
>
>
> ________________________________
> From: Mike Tutkowski <mi...@solidfire.com>
> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep Cloudstack <pr...@yahoo.com>
> Cc: Chiradeep Vittal <Ch...@citrix.com>; Animesh Chaturvedi <an...@citrix.com>
> Sent: Thursday, March 20, 2014 10:34 AM
> Subject: Re: 4.4 Feature Freeze
>
>
> It looks like your code is exclusively related to a network plug-in, is
> that correct? In other words, you do not modify any CloudStack core code,
> but rather solely interface with CloudStack via a plug-in interface.
>
>
> On Wed, Mar 19, 2014 at 10:50 PM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
>> Hugo can talk about this in more depth, but the idea is that you develop
>> your feature in your own branch (every now and then rebasing your work on
>> top of what's been put into master to keep it current).
>>
>> At some point, there is what we call Feature Freeze (that was last week
>> Friday).
>>
>> On this day (ideally beforehand, if reasonably possible), all new features
>> must be taken from your branch and put into the master branch. At some
>> point in the day, a new branch - in this case, called 4.4 - is made and
>> then master is used for the release to follow 4.4.
>>
>> After Feature Freeze, all changes to 4.4 should be accompanied by a JIRA
>> ticket (ideally this would always be the case) and most of our 4.4 effort
>> is placed into testing what we have versus adding new features to it.
>>
>>
>> On Wed, Mar 19, 2014 at 10:44 PM, Pradeep Cloudstack <
>> pradeepcloudstack@yahoo.com> wrote:
>>
>>> Hi Sudha,Mike,Hogo,
>>> this is a new feature (and I am also new to the process)
>>> So I am not quite getting the meaning of "All merges are done last week".
>>>
>>> -Pradeep
>>>
>>>
>>>
>>>
>>> ________________________________
>>> From: Sudha Ponnaganti <su...@citrix.com>
>>> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep
>>> Cloudstack <pr...@yahoo.com>; Chiradeep Vittal <
>>> Chiradeep.Vittal@citrix.com>; Animesh Chaturvedi <
>>> animesh.chaturvedi@citrix.com>
>>> 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:pradeepcloudstack@yahoo.com]
>>> Sent: Wednesday, March 19, 2014 9:30 PM
>>> To: dev@cloudstack.apache.org; Chiradeep Vittal; Animesh Chaturvedi
>>> Subject: Re: 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 <mi...@solidfire.com>
>>> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep
>>> Cloudstack <pr...@yahoo.com>
>>> 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 features that are to go into 4.4 should
>>> have been in master on that day when the 4.4 branch was cut.
>>>
>>>
>>> On Wed, Mar 19, 2014 at 10:01 PM, Pradeep Cloudstack <
>>> pradeepcloudstack@yahoo.com> wrote:
>>>
>>>> What is the code-freeze date for 4.4 ?
>>>> I need to commit the following feature -
>>>>
>>>>
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
>>>>
>>>>
>>>> -Pradeep
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
>>>> sudha.ponnaganti@citrix.com> wrote:
>>>>
>>>> Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel
>>> comfortable
>>>> merging in my feature branch though when I pull from master and can no
>>>> longer run my own feature tests.
>>>>
>>>> On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
>>>>> I'm not sure what the offending ones are at the moment, and there was
>>>>> recently a feature merge that was not squashed, so it might be a
>>>>> little difficult to weed through.
>>>>>
>>>>> On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
>>>>> <su...@citrix.com>
>>>>> wrote:
>>>>>>
>>>>>> Can the offending check-ins be reverted or master be blocked for
>>>>>> further check-ins till blocking issue is fixed.
>>>>>> Talluri is running BVTs and can that be taken as basic passing
>>>>>> criteria to re-enable check-ins.
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
>>>>>> and I see that while I was sleeping others have reported some of the
>>>>>> issues I was seeing as well.
>>>>>>
>>>>>> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
>>>>>>> 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 the moment.
>>>>>>>> Let's take this discussion to the 4.5 release if we need to or
>>>>>>>> focus on doing a high quality release for 4.4 so we can focus on
>>>>>>>> features again in 4.4
>>>>>>>>
>>>>>>>> This means that the feature freeze would be this friday and i
>>>>>>>> intend to cut the 4.4 branch around 14:00 CET
>>>>>>>>
>>>>>>>> As we have a 72 hour window for MERGE requests, please make sure
>>>>>>>> they are in today (if the feature is ready).
>>>>>>>>
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Hugo
>>>>>>>
>>>>>>>
>>>>>>> Can someone confirm if this has made it in?
>>>>>>> https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>>>>>>>
>>>>>>> Marcus requested the MERGE a couple of days ago.
>>>>>>>
>>> http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
>>>>>>>
>>>>>>> Lucian
>>>>>>>
>>>>>>> --
>>>>>>> Sent from the Delta quadrant using Borg technology!
>>>>>>>
>>>>>>> Nux!
>>>>>>> www.nux.ro
>>>>
>>>
>>>
>>>
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkowski@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>
>>> *(tm)*
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
>
>> *(tm)*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
Re: 4.4 Feature Freeze
Posted by Pradeep Cloudstack <pr...@yahoo.com>.
Yes Mike
-Pradeep
________________________________
From: Mike Tutkowski <mi...@solidfire.com>
To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep Cloudstack <pr...@yahoo.com>
Cc: Chiradeep Vittal <Ch...@citrix.com>; Animesh Chaturvedi <an...@citrix.com>
Sent: Thursday, March 20, 2014 10:34 AM
Subject: Re: 4.4 Feature Freeze
It looks like your code is exclusively related to a network plug-in, is
that correct? In other words, you do not modify any CloudStack core code,
but rather solely interface with CloudStack via a plug-in interface.
On Wed, Mar 19, 2014 at 10:50 PM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:
> Hugo can talk about this in more depth, but the idea is that you develop
> your feature in your own branch (every now and then rebasing your work on
> top of what's been put into master to keep it current).
>
> At some point, there is what we call Feature Freeze (that was last week
> Friday).
>
> On this day (ideally beforehand, if reasonably possible), all new features
> must be taken from your branch and put into the master branch. At some
> point in the day, a new branch - in this case, called 4.4 - is made and
> then master is used for the release to follow 4.4.
>
> After Feature Freeze, all changes to 4.4 should be accompanied by a JIRA
> ticket (ideally this would always be the case) and most of our 4.4 effort
> is placed into testing what we have versus adding new features to it.
>
>
> On Wed, Mar 19, 2014 at 10:44 PM, Pradeep Cloudstack <
> pradeepcloudstack@yahoo.com> wrote:
>
>> Hi Sudha,Mike,Hogo,
>> this is a new feature (and I am also new to the process)
>> So I am not quite getting the meaning of "All merges are done last week".
>>
>> -Pradeep
>>
>>
>>
>>
>> ________________________________
>> From: Sudha Ponnaganti <su...@citrix.com>
>> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep
>> Cloudstack <pr...@yahoo.com>; Chiradeep Vittal <
>> Chiradeep.Vittal@citrix.com>; Animesh Chaturvedi <
>> animesh.chaturvedi@citrix.com>
>> 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:pradeepcloudstack@yahoo.com]
>> Sent: Wednesday, March 19, 2014 9:30 PM
>> To: dev@cloudstack.apache.org; Chiradeep Vittal; Animesh Chaturvedi
>> Subject: Re: 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 <mi...@solidfire.com>
>> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep
>> Cloudstack <pr...@yahoo.com>
>> 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 features that are to go into 4.4 should
>> have been in master on that day when the 4.4 branch was cut.
>>
>>
>> On Wed, Mar 19, 2014 at 10:01 PM, Pradeep Cloudstack <
>> pradeepcloudstack@yahoo.com> wrote:
>>
>> > What is the code-freeze date for 4.4 ?
>> > I need to commit the following feature -
>> >
>> >
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
>> >
>> >
>> > -Pradeep
>> >
>> >
>> >
>> >
>> >
>> > On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
>> > sudha.ponnaganti@citrix.com> wrote:
>> >
>> > Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel
>> comfortable
>> > merging in my feature branch though when I pull from master and can no
>> > longer run my own feature tests.
>> >
>> > On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
>> > > I'm not sure what the offending ones are at the moment, and there was
>> > > recently a feature merge that was not squashed, so it might be a
>> > > little difficult to weed through.
>> > >
>> > > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
>> > > <su...@citrix.com>
>> > > wrote:
>> > >>
>> > >> Can the offending check-ins be reverted or master be blocked for
>> > >> further check-ins till blocking issue is fixed.
>> > >> Talluri is running BVTs and can that be taken as basic passing
>> > >> criteria to re-enable check-ins.
>> > >>
>> > >> -----Original Message-----
>> > >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
>> > >> and I see that while I was sleeping others have reported some of the
>> > >> issues I was seeing as well.
>> > >>
>> > >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
>> > >> > 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 the moment.
>> > >> >> Let's take this discussion to the 4.5 release if we need to or
>> > >> >> focus on doing a high quality release for 4.4 so we can focus on
>> > >> >> features again in 4.4
>> > >> >>
>> > >> >> This means that the feature freeze would be this friday and i
>> > >> >> intend to cut the 4.4 branch around 14:00 CET
>> > >> >>
>> > >> >> As we have a 72 hour window for MERGE requests, please make sure
>> > >> >> they are in today (if the feature is ready).
>> > >> >>
>> > >> >>
>> > >> >> Cheers,
>> > >> >>
>> > >> >> Hugo
>> > >> >
>> > >> >
>> > >> > Can someone confirm if this has made it in?
>> > >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>> > >> >
>> > >> > Marcus requested the MERGE a couple of days ago.
>> > >> >
>> http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
>> > >> >
>> > >> > Lucian
>> > >> >
>> > >> > --
>> > >> > Sent from the Delta quadrant using Borg technology!
>> > >> >
>> > >> > Nux!
>> > >> > www.nux.ro
>> >
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud<http://solidfire.com/solution/overview/?video=play>
>>
>> *(tm)*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
It looks like your code is exclusively related to a network plug-in, is
that correct? In other words, you do not modify any CloudStack core code,
but rather solely interface with CloudStack via a plug-in interface.
On Wed, Mar 19, 2014 at 10:50 PM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:
> Hugo can talk about this in more depth, but the idea is that you develop
> your feature in your own branch (every now and then rebasing your work on
> top of what's been put into master to keep it current).
>
> At some point, there is what we call Feature Freeze (that was last week
> Friday).
>
> On this day (ideally beforehand, if reasonably possible), all new features
> must be taken from your branch and put into the master branch. At some
> point in the day, a new branch - in this case, called 4.4 - is made and
> then master is used for the release to follow 4.4.
>
> After Feature Freeze, all changes to 4.4 should be accompanied by a JIRA
> ticket (ideally this would always be the case) and most of our 4.4 effort
> is placed into testing what we have versus adding new features to it.
>
>
> On Wed, Mar 19, 2014 at 10:44 PM, Pradeep Cloudstack <
> pradeepcloudstack@yahoo.com> wrote:
>
>> Hi Sudha,Mike,Hogo,
>> this is a new feature (and I am also new to the process)
>> So I am not quite getting the meaning of "All merges are done last week".
>>
>> -Pradeep
>>
>>
>>
>>
>> ________________________________
>> From: Sudha Ponnaganti <su...@citrix.com>
>> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep
>> Cloudstack <pr...@yahoo.com>; Chiradeep Vittal <
>> Chiradeep.Vittal@citrix.com>; Animesh Chaturvedi <
>> animesh.chaturvedi@citrix.com>
>> 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:pradeepcloudstack@yahoo.com]
>> Sent: Wednesday, March 19, 2014 9:30 PM
>> To: dev@cloudstack.apache.org; Chiradeep Vittal; Animesh Chaturvedi
>> Subject: Re: 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 <mi...@solidfire.com>
>> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep
>> Cloudstack <pr...@yahoo.com>
>> 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 features that are to go into 4.4 should
>> have been in master on that day when the 4.4 branch was cut.
>>
>>
>> On Wed, Mar 19, 2014 at 10:01 PM, Pradeep Cloudstack <
>> pradeepcloudstack@yahoo.com> wrote:
>>
>> > What is the code-freeze date for 4.4 ?
>> > I need to commit the following feature -
>> >
>> >
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
>> >
>> >
>> > -Pradeep
>> >
>> >
>> >
>> >
>> >
>> > On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
>> > sudha.ponnaganti@citrix.com> wrote:
>> >
>> > Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel
>> comfortable
>> > merging in my feature branch though when I pull from master and can no
>> > longer run my own feature tests.
>> >
>> > On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
>> > > I'm not sure what the offending ones are at the moment, and there was
>> > > recently a feature merge that was not squashed, so it might be a
>> > > little difficult to weed through.
>> > >
>> > > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
>> > > <su...@citrix.com>
>> > > wrote:
>> > >>
>> > >> Can the offending check-ins be reverted or master be blocked for
>> > >> further check-ins till blocking issue is fixed.
>> > >> Talluri is running BVTs and can that be taken as basic passing
>> > >> criteria to re-enable check-ins.
>> > >>
>> > >> -----Original Message-----
>> > >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
>> > >> and I see that while I was sleeping others have reported some of the
>> > >> issues I was seeing as well.
>> > >>
>> > >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
>> > >> > 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 the moment.
>> > >> >> Let's take this discussion to the 4.5 release if we need to or
>> > >> >> focus on doing a high quality release for 4.4 so we can focus on
>> > >> >> features again in 4.4
>> > >> >>
>> > >> >> This means that the feature freeze would be this friday and i
>> > >> >> intend to cut the 4.4 branch around 14:00 CET
>> > >> >>
>> > >> >> As we have a 72 hour window for MERGE requests, please make sure
>> > >> >> they are in today (if the feature is ready).
>> > >> >>
>> > >> >>
>> > >> >> Cheers,
>> > >> >>
>> > >> >> Hugo
>> > >> >
>> > >> >
>> > >> > Can someone confirm if this has made it in?
>> > >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>> > >> >
>> > >> > Marcus requested the MERGE a couple of days ago.
>> > >> >
>> http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
>> > >> >
>> > >> > Lucian
>> > >> >
>> > >> > --
>> > >> > Sent from the Delta quadrant using Borg technology!
>> > >> >
>> > >> > Nux!
>> > >> > www.nux.ro
>> >
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud<http://solidfire.com/solution/overview/?video=play>
>>
>> *(tm)*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
Hugo can talk about this in more depth, but the idea is that you develop
your feature in your own branch (every now and then rebasing your work on
top of what's been put into master to keep it current).
At some point, there is what we call Feature Freeze (that was last week
Friday).
On this day (ideally beforehand, if reasonably possible), all new features
must be taken from your branch and put into the master branch. At some
point in the day, a new branch - in this case, called 4.4 - is made and
then master is used for the release to follow 4.4.
After Feature Freeze, all changes to 4.4 should be accompanied by a JIRA
ticket (ideally this would always be the case) and most of our 4.4 effort
is placed into testing what we have versus adding new features to it.
On Wed, Mar 19, 2014 at 10:44 PM, Pradeep Cloudstack <
pradeepcloudstack@yahoo.com> wrote:
> Hi Sudha,Mike,Hogo,
> this is a new feature (and I am also new to the process)
> So I am not quite getting the meaning of "All merges are done last week".
>
> -Pradeep
>
>
>
>
> ________________________________
> From: Sudha Ponnaganti <su...@citrix.com>
> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep
> Cloudstack <pr...@yahoo.com>; Chiradeep Vittal <
> Chiradeep.Vittal@citrix.com>; Animesh Chaturvedi <
> animesh.chaturvedi@citrix.com>
> 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:pradeepcloudstack@yahoo.com]
> Sent: Wednesday, March 19, 2014 9:30 PM
> To: dev@cloudstack.apache.org; Chiradeep Vittal; Animesh Chaturvedi
> Subject: Re: 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 <mi...@solidfire.com>
> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep
> Cloudstack <pr...@yahoo.com>
> 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 features that are to go into 4.4 should
> have been in master on that day when the 4.4 branch was cut.
>
>
> On Wed, Mar 19, 2014 at 10:01 PM, Pradeep Cloudstack <
> pradeepcloudstack@yahoo.com> wrote:
>
> > What is the code-freeze date for 4.4 ?
> > I need to commit the following feature -
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
> >
> >
> > -Pradeep
> >
> >
> >
> >
> >
> > On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com> wrote:
> >
> > Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel
> comfortable
> > merging in my feature branch though when I pull from master and can no
> > longer run my own feature tests.
> >
> > On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> > > I'm not sure what the offending ones are at the moment, and there was
> > > recently a feature merge that was not squashed, so it might be a
> > > little difficult to weed through.
> > >
> > > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
> > > <su...@citrix.com>
> > > wrote:
> > >>
> > >> Can the offending check-ins be reverted or master be blocked for
> > >> further check-ins till blocking issue is fixed.
> > >> Talluri is running BVTs and can that be taken as basic passing
> > >> criteria to re-enable check-ins.
> > >>
> > >> -----Original Message-----
> > >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
> > >> and I see that while I was sleeping others have reported some of the
> > >> issues I was seeing as well.
> > >>
> > >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> > >> > 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 the moment.
> > >> >> Let's take this discussion to the 4.5 release if we need to or
> > >> >> focus on doing a high quality release for 4.4 so we can focus on
> > >> >> features again in 4.4
> > >> >>
> > >> >> This means that the feature freeze would be this friday and i
> > >> >> intend to cut the 4.4 branch around 14:00 CET
> > >> >>
> > >> >> As we have a 72 hour window for MERGE requests, please make sure
> > >> >> they are in today (if the feature is ready).
> > >> >>
> > >> >>
> > >> >> Cheers,
> > >> >>
> > >> >> Hugo
> > >> >
> > >> >
> > >> > Can someone confirm if this has made it in?
> > >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> > >> >
> > >> > Marcus requested the MERGE a couple of days ago.
> > >> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
> > >> >
> > >> > Lucian
> > >> >
> > >> > --
> > >> > Sent from the Delta quadrant using Borg technology!
> > >> >
> > >> > Nux!
> > >> > www.nux.ro
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
>
> *(tm)*
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Pradeep Cloudstack <pr...@yahoo.com>.
Hi Sudha,Mike,Hogo,
this is a new feature (and I am also new to the process)
So I am not quite getting the meaning of "All merges are done last week".
-Pradeep
________________________________
From: Sudha Ponnaganti <su...@citrix.com>
To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep Cloudstack <pr...@yahoo.com>; Chiradeep Vittal <Ch...@citrix.com>; Animesh Chaturvedi <an...@citrix.com>
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:pradeepcloudstack@yahoo.com]
Sent: Wednesday, March 19, 2014 9:30 PM
To: dev@cloudstack.apache.org; Chiradeep Vittal; Animesh Chaturvedi
Subject: Re: 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 <mi...@solidfire.com>
To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep Cloudstack <pr...@yahoo.com>
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 features that are to go into 4.4 should
have been in master on that day when the 4.4 branch was cut.
On Wed, Mar 19, 2014 at 10:01 PM, Pradeep Cloudstack <
pradeepcloudstack@yahoo.com> wrote:
> What is the code-freeze date for 4.4 ?
> I need to commit the following feature -
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
>
>
> -Pradeep
>
>
>
>
>
> On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com> wrote:
>
> Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel comfortable
> merging in my feature branch though when I pull from master and can no
> longer run my own feature tests.
>
> On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> > I'm not sure what the offending ones are at the moment, and there was
> > recently a feature merge that was not squashed, so it might be a
> > little difficult to weed through.
> >
> > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
> > <su...@citrix.com>
> > wrote:
> >>
> >> Can the offending check-ins be reverted or master be blocked for
> >> further check-ins till blocking issue is fixed.
> >> Talluri is running BVTs and can that be taken as basic passing
> >> criteria to re-enable check-ins.
> >>
> >> -----Original Message-----
> >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
> >> and I see that while I was sleeping others have reported some of the
> >> issues I was seeing as well.
> >>
> >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> >> > 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 the moment.
> >> >> Let's take this discussion to the 4.5 release if we need to or
> >> >> focus on doing a high quality release for 4.4 so we can focus on
> >> >> features again in 4.4
> >> >>
> >> >> This means that the feature freeze would be this friday and i
> >> >> intend to cut the 4.4 branch around 14:00 CET
> >> >>
> >> >> As we have a 72 hour window for MERGE requests, please make sure
> >> >> they are in today (if the feature is ready).
> >> >>
> >> >>
> >> >> Cheers,
> >> >>
> >> >> Hugo
> >> >
> >> >
> >> > Can someone confirm if this has made it in?
> >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> >> >
> >> > Marcus requested the MERGE a couple of days ago.
> >> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
> >> >
> >> > Lucian
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
RE: 4.4 Feature Freeze
Posted by Sudha Ponnaganti <su...@citrix.com>.
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:pradeepcloudstack@yahoo.com]
Sent: Wednesday, March 19, 2014 9:30 PM
To: dev@cloudstack.apache.org; Chiradeep Vittal; Animesh Chaturvedi
Subject: Re: 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 <mi...@solidfire.com>
To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep Cloudstack <pr...@yahoo.com>
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 features that are to go into 4.4 should
have been in master on that day when the 4.4 branch was cut.
On Wed, Mar 19, 2014 at 10:01 PM, Pradeep Cloudstack <
pradeepcloudstack@yahoo.com> wrote:
> What is the code-freeze date for 4.4 ?
> I need to commit the following feature -
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
>
>
> -Pradeep
>
>
>
>
>
> On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com> wrote:
>
> Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel comfortable
> merging in my feature branch though when I pull from master and can no
> longer run my own feature tests.
>
> On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> > I'm not sure what the offending ones are at the moment, and there was
> > recently a feature merge that was not squashed, so it might be a
> > little difficult to weed through.
> >
> > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
> > <su...@citrix.com>
> > wrote:
> >>
> >> Can the offending check-ins be reverted or master be blocked for
> >> further check-ins till blocking issue is fixed.
> >> Talluri is running BVTs and can that be taken as basic passing
> >> criteria to re-enable check-ins.
> >>
> >> -----Original Message-----
> >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
> >> and I see that while I was sleeping others have reported some of the
> >> issues I was seeing as well.
> >>
> >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> >> > 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 the moment.
> >> >> Let's take this discussion to the 4.5 release if we need to or
> >> >> focus on doing a high quality release for 4.4 so we can focus on
> >> >> features again in 4.4
> >> >>
> >> >> This means that the feature freeze would be this friday and i
> >> >> intend to cut the 4.4 branch around 14:00 CET
> >> >>
> >> >> As we have a 72 hour window for MERGE requests, please make sure
> >> >> they are in today (if the feature is ready).
> >> >>
> >> >>
> >> >> Cheers,
> >> >>
> >> >> Hugo
> >> >
> >> >
> >> > Can someone confirm if this has made it in?
> >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> >> >
> >> > Marcus requested the MERGE a couple of days ago.
> >> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
> >> >
> >> > Lucian
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
At this point, I'd recommend talking to Hugo, who is the release manager
for 4.4.
I've CCed him on this message (although he's on the normal dev@ mailing
list, as well).
On Wed, Mar 19, 2014 at 10:29 PM, Pradeep Cloudstack <
pradeepcloudstack@yahoo.com> wrote:
> 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 <mi...@solidfire.com>
> To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep
> Cloudstack <pr...@yahoo.com>
> 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 features that are to go into 4.4 should
> have been in master on that day when the 4.4 branch was cut.
>
>
> On Wed, Mar 19, 2014 at 10:01 PM, Pradeep Cloudstack <
> pradeepcloudstack@yahoo.com> wrote:
>
> > What is the code-freeze date for 4.4 ?
> > I need to commit the following feature -
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
> >
> >
> > -Pradeep
> >
> >
> >
> >
> >
> > On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
> > sudha.ponnaganti@citrix.com> wrote:
> >
> > Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel
> comfortable
> > merging in my feature branch though when I pull from master and can no
> > longer run my own feature tests.
> >
> > On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> > > I'm not sure what the offending ones are at the moment, and there was
> > > recently a feature merge that was not squashed, so it might be a
> > > little difficult to weed through.
> > >
> > > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
> > > <su...@citrix.com>
> > > wrote:
> > >>
> > >> Can the offending check-ins be reverted or master be blocked for
> > >> further check-ins till blocking issue is fixed.
> > >> Talluri is running BVTs and can that be taken as basic passing
> > >> criteria to re-enable check-ins.
> > >>
> > >> -----Original Message-----
> > >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
> > >> and I see that while I was sleeping others have reported some of the
> > >> issues I was seeing as well.
> > >>
> > >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> > >> > 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 the moment.
> > >> >> Let's take this discussion to the 4.5 release if we need to or
> > >> >> focus on doing a high quality release for 4.4 so we can focus on
> > >> >> features again in 4.4
> > >> >>
> > >> >> This means that the feature freeze would be this friday and i
> > >> >> intend to cut the 4.4 branch around 14:00 CET
> > >> >>
> > >> >> As we have a 72 hour window for MERGE requests, please make sure
> > >> >> they are in today (if the feature is ready).
> > >> >>
> > >> >>
> > >> >> Cheers,
> > >> >>
> > >> >> Hugo
> > >> >
> > >> >
> > >> > Can someone confirm if this has made it in?
> > >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> > >> >
> > >> > Marcus requested the MERGE a couple of days ago.
> > >> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
> > >> >
> > >> > Lucian
> > >> >
> > >> > --
> > >> > Sent from the Delta quadrant using Borg technology!
> > >> >
> > >> > Nux!
> > >> > www.nux.ro
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
>
> *(tm)*
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Pradeep Cloudstack <pr...@yahoo.com>.
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 <mi...@solidfire.com>
To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org>; Pradeep Cloudstack <pr...@yahoo.com>
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 features that are to go into 4.4 should
have been in master on that day when the 4.4 branch was cut.
On Wed, Mar 19, 2014 at 10:01 PM, Pradeep Cloudstack <
pradeepcloudstack@yahoo.com> wrote:
> What is the code-freeze date for 4.4 ?
> I need to commit the following feature -
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
>
>
> -Pradeep
>
>
>
>
>
> On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com> wrote:
>
> Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel comfortable
> merging in my feature branch though when I pull from master and can no
> longer run my own feature tests.
>
> On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> > I'm not sure what the offending ones are at the moment, and there was
> > recently a feature merge that was not squashed, so it might be a
> > little difficult to weed through.
> >
> > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
> > <su...@citrix.com>
> > wrote:
> >>
> >> Can the offending check-ins be reverted or master be blocked for
> >> further check-ins till blocking issue is fixed.
> >> Talluri is running BVTs and can that be taken as basic passing
> >> criteria to re-enable check-ins.
> >>
> >> -----Original Message-----
> >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
> >> and I see that while I was sleeping others have reported some of the
> >> issues I was seeing as well.
> >>
> >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> >> > 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 the moment.
> >> >> Let's take this discussion to the 4.5 release if we need to or
> >> >> focus on doing a high quality release for 4.4 so we can focus on
> >> >> features again in 4.4
> >> >>
> >> >> This means that the feature freeze would be this friday and i
> >> >> intend to cut the 4.4 branch around 14:00 CET
> >> >>
> >> >> As we have a 72 hour window for MERGE requests, please make sure
> >> >> they are in today (if the feature is ready).
> >> >>
> >> >>
> >> >> Cheers,
> >> >>
> >> >> Hugo
> >> >
> >> >
> >> > Can someone confirm if this has made it in?
> >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> >> >
> >> > Marcus requested the MERGE a couple of days ago.
> >> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
> >> >
> >> > Lucian
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
I'm not sure if we have a "code freeze" per se, but "feature freeze" was
last week Friday. Technically all features that are to go into 4.4 should
have been in master on that day when the 4.4 branch was cut.
On Wed, Mar 19, 2014 at 10:01 PM, Pradeep Cloudstack <
pradeepcloudstack@yahoo.com> wrote:
> What is the code-freeze date for 4.4 ?
> I need to commit the following feature -
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
>
>
> -Pradeep
>
>
>
>
>
> On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <
> sudha.ponnaganti@citrix.com> wrote:
>
> Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel comfortable
> merging in my feature branch though when I pull from master and can no
> longer run my own feature tests.
>
> On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> > I'm not sure what the offending ones are at the moment, and there was
> > recently a feature merge that was not squashed, so it might be a
> > little difficult to weed through.
> >
> > On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
> > <su...@citrix.com>
> > wrote:
> >>
> >> Can the offending check-ins be reverted or master be blocked for
> >> further check-ins till blocking issue is fixed.
> >> Talluri is running BVTs and can that be taken as basic passing
> >> criteria to re-enable check-ins.
> >>
> >> -----Original Message-----
> >> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
> >> and I see that while I was sleeping others have reported some of the
> >> issues I was seeing as well.
> >>
> >> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> >> > 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 the moment.
> >> >> Let's take this discussion to the 4.5 release if we need to or
> >> >> focus on doing a high quality release for 4.4 so we can focus on
> >> >> features again in 4.4
> >> >>
> >> >> This means that the feature freeze would be this friday and i
> >> >> intend to cut the 4.4 branch around 14:00 CET
> >> >>
> >> >> As we have a 72 hour window for MERGE requests, please make sure
> >> >> they are in today (if the feature is ready).
> >> >>
> >> >>
> >> >> Cheers,
> >> >>
> >> >> Hugo
> >> >
> >> >
> >> > Can someone confirm if this has made it in?
> >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> >> >
> >> > Marcus requested the MERGE a couple of days ago.
> >> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
> >> >
> >> > Lucian
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Pradeep Cloudstack <pr...@yahoo.com>.
What is the code-freeze date for 4.4 ?
I need to commit the following feature -
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=36274178
-Pradeep
On Friday, March 14, 2014 8:13 PM, Sudha Ponnaganti <su...@citrix.com> wrote:
Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel comfortable merging in my feature branch though when I pull from master and can no longer run my own feature tests.
On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> I'm not sure what the offending ones are at the moment, and there was
> recently a feature merge that was not squashed, so it might be a
> little difficult to weed through.
>
> On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
> <su...@citrix.com>
> wrote:
>>
>> Can the offending check-ins be reverted or master be blocked for
>> further check-ins till blocking issue is fixed.
>> Talluri is running BVTs and can that be taken as basic passing
>> criteria to re-enable check-ins.
>>
>> -----Original Message-----
>> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
>> and I see that while I was sleeping others have reported some of the
>> issues I was seeing as well.
>>
>> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
>> > 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 the moment.
>> >> Let's take this discussion to the 4.5 release if we need to or
>> >> focus on doing a high quality release for 4.4 so we can focus on
>> >> features again in 4.4
>> >>
>> >> This means that the feature freeze would be this friday and i
>> >> intend to cut the 4.4 branch around 14:00 CET
>> >>
>> >> As we have a 72 hour window for MERGE requests, please make sure
>> >> they are in today (if the feature is ready).
>> >>
>> >>
>> >> Cheers,
>> >>
>> >> Hugo
>> >
>> >
>> > Can someone confirm if this has made it in?
>> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>> >
>> > Marcus requested the MERGE a couple of days ago.
>> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
>> >
>> > Lucian
>> >
>> > --
>> > Sent from the Delta quadrant using Borg technology!
>> >
>> > Nux!
>> > www.nux.ro
RE: 4.4 Feature Freeze
Posted by Sudha Ponnaganti <su...@citrix.com>.
Other alternative is to block further check-ins till blocking 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:shadowsor@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. Obviously I don't feel comfortable merging in my feature branch though when I pull from master and can no longer run my own feature tests.
On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> I'm not sure what the offending ones are at the moment, and there was
> recently a feature merge that was not squashed, so it might be a
> little difficult to weed through.
>
> On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti"
> <su...@citrix.com>
> wrote:
>>
>> Can the offending check-ins be reverted or master be blocked for
>> further check-ins till blocking issue is fixed.
>> Talluri is running BVTs and can that be taken as basic passing
>> criteria to re-enable check-ins.
>>
>> -----Original Message-----
>> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master,
>> and I see that while I was sleeping others have reported some of the
>> issues I was seeing as well.
>>
>> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
>> > 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 the moment.
>> >> Let's take this discussion to the 4.5 release if we need to or
>> >> focus on doing a high quality release for 4.4 so we can focus on
>> >> features again in 4.4
>> >>
>> >> This means that the feature freeze would be this friday and i
>> >> intend to cut the 4.4 branch around 14:00 CET
>> >>
>> >> As we have a 72 hour window for MERGE requests, please make sure
>> >> they are in today (if the feature is ready).
>> >>
>> >>
>> >> Cheers,
>> >>
>> >> Hugo
>> >
>> >
>> > Can someone confirm if this has made it in?
>> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>> >
>> > Marcus requested the MERGE a couple of days ago.
>> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
>> >
>> > Lucian
>> >
>> > --
>> > Sent from the Delta quadrant using Borg technology!
>> >
>> > Nux!
>> > www.nux.ro
Re: 4.4 Feature Freeze
Posted by Marcus <sh...@gmail.com>.
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 feature tests.
On Fri, Mar 14, 2014 at 8:35 AM, Marcus <sh...@gmail.com> wrote:
> I'm not sure what the offending ones are at the moment, and there was
> recently a feature merge that was not squashed, so it might be a little
> difficult to weed through.
>
> On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti" <su...@citrix.com>
> wrote:
>>
>> Can the offending check-ins be reverted or master be blocked for further
>> check-ins till blocking issue is fixed.
>> Talluri is running BVTs and can that be taken as basic passing criteria to
>> re-enable check-ins.
>>
>> -----Original Message-----
>> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master, and I see that
>> while I was sleeping others have reported some of the issues I was seeing as
>> well.
>>
>> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
>> > 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 the moment. Let's take
>> >> this discussion to the 4.5 release if we need to or focus on doing a
>> >> high quality release for 4.4 so we can focus on features again in 4.4
>> >>
>> >> This means that the feature freeze would be this friday and i intend
>> >> to cut the 4.4 branch around 14:00 CET
>> >>
>> >> As we have a 72 hour window for MERGE requests, please make sure they
>> >> are in today (if the feature is ready).
>> >>
>> >>
>> >> Cheers,
>> >>
>> >> Hugo
>> >
>> >
>> > Can someone confirm if this has made it in?
>> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>> >
>> > Marcus requested the MERGE a couple of days ago.
>> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
>> >
>> > Lucian
>> >
>> > --
>> > Sent from the Delta quadrant using Borg technology!
>> >
>> > Nux!
>> > www.nux.ro
RE: 4.4 Feature Freeze
Posted by Marcus <sh...@gmail.com>.
I'm not sure what the offending ones are at the moment, and there was
recently a feature merge that was not squashed, so it might be a little
difficult to weed through.
On Mar 14, 2014 7:45 AM, "Sudha Ponnaganti" <su...@citrix.com>
wrote:
> Can the offending check-ins be reverted or master be blocked for further
> check-ins till blocking issue is fixed.
> Talluri is running BVTs and can that be taken as basic passing criteria to
> re-enable check-ins.
>
> -----Original Message-----
> From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master, and I see that
> while I was sleeping others have reported some of the issues I was seeing
> as well.
>
> On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> > 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 the moment. Let's take
> >> this discussion to the 4.5 release if we need to or focus on doing a
> >> high quality release for 4.4 so we can focus on features again in 4.4
> >>
> >> This means that the feature freeze would be this friday and i intend
> >> to cut the 4.4 branch around 14:00 CET
> >>
> >> As we have a 72 hour window for MERGE requests, please make sure they
> >> are in today (if the feature is ready).
> >>
> >>
> >> Cheers,
> >>
> >> Hugo
> >
> >
> > Can someone confirm if this has made it in?
> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> >
> > Marcus requested the MERGE a couple of days ago.
> > http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
> >
> > Lucian
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
>
RE: 4.4 Feature Freeze
Posted by Sudha Ponnaganti <su...@citrix.com>.
Can the offending check-ins be reverted or master be blocked for further check-ins till blocking issue is fixed.
Talluri is running BVTs and can that be taken as basic passing criteria to re-enable check-ins.
-----Original Message-----
From: Marcus [mailto:shadowsor@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 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't even get a vm running with the current master, and I see that while I was sleeping others have reported some of the issues I was seeing as well.
On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> 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 the moment. Let's take
>> this discussion to the 4.5 release if we need to or focus on doing a
>> high quality release for 4.4 so we can focus on features again in 4.4
>>
>> This means that the feature freeze would be this friday and i intend
>> to cut the 4.4 branch around 14:00 CET
>>
>> As we have a 72 hour window for MERGE requests, please make sure they
>> are in today (if the feature is ready).
>>
>>
>> Cheers,
>>
>> Hugo
>
>
> Can someone confirm if this has made it in?
> https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>
> Marcus requested the MERGE a couple of days ago.
> http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
Re: 4.4 Feature Freeze
Posted by Marcus <sh...@gmail.com>.
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't even get a vm running with the current master,
and I see that while I was sleeping others have reported some of the
issues I was seeing as well.
On Fri, Mar 14, 2014 at 3:43 AM, Nux! <nu...@li.nux.ro> wrote:
> 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 the moment. Let's take
>> this discussion to the 4.5 release if we need to or focus on doing a
>> high quality release for 4.4 so we can focus on features again in 4.4
>>
>> This means that the feature freeze would be this friday and i intend
>> to cut the 4.4 branch around 14:00 CET
>>
>> As we have a 72 hour window for MERGE requests, please make sure they
>> are in today (if the feature is ready).
>>
>>
>> Cheers,
>>
>> Hugo
>
>
> Can someone confirm if this has made it in?
> https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>
> Marcus requested the MERGE a couple of days ago.
> http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
Re: 4.4 Feature Freeze
Posted by Nux! <nu...@li.nux.ro>.
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 the moment. Let’s take
> this discussion to the 4.5 release if we need to or focus on doing a
> high quality release for 4.4 so we can focus on features again in 4.4
>
> This means that the feature freeze would be this friday and i intend
> to cut the 4.4 branch around 14:00 CET
>
> As we have a 72 hour window for MERGE requests, please make sure they
> are in today (if the feature is ready).
>
>
> Cheers,
>
> Hugo
Can someone confirm if this has made it in?
https://issues.apache.org/jira/browse/CLOUDSTACK-6181
Marcus requested the MERGE a couple of days ago.
http://www.mail-archive.com/dev@cloudstack.apache.org/msg24793.html
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
RE: 4.4 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
Hugo
Folks in USA will still have their day shining on 3/14. Can you cut it after the day in USA is over in PST time
Animesh
> -----Original Message-----
> From: Trippie [mailto:trippie@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 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 the 4.5 release if we need
> to or focus on doing a high quality release for 4.4 so we can focus on
> features again in 4.4
>
> This means that the feature freeze would be this friday and i intend to cut
> the 4.4 branch around 14:00 CET
>
> As we have a 72 hour window for MERGE requests, please make sure they
> are in today (if the feature is ready).
>
>
> Cheers,
>
> Hugo
>
>
>
RE: 4.4 Feature Freeze
Posted by Sudha Ponnaganti <su...@citrix.com>.
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 releases if that is okay.
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases+in+Progress
Thanks
/Sudha
-----Original Message-----
From: Trippie [mailto:trippie@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 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 the 4.5 release if we need to or focus on doing a high quality release for 4.4 so we can focus on features again in 4.4
This means that the feature freeze would be this friday and i intend to cut the 4.4 branch around 14:00 CET
As we have a 72 hour window for MERGE requests, please make sure they are in today (if the feature is ready).
Cheers,
Hugo
Re: 4.4 Feature Freeze
Posted by Hugo Trippaers <hu...@trippaers.nl>.
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 the 4.5 release if we need to or focus on doing a high quality release for 4.4 so we can focus on features again in 4.4
This means that the feature freeze would be this friday and i intend to cut the 4.4 branch around 14:00 CET
As we have a 72 hour window for MERGE requests, please make sure they are in today (if the feature is ready).
Cheers,
Hugo
RE: 4.4 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Sebastien Goasguen [mailto:runseb@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
> <an...@citrix.com> wrote:
>
> >
> >
> >> -----Original Message-----
> >> From: Sebastien Goasguen [mailto:runseb@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 code into the release.
> >>
> > [Animesh] That is not right, for 4.3 I had called out feature freeze date
> clearly and do not recall new feature added. IMHO the one challenge as
> community that we have which has been raised earlier also is QA
> contribution is primarily coming from one organization. Most other folks
> start taking the release for a spin only after RC2/RC3 or so and then we see
> additional issues and more re-spins. We really have to get all engaged in
> testing much earlier in the cycle. Sudha used to call out for help on QA
> activity but in prior releases I don't think she got much volunteers. We have
> huge technical debt and that is not going to go away with pointing fingers. If
> a specific scenario is benefiting someone as a user/developer of CloudStack
> and it turns out is not guarded with automation sufficiently and regresses in
> a release shouldn't the person using it also take some responsibility for
> safeguarding it with automation?
> >
>
>
> Of course everyone is a stakeholder in making CloudStack a high quality
> software.
>
> I am not pointing fingers at anyone I am just expressing my perception of
> what is going on. I have seen several things lately where it seems that we
> prefer to put half-baked features in a major release rather than wait.
>
> Say we release every 6 months, since releases are far apart this puts stress
> on the developer to put his feature "in" before feature freeze, perhaps
> sacrificing quality and testing. If we were to release more often then the
> stress to "miss" a release would be alleviated.
[Animesh] I need some more time to rationalize and put together mu thoughts on 6 months v/s 4 months. But my first priority is 4.3 so will come to it later
>
> I'd rather see/know that developers don't rush their features because they
> know they can see it in less than 4 months then see features being added to
> a release in fear of missing a cycle.
>
> The issue of QA is another one. Personally I'd like to start testing a release
> branch once code has stabilized and I'd prefer to see a RM lock down on the
> release before testing.
[Animesh] As soon as we did the first RC I had created the forward branch and 4.3 branch checkins were not allowed
What we have seen (and I'd be happy to be wrong), is
> lots of code changes -a lot of times without bug ids- even after an RC was
> out (even though this got corrected in the latest RC).
[Animesh] I hate that too, I had called out to many folks that we need a bug ID for any cherry-pick.
When there is so much
> churn on a release so close to an RC being cut it really is not conducive to
> testing. Maybe the churn is not an issue, but imho I would like to see every
> commit being with a bug ID and being a direct decision of the RM.
[Animesh] Certainly once I have wrapped up 4.3 I will put a report for each RC to help us analyze how can we improve. Even during RCs most feedback came from only a few handful of people, may be other community members were testing but did not provide feedback but atleast from the data it does looks like testing involvement even during RCs is limited. Once we get a -1 on RC I think people holdback on testing and then next RC we find something else.
>
> -Sebastien
RE: 4.4 Feature Freeze
Posted by Paul Angus <pa...@shapeblue.com>.
To stick my oar in,
I think that 3 days is too short a time for people to get round to doing meaningful testing, particularly for those of us doing it on a purely voluntary basis.
Also I got the feeling that we were spinning up new RCs before it was clear that all issues with the previous RC had been fixed and committed.
Maybe a -1 has to be accompanied by a Jira ticket marked as a blocker. People should carry on testing an RC after it's vote has been cancelled and adding -1s and Jira blockers tickets, to avoid a new RC which is going to be -1ed immediately... Once the blockers are cleared we should be good to go for the next RC.
Regards
Paul Angus
Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus
paul.angus@shapeblue.com
-----Original Message-----
From: Daan Hoogland [mailto:daan.hoogland@gmail.com]
Sent: 04 March 2014 15:55
To: dev
Subject: 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 bothering him.
However, Sebastien makes a very good point and I would go further. In my opinion we shouldn't be talking about how many months we keep between releases. If I make a new feature I want it scrutinized by all the guru's. Once they have nothing to nag about anymore it should be in in less then a month. We are a long way from that, but having to plan a feature in advance is never going to advance quality and instead will always be a constraint on it.
I could make the finger pointing point as well; At Schuberg Philis we are dedicating a lot of effort to quality, both by tracking bug findings and by setting up an automated test environment. I would prefer to spend this energy in making nice features for the next release. There is seven of us now and I don't think we spend one seventh of our energy/time in new features over the last period. The next release is containing a bunch of features already that won't be stable from the get go anyway. let's make a good product before we make it greater.
So, can we find common ground on this issue? My take, rather one feature per release (each week) with high quality and intensive testing then three features with divided attention to the code involved. This is not a proposal, yet. Just an illustration of my emotions.
kind regards,
Daan
On Tue, Mar 4, 2014 at 1:45 PM, Sebastien Goasguen <ru...@gmail.com> wrote:
>
> On Mar 3, 2014, at 8:18 PM, Animesh Chaturvedi <an...@citrix.com> wrote:
>
>>
>>
>>> -----Original Message-----
>>> From: Sebastien Goasguen [mailto:runseb@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 code into the release.
>>>
>> [Animesh] That is not right, for 4.3 I had called out feature freeze date clearly and do not recall new feature added. IMHO the one challenge as community that we have which has been raised earlier also is QA contribution is primarily coming from one organization. Most other folks start taking the release for a spin only after RC2/RC3 or so and then we see additional issues and more re-spins. We really have to get all engaged in testing much earlier in the cycle. Sudha used to call out for help on QA activity but in prior releases I don't think she got much volunteers. We have huge technical debt and that is not going to go away with pointing fingers. If a specific scenario is benefiting someone as a user/developer of CloudStack and it turns out is not guarded with automation sufficiently and regresses in a release shouldn't the person using it also take some responsibility for safeguarding it with automation?
>>
>
>
> Of course everyone is a stakeholder in making CloudStack a high quality software.
>
> I am not pointing fingers at anyone I am just expressing my perception of what is going on. I have seen several things lately where it seems that we prefer to put half-baked features in a major release rather than wait.
>
> Say we release every 6 months, since releases are far apart this puts stress on the developer to put his feature "in" before feature freeze, perhaps sacrificing quality and testing. If we were to release more often then the stress to "miss" a release would be alleviated.
>
> I'd rather see/know that developers don't rush their features because they know they can see it in less than 4 months then see features being added to a release in fear of missing a cycle.
>
> The issue of QA is another one. Personally I'd like to start testing a release branch once code has stabilized and I'd prefer to see a RM lock down on the release before testing. What we have seen (and I'd be happy to be wrong), is lots of code changes -a lot of times without bug ids- even after an RC was out (even though this got corrected in the latest RC). When there is so much churn on a release so close to an RC being cut it really is not conducive to testing. Maybe the churn is not an issue, but imho I would like to see every commit being with a bug ID and being a direct decision of the RM.
>
> -Sebastien
>
--
Daan
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments.
Apache CloudStack Bootcamp training courses
**NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/>
18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/>
17th-23rd March 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
24th-28th March 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
16th-20th June 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
23rd-27th June 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: 4.4 Feature Freeze
Posted by Daan Hoogland <da...@gmail.com>.
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 bothering him.
However, Sebastien makes a very good point and I would go further. In
my opinion we shouldn't be talking about how many months we keep
between releases. If I make a new feature I want it scrutinized by all
the guru's. Once they have nothing to nag about anymore it should be
in in less then a month. We are a long way from that, but having to
plan a feature in advance is never going to advance quality and
instead will always be a constraint on it.
I could make the finger pointing point as well; At Schuberg Philis we
are dedicating a lot of effort to quality, both by tracking bug
findings and by setting up an automated test environment. I would
prefer to spend this energy in making nice features for the next
release. There is seven of us now and I don't think we spend one
seventh of our energy/time in new features over the last period. The
next release is containing a bunch of features already that won't be
stable from the get go anyway. let's make a good product before we
make it greater.
So, can we find common ground on this issue? My take, rather one
feature per release (each week) with high quality and intensive
testing then three features with divided attention to the code
involved. This is not a proposal, yet. Just an illustration of my
emotions.
kind regards,
Daan
On Tue, Mar 4, 2014 at 1:45 PM, Sebastien Goasguen <ru...@gmail.com> wrote:
>
> On Mar 3, 2014, at 8:18 PM, Animesh Chaturvedi <an...@citrix.com> wrote:
>
>>
>>
>>> -----Original Message-----
>>> From: Sebastien Goasguen [mailto:runseb@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
>>> code into the release.
>>>
>> [Animesh] That is not right, for 4.3 I had called out feature freeze date clearly and do not recall new feature added. IMHO the one challenge as community that we have which has been raised earlier also is QA contribution is primarily coming from one organization. Most other folks start taking the release for a spin only after RC2/RC3 or so and then we see additional issues and more re-spins. We really have to get all engaged in testing much earlier in the cycle. Sudha used to call out for help on QA activity but in prior releases I don't think she got much volunteers. We have huge technical debt and that is not going to go away with pointing fingers. If a specific scenario is benefiting someone as a user/developer of CloudStack and it turns out is not guarded with automation sufficiently and regresses in a release shouldn't the person using it also take some responsibility for safeguarding it with automation?
>>
>
>
> Of course everyone is a stakeholder in making CloudStack a high quality software.
>
> I am not pointing fingers at anyone I am just expressing my perception of what is going on. I have seen several things lately where it seems that we prefer to put half-baked features in a major release rather than wait.
>
> Say we release every 6 months, since releases are far apart this puts stress on the developer to put his feature "in" before feature freeze, perhaps sacrificing quality and testing. If we were to release more often then the stress to "miss" a release would be alleviated.
>
> I'd rather see/know that developers don't rush their features because they know they can see it in less than 4 months then see features being added to a release in fear of missing a cycle.
>
> The issue of QA is another one. Personally I'd like to start testing a release branch once code has stabilized and I'd prefer to see a RM lock down on the release before testing. What we have seen (and I'd be happy to be wrong), is lots of code changes -a lot of times without bug ids- even after an RC was out (even though this got corrected in the latest RC). When there is so much churn on a release so close to an RC being cut it really is not conducive to testing. Maybe the churn is not an issue, but imho I would like to see every commit being with a bug ID and being a direct decision of the RM.
>
> -Sebastien
>
--
Daan
Re: 4.4 Feature Freeze
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Mar 3, 2014, at 8:18 PM, Animesh Chaturvedi <an...@citrix.com> wrote:
>
>
>> -----Original Message-----
>> From: Sebastien Goasguen [mailto:runseb@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
>> code into the release.
>>
> [Animesh] That is not right, for 4.3 I had called out feature freeze date clearly and do not recall new feature added. IMHO the one challenge as community that we have which has been raised earlier also is QA contribution is primarily coming from one organization. Most other folks start taking the release for a spin only after RC2/RC3 or so and then we see additional issues and more re-spins. We really have to get all engaged in testing much earlier in the cycle. Sudha used to call out for help on QA activity but in prior releases I don't think she got much volunteers. We have huge technical debt and that is not going to go away with pointing fingers. If a specific scenario is benefiting someone as a user/developer of CloudStack and it turns out is not guarded with automation sufficiently and regresses in a release shouldn't the person using it also take some responsibility for safeguarding it with automation?
>
Of course everyone is a stakeholder in making CloudStack a high quality software.
I am not pointing fingers at anyone I am just expressing my perception of what is going on. I have seen several things lately where it seems that we prefer to put half-baked features in a major release rather than wait.
Say we release every 6 months, since releases are far apart this puts stress on the developer to put his feature "in" before feature freeze, perhaps sacrificing quality and testing. If we were to release more often then the stress to "miss" a release would be alleviated.
I'd rather see/know that developers don't rush their features because they know they can see it in less than 4 months then see features being added to a release in fear of missing a cycle.
The issue of QA is another one. Personally I'd like to start testing a release branch once code has stabilized and I'd prefer to see a RM lock down on the release before testing. What we have seen (and I'd be happy to be wrong), is lots of code changes -a lot of times without bug ids- even after an RC was out (even though this got corrected in the latest RC). When there is so much churn on a release so close to an RC being cut it really is not conducive to testing. Maybe the churn is not an issue, but imho I would like to see every commit being with a bug ID and being a direct decision of the RM.
-Sebastien
RE: 4.4 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Sebastien Goasguen [mailto:runseb@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
> code into the release.
>
[Animesh] That is not right, for 4.3 I had called out feature freeze date clearly and do not recall new feature added. IMHO the one challenge as community that we have which has been raised earlier also is QA contribution is primarily coming from one organization. Most other folks start taking the release for a spin only after RC2/RC3 or so and then we see additional issues and more re-spins. We really have to get all engaged in testing much earlier in the cycle. Sudha used to call out for help on QA activity but in prior releases I don't think she got much volunteers. We have huge technical debt and that is not going to go away with pointing fingers. If a specific scenario is benefiting someone as a user/developer of CloudStack and it turns out is not guarded with automation sufficiently and regresses in a release shouldn't the person using it also take some responsibility for safeguarding it with automation?
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
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, 2014 at 5:41 PM, Mike Tutkowski <mike.tutkowski@solidfire.com
> 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 <ru...@gmail.com>wrote:
>
>>
>> On Feb 28, 2014, at 9:09 AM, Hugo Trippaers <hu...@trippaers.nl> 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
>> features coming in at the last minute. Actually i'm under the impression
>> that when we move the deadline people will actually try to get more
>> features in instead of working on stabilizing existing features.
>> >
>> > "We can't deliver features on the roadmap." There is validity to this
>> point, but on the other hand we already know the entire release schedule
>> way ahead, this feature freeze date should not come as a surprise. But as i
>> mentioned in an earlier mail, lets have this discussion. Post which
>> features might not make it into the release so we can have a discussion if
>> we should slip the release date to get this feature in. I think we all now
>> that there are commercial parties working with this software to build
>> releases and have customers demanding features, but if we don't discuss
>> that on list it's hard for us to take it into account.
>> >
>> > "Feature freeze wasn't called" True, i wasn't even aware that this was
>> a requirement. We should add this to the procedure here
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so
>> release managers know this is expected of them. It should not impact the
>> dates as the dates are already fixed by the release schedule (every 4
>> months)
>> >
>> >
>> > I'm still -1 on extending the feature freeze. I would rather extend the
>> test/stability phase to we have some more time to fix issues before we get
>> into the RC spinning.
>> >
>> >
>> > 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?
>> >
>> > ASF JIRA
>> > Project: CloudStack
>> > Type: New Feature
>> > Fix Version: 4.4.0
>> > Resolution: Unresolved
>> > Sorted by: Updated descending
>> > 1-15 of 15 as at: 28/Feb/14 15:07
>> > T Key Summary Assignee Reporter P Status
>> Resolution Created Updated Due
>> > <newfeature.png> CLOUDSTACK-6181
>> > Root resize
>> > Unassigned Nux <major.png> <open.png> Open Unresolved
>> 27/Feb/14 27/Feb/14
>> > <newfeature.png> CLOUDSTACK-6161
>> > distributed routing and network ACL with OVS plug-in
>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>> Unresolved 24/Feb/14 24/Feb/14
>> > <newfeature.png> CLOUDSTACK-6092
>> > Storage OverProvisioning as a Per Primary Basis
>> > Saksham Srivastava Saksham Srivastava <major.png>
>> <open.png> Open Unresolved 13/Feb/14 20/Feb/14
>> > <newfeature.png> CLOUDSTACK-6144
>> > HA for guest VMs running Hyper-V
>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>> Unresolved 20/Feb/14 20/Feb/14
>> > <newfeature.png> CLOUDSTACK-6143
>> > Storage Live-Migration support for Hyper-V
>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>> Unresolved 20/Feb/14 20/Feb/14
>> > <newfeature.png> CLOUDSTACK-6142
>> > Zone Wide Primary Store in Hyper-V
>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>> Unresolved 20/Feb/14 20/Feb/14
>> > <newfeature.png> CLOUDSTACK-6104
>> > PVLAN support for CloudStack deployment over Nexus 1000v in VMware
>> environment
>> > Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png>
>> <open.png> Open Unresolved 14/Feb/14 15/Feb/14
>> > <newfeature.png> CLOUDSTACK-6109
>> > Support of iSCSI as primary store in Hyper-V
>> > Rajesh Battala Rajesh Battala <major.png> <open.png> Open
>> Unresolved 14/Feb/14 14/Feb/14
>> > <newfeature.png> CLOUDSTACK-6106
>> > Support of VPC in HyperV
>> > Rajesh Battala Rajesh Battala <major.png> <open.png> Open
>> Unresolved 14/Feb/14 14/Feb/14
>> > <newfeature.png> CLOUDSTACK-6090
>> > Virtual Router Service Failure Alerting
>> > Harikrishna Patnala Harikrishna Patnala <major.png>
>> <open.png> Open Unresolved 13/Feb/14 13/Feb/14
>> > <newfeature.png> CLOUDSTACK-6052
>> > List VM enhancement to support querying with multiple VM IDs
>> > Koushik Das Koushik Das <major.png> <open.png> Open
>> Unresolved 07/Feb/14 07/Feb/14
>> > <newfeature.png> CLOUDSTACK-5569
>> > enhance OVS plug-in to support region level VPC and guest networks that
>> span zones
>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>> Unresolved 19/Dec/13 19/Dec/13
>> > <newfeature.png> CLOUDSTACK-5568
>> > introduce notion of guest network that spans multiple zones
>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>> Unresolved 19/Dec/13 19/Dec/13
>> > <newfeature.png> CLOUDSTACK-5567
>> > enable VPC at region level
>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>> Unresolved 19/Dec/13 19/Dec/13
>> > <newfeature.png> CLOUDSTACK-5398
>> > Cloudstack network-element plugin to orchestrate Juniper's switches
>> > Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open
>> Unresolved 06/Dec/13 06/Dec/13
>> >
>> >
>> >
>>
>> Hugo as RM for 4.4 I would like support you in being strict on this.
>>
>> First if a feature is not listed in JIRA right now, then it does not
>> exist and is not planned for 4.4
>> These features should be in topic branches and merges should be called,
>> if one of those gets merged without a MERGE request then we should revert.
>> When a MERGE is called the person calling the merge needs to explain the
>> testing done.
>>
>> Postponing always encourages more postponing, we need to get off the
>> habit of rushing code in and then fixing that code in the multiple RC votes.
>>
>> My take is that we are slipping on RC and re-voting because we are
>> forcing code into the release.
>>
>> I did not check if the 4.4 branch exists already but I would be in favor
>> of locking that branch now with you being the only one to commit to it.
>>
>> -sebastien
>>
>>
>> > Cheers,
>> >
>> > Hugo
>> >
>> > On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org> wrote:
>> >
>> >> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>> >>>
>> >>
>> >> But you do agree that the re-spins uncovered bugs/issues that needed
>> >> to be fixed? Is it perhaps a mismatch in when the artifacts start
>> >> getting tested by the users+devs as opposed to when company-x might be
>> >> satisfied with their testing? More than 90% of the re-spins are
>> >> bugs/issues uncovered by users who needed RC candidates and weren't
>> >> testing artifacts on a daily basis (I could be wrong here). I don't
>> >> think someone with a large test engineering team would wait for the
>> >> RCs to get rolling. May be if we addressed that mismatch in timing we
>> >> could have smaller RC phases. Something like a soft-freeze and a
>> >> hard-freeze.
>> >>
>> >> post soft-freeze : users+devs do a daily test (mostly manually for
>> >> features they care about)
>> >> post hard-freeze : everyone only looks at a daily automated test
>> >> report and if all looks good, we release?
>> >>
>> >> --
>> >> Prasanna.,
>> >>
>> >> ------------------------
>> >> Powered by BigRock.com
>> >>
>> >
>>
>>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Marcus <sh...@gmail.com>.
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 <ru...@gmail.com> wrote:
>
> On Feb 28, 2014, at 9:09 AM, Hugo Trippaers <hu...@trippaers.nl> 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 features coming in at the last minute. Actually i'm under the impression that when we move the deadline people will actually try to get more features in instead of working on stabilizing existing features.
>>
>> "We can't deliver features on the roadmap." There is validity to this point, but on the other hand we already know the entire release schedule way ahead, this feature freeze date should not come as a surprise. But as i mentioned in an earlier mail, lets have this discussion. Post which features might not make it into the release so we can have a discussion if we should slip the release date to get this feature in. I think we all now that there are commercial parties working with this software to build releases and have customers demanding features, but if we don't discuss that on list it's hard for us to take it into account.
>>
>> "Feature freeze wasn't called" True, i wasn't even aware that this was a requirement. We should add this to the procedure here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so release managers know this is expected of them. It should not impact the dates as the dates are already fixed by the release schedule (every 4 months)
>>
>>
>> I'm still -1 on extending the feature freeze. I would rather extend the test/stability phase to we have some more time to fix issues before we get into the RC spinning.
>>
>>
>> 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?
>>
>> ASF JIRA
>> Project: CloudStack
>> Type: New Feature
>> Fix Version: 4.4.0
>> Resolution: Unresolved
>> Sorted by: Updated descending
>> 1-15 of 15 as at: 28/Feb/14 15:07
>> T Key Summary Assignee Reporter P Status Resolution Created Updated Due
>> <newfeature.png> CLOUDSTACK-6181
>> Root resize
>> Unassigned Nux <major.png> <open.png> Open Unresolved 27/Feb/14 27/Feb/14
>> <newfeature.png> CLOUDSTACK-6161
>> distributed routing and network ACL with OVS plug-in
>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 24/Feb/14 24/Feb/14
>> <newfeature.png> CLOUDSTACK-6092
>> Storage OverProvisioning as a Per Primary Basis
>> Saksham Srivastava Saksham Srivastava <major.png> <open.png> Open Unresolved 13/Feb/14 20/Feb/14
>> <newfeature.png> CLOUDSTACK-6144
>> HA for guest VMs running Hyper-V
>> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14 20/Feb/14
>> <newfeature.png> CLOUDSTACK-6143
>> Storage Live-Migration support for Hyper-V
>> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14 20/Feb/14
>> <newfeature.png> CLOUDSTACK-6142
>> Zone Wide Primary Store in Hyper-V
>> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14 20/Feb/14
>> <newfeature.png> CLOUDSTACK-6104
>> PVLAN support for CloudStack deployment over Nexus 1000v in VMware environment
>> Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png> <open.png> Open Unresolved 14/Feb/14 15/Feb/14
>> <newfeature.png> CLOUDSTACK-6109
>> Support of iSCSI as primary store in Hyper-V
>> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved 14/Feb/14 14/Feb/14
>> <newfeature.png> CLOUDSTACK-6106
>> Support of VPC in HyperV
>> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved 14/Feb/14 14/Feb/14
>> <newfeature.png> CLOUDSTACK-6090
>> Virtual Router Service Failure Alerting
>> Harikrishna Patnala Harikrishna Patnala <major.png> <open.png> Open Unresolved 13/Feb/14 13/Feb/14
>> <newfeature.png> CLOUDSTACK-6052
>> List VM enhancement to support querying with multiple VM IDs
>> Koushik Das Koushik Das <major.png> <open.png> Open Unresolved 07/Feb/14 07/Feb/14
>> <newfeature.png> CLOUDSTACK-5569
>> enhance OVS plug-in to support region level VPC and guest networks that span zones
>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13 19/Dec/13
>> <newfeature.png> CLOUDSTACK-5568
>> introduce notion of guest network that spans multiple zones
>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13 19/Dec/13
>> <newfeature.png> CLOUDSTACK-5567
>> enable VPC at region level
>> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13 19/Dec/13
>> <newfeature.png> CLOUDSTACK-5398
>> Cloudstack network-element plugin to orchestrate Juniper's switches
>> Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open Unresolved 06/Dec/13 06/Dec/13
>>
>>
>>
>
> Hugo as RM for 4.4 I would like support you in being strict on this.
>
> First if a feature is not listed in JIRA right now, then it does not exist and is not planned for 4.4
> These features should be in topic branches and merges should be called, if one of those gets merged without a MERGE request then we should revert. When a MERGE is called the person calling the merge needs to explain the testing done.
>
> Postponing always encourages more postponing, we need to get off the habit of rushing code in and then fixing that code in the multiple RC votes.
>
> My take is that we are slipping on RC and re-voting because we are forcing code into the release.
>
> I did not check if the 4.4 branch exists already but I would be in favor of locking that branch now with you being the only one to commit to it.
>
> -sebastien
>
>
>> Cheers,
>>
>> Hugo
>>
>> On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org> wrote:
>>
>>> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>>>>
>>>
>>> But you do agree that the re-spins uncovered bugs/issues that needed
>>> to be fixed? Is it perhaps a mismatch in when the artifacts start
>>> getting tested by the users+devs as opposed to when company-x might be
>>> satisfied with their testing? More than 90% of the re-spins are
>>> bugs/issues uncovered by users who needed RC candidates and weren't
>>> testing artifacts on a daily basis (I could be wrong here). I don't
>>> think someone with a large test engineering team would wait for the
>>> RCs to get rolling. May be if we addressed that mismatch in timing we
>>> could have smaller RC phases. Something like a soft-freeze and a
>>> hard-freeze.
>>>
>>> post soft-freeze : users+devs do a daily test (mostly manually for
>>> features they care about)
>>> post hard-freeze : everyone only looks at a daily automated test
>>> report and if all looks good, we release?
>>>
>>> --
>>> Prasanna.,
>>>
>>> ------------------------
>>> Powered by BigRock.com
>>>
>>
>
Re: 4.4 Feature Freeze
Posted by Abhinandan Prateek <Ab...@citrix.com>.
Daan,
Since you are the 4.4 RM we will respect your decision.
-abhi
On 03/03/14 2:11 pm, "Daan Hoogland" <da...@gmail.com> 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 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 at 9:33 AM, Abhinandan Prateek
><Ab...@citrix.com> wrote:
>> 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" <mi...@solidfire.com>
>>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
>>><ru...@gmail.com>wrote:
>>>
>>>>
>>>> On Feb 28, 2014, at 9:09 AM, Hugo Trippaers <hu...@trippaers.nl> 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
>>>> features coming in at the last minute. Actually i'm under the
>>>>impression
>>>> that when we move the deadline people will actually try to get more
>>>> features in instead of working on stabilizing existing features.
>>>> >
>>>> > "We can't deliver features on the roadmap." There is validity to
>>>>this
>>>> point, but on the other hand we already know the entire release
>>>>schedule
>>>> way ahead, this feature freeze date should not come as a surprise. But
>>>>as i
>>>> mentioned in an earlier mail, lets have this discussion. Post which
>>>> features might not make it into the release so we can have a
>>>>discussion
>>>>if
>>>> we should slip the release date to get this feature in. I think we all
>>>>now
>>>> that there are commercial parties working with this software to build
>>>> releases and have customers demanding features, but if we don't
>>>>discuss
>>>> that on list it's hard for us to take it into account.
>>>> >
>>>> > "Feature freeze wasn't called" True, i wasn't even aware that this
>>>>was a
>>>> requirement. We should add this to the procedure here
>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so
>>>> release managers know this is expected of them. It should not impact
>>>>the
>>>> dates as the dates are already fixed by the release schedule (every 4
>>>> months)
>>>> >
>>>> >
>>>> > I'm still -1 on extending the feature freeze. I would rather extend
>>>>the
>>>> test/stability phase to we have some more time to fix issues before we
>>>>get
>>>> into the RC spinning.
>>>> >
>>>> >
>>>> > 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?
>>>> >
>>>> > ASF JIRA
>>>> > Project: CloudStack
>>>> > Type: New Feature
>>>> > Fix Version: 4.4.0
>>>> > Resolution: Unresolved
>>>> > Sorted by: Updated descending
>>>> > 1-15 of 15 as at: 28/Feb/14 15:07
>>>> > T Key Summary Assignee Reporter P Status
>>>> Resolution Created Updated Due
>>>> > <newfeature.png> CLOUDSTACK-6181
>>>> > Root resize
>>>> > Unassigned Nux <major.png> <open.png> Open Unresolved
>>>> 27/Feb/14 27/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6161
>>>> > distributed routing and network ACL with OVS plug-in
>>>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>>>Unresolved
>>>> 24/Feb/14 24/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6092
>>>> > Storage OverProvisioning as a Per Primary Basis
>>>> > Saksham Srivastava Saksham Srivastava <major.png>
>>>><open.png>
>>>> Open Unresolved 13/Feb/14 20/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6144
>>>> > HA for guest VMs running Hyper-V
>>>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>>>>Unresolved
>>>> 20/Feb/14 20/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6143
>>>> > Storage Live-Migration support for Hyper-V
>>>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>>>>Unresolved
>>>> 20/Feb/14 20/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6142
>>>> > Zone Wide Primary Store in Hyper-V
>>>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>>>>Unresolved
>>>> 20/Feb/14 20/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6104
>>>> > PVLAN support for CloudStack deployment over Nexus 1000v in VMware
>>>> environment
>>>> > Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png>
>>>><open.png>
>>>> Open Unresolved 14/Feb/14 15/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6109
>>>> > Support of iSCSI as primary store in Hyper-V
>>>> > Rajesh Battala Rajesh Battala <major.png> <open.png>
>>>>Open
>>>> Unresolved 14/Feb/14 14/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6106
>>>> > Support of VPC in HyperV
>>>> > Rajesh Battala Rajesh Battala <major.png> <open.png>
>>>>Open
>>>> Unresolved 14/Feb/14 14/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6090
>>>> > Virtual Router Service Failure Alerting
>>>> > Harikrishna Patnala Harikrishna Patnala <major.png>
>>>><open.png>
>>>> Open Unresolved 13/Feb/14 13/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-6052
>>>> > List VM enhancement to support querying with multiple VM IDs
>>>> > Koushik Das Koushik Das <major.png> <open.png> Open
>>>>Unresolved
>>>> 07/Feb/14 07/Feb/14
>>>> > <newfeature.png> CLOUDSTACK-5569
>>>> > enhance OVS plug-in to support region level VPC and guest networks
>>>>that
>>>> span zones
>>>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>>>Unresolved
>>>> 19/Dec/13 19/Dec/13
>>>> > <newfeature.png> CLOUDSTACK-5568
>>>> > introduce notion of guest network that spans multiple zones
>>>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>>>Unresolved
>>>> 19/Dec/13 19/Dec/13
>>>> > <newfeature.png> CLOUDSTACK-5567
>>>> > enable VPC at region level
>>>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>>>Unresolved
>>>> 19/Dec/13 19/Dec/13
>>>> > <newfeature.png> CLOUDSTACK-5398
>>>> > Cloudstack network-element plugin to orchestrate Juniper's switches
>>>> > Unassigned Pradeep H Krishnamurthy <major.png> <open.png>
>>>>Open
>>>> Unresolved 06/Dec/13 06/Dec/13
>>>> >
>>>> >
>>>> >
>>>>
>>>> Hugo as RM for 4.4 I would like support you in being strict on this.
>>>>
>>>> First if a feature is not listed in JIRA right now, then it does not
>>>>exist
>>>> and is not planned for 4.4
>>>> These features should be in topic branches and merges should be
>>>>called,
>>>>if
>>>> one of those gets merged without a MERGE request then we should
>>>>revert.
>>>> When a MERGE is called the person calling the merge needs to explain
>>>>the
>>>> testing done.
>>>>
>>>> Postponing always encourages more postponing, we need to get off the
>>>>habit
>>>> of rushing code in and then fixing that code in the multiple RC votes.
>>>>
>>>> My take is that we are slipping on RC and re-voting because we are
>>>>forcing
>>>> code into the release.
>>>>
>>>> I did not check if the 4.4 branch exists already but I would be in
>>>>favor
>>>> of locking that branch now with you being the only one to commit to
>>>>it.
>>>>
>>>> -sebastien
>>>>
>>>>
>>>> > Cheers,
>>>> >
>>>> > Hugo
>>>> >
>>>> > On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org>
>>>>wrote:
>>>> >
>>>> >> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>>>> >>>
>>>> >>
>>>> >> But you do agree that the re-spins uncovered bugs/issues that
>>>>needed
>>>> >> to be fixed? Is it perhaps a mismatch in when the artifacts start
>>>> >> getting tested by the users+devs as opposed to when company-x might
>>>>be
>>>> >> satisfied with their testing? More than 90% of the re-spins are
>>>> >> bugs/issues uncovered by users who needed RC candidates and weren't
>>>> >> testing artifacts on a daily basis (I could be wrong here). I don't
>>>> >> think someone with a large test engineering team would wait for the
>>>> >> RCs to get rolling. May be if we addressed that mismatch in timing
>>>>we
>>>> >> could have smaller RC phases. Something like a soft-freeze and a
>>>> >> hard-freeze.
>>>> >>
>>>> >> post soft-freeze : users+devs do a daily test (mostly manually for
>>>> >> features they care about)
>>>> >> post hard-freeze : everyone only looks at a daily automated test
>>>> >> report and if all looks good, we release?
>>>> >>
>>>> >> --
>>>> >> Prasanna.,
>>>> >>
>>>> >> ------------------------
>>>> >> Powered by BigRock.com
>>>> >>
>>>> >
>>>>
>>>>
>>>
>>>
>>>--
>>>*Mike Tutkowski*
>>>*Senior CloudStack Developer, SolidFire Inc.*
>>>e: mike.tutkowski@solidfire.com
>>>o: 303.746.7302
>>>Advancing the way the world uses the
>>>cloud<http://solidfire.com/solution/overview/?video=play>
>>>*(tm)*
>>
>
>
>
>--
>Daan
Re: 4.4 Feature Freeze
Posted by Daan Hoogland <da...@gmail.com>.
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 at 9:33 AM, Abhinandan Prateek
<Ab...@citrix.com> wrote:
> 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" <mi...@solidfire.com> 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
>><ru...@gmail.com>wrote:
>>
>>>
>>> On Feb 28, 2014, at 9:09 AM, Hugo Trippaers <hu...@trippaers.nl> 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
>>> features coming in at the last minute. Actually i'm under the impression
>>> that when we move the deadline people will actually try to get more
>>> features in instead of working on stabilizing existing features.
>>> >
>>> > "We can't deliver features on the roadmap." There is validity to this
>>> point, but on the other hand we already know the entire release schedule
>>> way ahead, this feature freeze date should not come as a surprise. But
>>>as i
>>> mentioned in an earlier mail, lets have this discussion. Post which
>>> features might not make it into the release so we can have a discussion
>>>if
>>> we should slip the release date to get this feature in. I think we all
>>>now
>>> that there are commercial parties working with this software to build
>>> releases and have customers demanding features, but if we don't discuss
>>> that on list it's hard for us to take it into account.
>>> >
>>> > "Feature freeze wasn't called" True, i wasn't even aware that this
>>>was a
>>> requirement. We should add this to the procedure here
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so
>>> release managers know this is expected of them. It should not impact the
>>> dates as the dates are already fixed by the release schedule (every 4
>>> months)
>>> >
>>> >
>>> > I'm still -1 on extending the feature freeze. I would rather extend
>>>the
>>> test/stability phase to we have some more time to fix issues before we
>>>get
>>> into the RC spinning.
>>> >
>>> >
>>> > 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?
>>> >
>>> > ASF JIRA
>>> > Project: CloudStack
>>> > Type: New Feature
>>> > Fix Version: 4.4.0
>>> > Resolution: Unresolved
>>> > Sorted by: Updated descending
>>> > 1-15 of 15 as at: 28/Feb/14 15:07
>>> > T Key Summary Assignee Reporter P Status
>>> Resolution Created Updated Due
>>> > <newfeature.png> CLOUDSTACK-6181
>>> > Root resize
>>> > Unassigned Nux <major.png> <open.png> Open Unresolved
>>> 27/Feb/14 27/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6161
>>> > distributed routing and network ACL with OVS plug-in
>>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>>Unresolved
>>> 24/Feb/14 24/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6092
>>> > Storage OverProvisioning as a Per Primary Basis
>>> > Saksham Srivastava Saksham Srivastava <major.png>
>>><open.png>
>>> Open Unresolved 13/Feb/14 20/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6144
>>> > HA for guest VMs running Hyper-V
>>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>>>Unresolved
>>> 20/Feb/14 20/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6143
>>> > Storage Live-Migration support for Hyper-V
>>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>>>Unresolved
>>> 20/Feb/14 20/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6142
>>> > Zone Wide Primary Store in Hyper-V
>>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>>>Unresolved
>>> 20/Feb/14 20/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6104
>>> > PVLAN support for CloudStack deployment over Nexus 1000v in VMware
>>> environment
>>> > Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png>
>>><open.png>
>>> Open Unresolved 14/Feb/14 15/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6109
>>> > Support of iSCSI as primary store in Hyper-V
>>> > Rajesh Battala Rajesh Battala <major.png> <open.png> Open
>>> Unresolved 14/Feb/14 14/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6106
>>> > Support of VPC in HyperV
>>> > Rajesh Battala Rajesh Battala <major.png> <open.png> Open
>>> Unresolved 14/Feb/14 14/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6090
>>> > Virtual Router Service Failure Alerting
>>> > Harikrishna Patnala Harikrishna Patnala <major.png>
>>><open.png>
>>> Open Unresolved 13/Feb/14 13/Feb/14
>>> > <newfeature.png> CLOUDSTACK-6052
>>> > List VM enhancement to support querying with multiple VM IDs
>>> > Koushik Das Koushik Das <major.png> <open.png> Open
>>>Unresolved
>>> 07/Feb/14 07/Feb/14
>>> > <newfeature.png> CLOUDSTACK-5569
>>> > enhance OVS plug-in to support region level VPC and guest networks
>>>that
>>> span zones
>>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>>Unresolved
>>> 19/Dec/13 19/Dec/13
>>> > <newfeature.png> CLOUDSTACK-5568
>>> > introduce notion of guest network that spans multiple zones
>>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>>Unresolved
>>> 19/Dec/13 19/Dec/13
>>> > <newfeature.png> CLOUDSTACK-5567
>>> > enable VPC at region level
>>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>>Unresolved
>>> 19/Dec/13 19/Dec/13
>>> > <newfeature.png> CLOUDSTACK-5398
>>> > Cloudstack network-element plugin to orchestrate Juniper's switches
>>> > Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open
>>> Unresolved 06/Dec/13 06/Dec/13
>>> >
>>> >
>>> >
>>>
>>> Hugo as RM for 4.4 I would like support you in being strict on this.
>>>
>>> First if a feature is not listed in JIRA right now, then it does not
>>>exist
>>> and is not planned for 4.4
>>> These features should be in topic branches and merges should be called,
>>>if
>>> one of those gets merged without a MERGE request then we should revert.
>>> When a MERGE is called the person calling the merge needs to explain the
>>> testing done.
>>>
>>> Postponing always encourages more postponing, we need to get off the
>>>habit
>>> of rushing code in and then fixing that code in the multiple RC votes.
>>>
>>> My take is that we are slipping on RC and re-voting because we are
>>>forcing
>>> code into the release.
>>>
>>> I did not check if the 4.4 branch exists already but I would be in favor
>>> of locking that branch now with you being the only one to commit to it.
>>>
>>> -sebastien
>>>
>>>
>>> > Cheers,
>>> >
>>> > Hugo
>>> >
>>> > On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org> wrote:
>>> >
>>> >> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>>> >>>
>>> >>
>>> >> But you do agree that the re-spins uncovered bugs/issues that needed
>>> >> to be fixed? Is it perhaps a mismatch in when the artifacts start
>>> >> getting tested by the users+devs as opposed to when company-x might
>>>be
>>> >> satisfied with their testing? More than 90% of the re-spins are
>>> >> bugs/issues uncovered by users who needed RC candidates and weren't
>>> >> testing artifacts on a daily basis (I could be wrong here). I don't
>>> >> think someone with a large test engineering team would wait for the
>>> >> RCs to get rolling. May be if we addressed that mismatch in timing we
>>> >> could have smaller RC phases. Something like a soft-freeze and a
>>> >> hard-freeze.
>>> >>
>>> >> post soft-freeze : users+devs do a daily test (mostly manually for
>>> >> features they care about)
>>> >> post hard-freeze : everyone only looks at a daily automated test
>>> >> report and if all looks good, we release?
>>> >>
>>> >> --
>>> >> Prasanna.,
>>> >>
>>> >> ------------------------
>>> >> Powered by BigRock.com
>>> >>
>>> >
>>>
>>>
>>
>>
>>--
>>*Mike Tutkowski*
>>*Senior CloudStack Developer, SolidFire Inc.*
>>e: mike.tutkowski@solidfire.com
>>o: 303.746.7302
>>Advancing the way the world uses the
>>cloud<http://solidfire.com/solution/overview/?video=play>
>>*(tm)*
>
--
Daan
Re: 4.4 Feature Freeze
Posted by Abhinandan Prateek <Ab...@citrix.com>.
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" <mi...@solidfire.com> 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
><ru...@gmail.com>wrote:
>
>>
>> On Feb 28, 2014, at 9:09 AM, Hugo Trippaers <hu...@trippaers.nl> 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
>> features coming in at the last minute. Actually i'm under the impression
>> that when we move the deadline people will actually try to get more
>> features in instead of working on stabilizing existing features.
>> >
>> > "We can't deliver features on the roadmap." There is validity to this
>> point, but on the other hand we already know the entire release schedule
>> way ahead, this feature freeze date should not come as a surprise. But
>>as i
>> mentioned in an earlier mail, lets have this discussion. Post which
>> features might not make it into the release so we can have a discussion
>>if
>> we should slip the release date to get this feature in. I think we all
>>now
>> that there are commercial parties working with this software to build
>> releases and have customers demanding features, but if we don't discuss
>> that on list it's hard for us to take it into account.
>> >
>> > "Feature freeze wasn't called" True, i wasn't even aware that this
>>was a
>> requirement. We should add this to the procedure here
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so
>> release managers know this is expected of them. It should not impact the
>> dates as the dates are already fixed by the release schedule (every 4
>> months)
>> >
>> >
>> > I'm still -1 on extending the feature freeze. I would rather extend
>>the
>> test/stability phase to we have some more time to fix issues before we
>>get
>> into the RC spinning.
>> >
>> >
>> > 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?
>> >
>> > ASF JIRA
>> > Project: CloudStack
>> > Type: New Feature
>> > Fix Version: 4.4.0
>> > Resolution: Unresolved
>> > Sorted by: Updated descending
>> > 1-15 of 15 as at: 28/Feb/14 15:07
>> > T Key Summary Assignee Reporter P Status
>> Resolution Created Updated Due
>> > <newfeature.png> CLOUDSTACK-6181
>> > Root resize
>> > Unassigned Nux <major.png> <open.png> Open Unresolved
>> 27/Feb/14 27/Feb/14
>> > <newfeature.png> CLOUDSTACK-6161
>> > distributed routing and network ACL with OVS plug-in
>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>Unresolved
>> 24/Feb/14 24/Feb/14
>> > <newfeature.png> CLOUDSTACK-6092
>> > Storage OverProvisioning as a Per Primary Basis
>> > Saksham Srivastava Saksham Srivastava <major.png>
>><open.png>
>> Open Unresolved 13/Feb/14 20/Feb/14
>> > <newfeature.png> CLOUDSTACK-6144
>> > HA for guest VMs running Hyper-V
>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>>Unresolved
>> 20/Feb/14 20/Feb/14
>> > <newfeature.png> CLOUDSTACK-6143
>> > Storage Live-Migration support for Hyper-V
>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>>Unresolved
>> 20/Feb/14 20/Feb/14
>> > <newfeature.png> CLOUDSTACK-6142
>> > Zone Wide Primary Store in Hyper-V
>> > Unassigned Rajesh Battala <major.png> <open.png> Open
>>Unresolved
>> 20/Feb/14 20/Feb/14
>> > <newfeature.png> CLOUDSTACK-6104
>> > PVLAN support for CloudStack deployment over Nexus 1000v in VMware
>> environment
>> > Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png>
>><open.png>
>> Open Unresolved 14/Feb/14 15/Feb/14
>> > <newfeature.png> CLOUDSTACK-6109
>> > Support of iSCSI as primary store in Hyper-V
>> > Rajesh Battala Rajesh Battala <major.png> <open.png> Open
>> Unresolved 14/Feb/14 14/Feb/14
>> > <newfeature.png> CLOUDSTACK-6106
>> > Support of VPC in HyperV
>> > Rajesh Battala Rajesh Battala <major.png> <open.png> Open
>> Unresolved 14/Feb/14 14/Feb/14
>> > <newfeature.png> CLOUDSTACK-6090
>> > Virtual Router Service Failure Alerting
>> > Harikrishna Patnala Harikrishna Patnala <major.png>
>><open.png>
>> Open Unresolved 13/Feb/14 13/Feb/14
>> > <newfeature.png> CLOUDSTACK-6052
>> > List VM enhancement to support querying with multiple VM IDs
>> > Koushik Das Koushik Das <major.png> <open.png> Open
>>Unresolved
>> 07/Feb/14 07/Feb/14
>> > <newfeature.png> CLOUDSTACK-5569
>> > enhance OVS plug-in to support region level VPC and guest networks
>>that
>> span zones
>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>Unresolved
>> 19/Dec/13 19/Dec/13
>> > <newfeature.png> CLOUDSTACK-5568
>> > introduce notion of guest network that spans multiple zones
>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>Unresolved
>> 19/Dec/13 19/Dec/13
>> > <newfeature.png> CLOUDSTACK-5567
>> > enable VPC at region level
>> > Murali Reddy Murali Reddy <major.png> <open.png> Open
>>Unresolved
>> 19/Dec/13 19/Dec/13
>> > <newfeature.png> CLOUDSTACK-5398
>> > Cloudstack network-element plugin to orchestrate Juniper's switches
>> > Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open
>> Unresolved 06/Dec/13 06/Dec/13
>> >
>> >
>> >
>>
>> Hugo as RM for 4.4 I would like support you in being strict on this.
>>
>> First if a feature is not listed in JIRA right now, then it does not
>>exist
>> and is not planned for 4.4
>> These features should be in topic branches and merges should be called,
>>if
>> one of those gets merged without a MERGE request then we should revert.
>> When a MERGE is called the person calling the merge needs to explain the
>> testing done.
>>
>> Postponing always encourages more postponing, we need to get off the
>>habit
>> of rushing code in and then fixing that code in the multiple RC votes.
>>
>> My take is that we are slipping on RC and re-voting because we are
>>forcing
>> code into the release.
>>
>> I did not check if the 4.4 branch exists already but I would be in favor
>> of locking that branch now with you being the only one to commit to it.
>>
>> -sebastien
>>
>>
>> > Cheers,
>> >
>> > Hugo
>> >
>> > On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org> wrote:
>> >
>> >> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>> >>>
>> >>
>> >> But you do agree that the re-spins uncovered bugs/issues that needed
>> >> to be fixed? Is it perhaps a mismatch in when the artifacts start
>> >> getting tested by the users+devs as opposed to when company-x might
>>be
>> >> satisfied with their testing? More than 90% of the re-spins are
>> >> bugs/issues uncovered by users who needed RC candidates and weren't
>> >> testing artifacts on a daily basis (I could be wrong here). I don't
>> >> think someone with a large test engineering team would wait for the
>> >> RCs to get rolling. May be if we addressed that mismatch in timing we
>> >> could have smaller RC phases. Something like a soft-freeze and a
>> >> hard-freeze.
>> >>
>> >> post soft-freeze : users+devs do a daily test (mostly manually for
>> >> features they care about)
>> >> post hard-freeze : everyone only looks at a daily automated test
>> >> report and if all looks good, we release?
>> >>
>> >> --
>> >> Prasanna.,
>> >>
>> >> ------------------------
>> >> Powered by BigRock.com
>> >>
>> >
>>
>>
>
>
>--
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkowski@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud<http://solidfire.com/solution/overview/?video=play>
>*(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
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 <ru...@gmail.com>wrote:
>
> On Feb 28, 2014, at 9:09 AM, Hugo Trippaers <hu...@trippaers.nl> 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
> features coming in at the last minute. Actually i'm under the impression
> that when we move the deadline people will actually try to get more
> features in instead of working on stabilizing existing features.
> >
> > "We can't deliver features on the roadmap." There is validity to this
> point, but on the other hand we already know the entire release schedule
> way ahead, this feature freeze date should not come as a surprise. But as i
> mentioned in an earlier mail, lets have this discussion. Post which
> features might not make it into the release so we can have a discussion if
> we should slip the release date to get this feature in. I think we all now
> that there are commercial parties working with this software to build
> releases and have customers demanding features, but if we don't discuss
> that on list it's hard for us to take it into account.
> >
> > "Feature freeze wasn't called" True, i wasn't even aware that this was a
> requirement. We should add this to the procedure here
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so
> release managers know this is expected of them. It should not impact the
> dates as the dates are already fixed by the release schedule (every 4
> months)
> >
> >
> > I'm still -1 on extending the feature freeze. I would rather extend the
> test/stability phase to we have some more time to fix issues before we get
> into the RC spinning.
> >
> >
> > 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?
> >
> > ASF JIRA
> > Project: CloudStack
> > Type: New Feature
> > Fix Version: 4.4.0
> > Resolution: Unresolved
> > Sorted by: Updated descending
> > 1-15 of 15 as at: 28/Feb/14 15:07
> > T Key Summary Assignee Reporter P Status
> Resolution Created Updated Due
> > <newfeature.png> CLOUDSTACK-6181
> > Root resize
> > Unassigned Nux <major.png> <open.png> Open Unresolved
> 27/Feb/14 27/Feb/14
> > <newfeature.png> CLOUDSTACK-6161
> > distributed routing and network ACL with OVS plug-in
> > Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved
> 24/Feb/14 24/Feb/14
> > <newfeature.png> CLOUDSTACK-6092
> > Storage OverProvisioning as a Per Primary Basis
> > Saksham Srivastava Saksham Srivastava <major.png> <open.png>
> Open Unresolved 13/Feb/14 20/Feb/14
> > <newfeature.png> CLOUDSTACK-6144
> > HA for guest VMs running Hyper-V
> > Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved
> 20/Feb/14 20/Feb/14
> > <newfeature.png> CLOUDSTACK-6143
> > Storage Live-Migration support for Hyper-V
> > Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved
> 20/Feb/14 20/Feb/14
> > <newfeature.png> CLOUDSTACK-6142
> > Zone Wide Primary Store in Hyper-V
> > Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved
> 20/Feb/14 20/Feb/14
> > <newfeature.png> CLOUDSTACK-6104
> > PVLAN support for CloudStack deployment over Nexus 1000v in VMware
> environment
> > Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png> <open.png>
> Open Unresolved 14/Feb/14 15/Feb/14
> > <newfeature.png> CLOUDSTACK-6109
> > Support of iSCSI as primary store in Hyper-V
> > Rajesh Battala Rajesh Battala <major.png> <open.png> Open
> Unresolved 14/Feb/14 14/Feb/14
> > <newfeature.png> CLOUDSTACK-6106
> > Support of VPC in HyperV
> > Rajesh Battala Rajesh Battala <major.png> <open.png> Open
> Unresolved 14/Feb/14 14/Feb/14
> > <newfeature.png> CLOUDSTACK-6090
> > Virtual Router Service Failure Alerting
> > Harikrishna Patnala Harikrishna Patnala <major.png> <open.png>
> Open Unresolved 13/Feb/14 13/Feb/14
> > <newfeature.png> CLOUDSTACK-6052
> > List VM enhancement to support querying with multiple VM IDs
> > Koushik Das Koushik Das <major.png> <open.png> Open Unresolved
> 07/Feb/14 07/Feb/14
> > <newfeature.png> CLOUDSTACK-5569
> > enhance OVS plug-in to support region level VPC and guest networks that
> span zones
> > Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved
> 19/Dec/13 19/Dec/13
> > <newfeature.png> CLOUDSTACK-5568
> > introduce notion of guest network that spans multiple zones
> > Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved
> 19/Dec/13 19/Dec/13
> > <newfeature.png> CLOUDSTACK-5567
> > enable VPC at region level
> > Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved
> 19/Dec/13 19/Dec/13
> > <newfeature.png> CLOUDSTACK-5398
> > Cloudstack network-element plugin to orchestrate Juniper's switches
> > Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open
> Unresolved 06/Dec/13 06/Dec/13
> >
> >
> >
>
> Hugo as RM for 4.4 I would like support you in being strict on this.
>
> First if a feature is not listed in JIRA right now, then it does not exist
> and is not planned for 4.4
> These features should be in topic branches and merges should be called, if
> one of those gets merged without a MERGE request then we should revert.
> When a MERGE is called the person calling the merge needs to explain the
> testing done.
>
> Postponing always encourages more postponing, we need to get off the habit
> of rushing code in and then fixing that code in the multiple RC votes.
>
> My take is that we are slipping on RC and re-voting because we are forcing
> code into the release.
>
> I did not check if the 4.4 branch exists already but I would be in favor
> of locking that branch now with you being the only one to commit to it.
>
> -sebastien
>
>
> > Cheers,
> >
> > Hugo
> >
> > On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org> wrote:
> >
> >> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
> >>>
> >>
> >> But you do agree that the re-spins uncovered bugs/issues that needed
> >> to be fixed? Is it perhaps a mismatch in when the artifacts start
> >> getting tested by the users+devs as opposed to when company-x might be
> >> satisfied with their testing? More than 90% of the re-spins are
> >> bugs/issues uncovered by users who needed RC candidates and weren't
> >> testing artifacts on a daily basis (I could be wrong here). I don't
> >> think someone with a large test engineering team would wait for the
> >> RCs to get rolling. May be if we addressed that mismatch in timing we
> >> could have smaller RC phases. Something like a soft-freeze and a
> >> hard-freeze.
> >>
> >> post soft-freeze : users+devs do a daily test (mostly manually for
> >> features they care about)
> >> post hard-freeze : everyone only looks at a daily automated test
> >> report and if all looks good, we release?
> >>
> >> --
> >> Prasanna.,
> >>
> >> ------------------------
> >> Powered by BigRock.com
> >>
> >
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Feb 28, 2014, at 9:09 AM, Hugo Trippaers <hu...@trippaers.nl> 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 features coming in at the last minute. Actually i’m under the impression that when we move the deadline people will actually try to get more features in instead of working on stabilizing existing features.
>
> “We can’t deliver features on the roadmap.” There is validity to this point, but on the other hand we already know the entire release schedule way ahead, this feature freeze date should not come as a surprise. But as i mentioned in an earlier mail, lets have this discussion. Post which features might not make it into the release so we can have a discussion if we should slip the release date to get this feature in. I think we all now that there are commercial parties working with this software to build releases and have customers demanding features, but if we don’t discuss that on list it’s hard for us to take it into account.
>
> “Feature freeze wasn’t called” True, i wasn’t even aware that this was a requirement. We should add this to the procedure here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so release managers know this is expected of them. It should not impact the dates as the dates are already fixed by the release schedule (every 4 months)
>
>
> I’m still -1 on extending the feature freeze. I would rather extend the test/stability phase to we have some more time to fix issues before we get into the RC spinning.
>
>
> 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?
>
> ASF JIRA
> Project: CloudStack
> Type: New Feature
> Fix Version: 4.4.0
> Resolution: Unresolved
> Sorted by: Updated descending
> 1–15 of 15 as at: 28/Feb/14 15:07
> T Key Summary Assignee Reporter P Status Resolution Created Updated Due
> <newfeature.png> CLOUDSTACK-6181
> Root resize
> Unassigned Nux <major.png> <open.png> Open Unresolved 27/Feb/14 27/Feb/14
> <newfeature.png> CLOUDSTACK-6161
> distributed routing and network ACL with OVS plug-in
> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 24/Feb/14 24/Feb/14
> <newfeature.png> CLOUDSTACK-6092
> Storage OverProvisioning as a Per Primary Basis
> Saksham Srivastava Saksham Srivastava <major.png> <open.png> Open Unresolved 13/Feb/14 20/Feb/14
> <newfeature.png> CLOUDSTACK-6144
> HA for guest VMs running Hyper-V
> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14 20/Feb/14
> <newfeature.png> CLOUDSTACK-6143
> Storage Live-Migration support for Hyper-V
> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14 20/Feb/14
> <newfeature.png> CLOUDSTACK-6142
> Zone Wide Primary Store in Hyper-V
> Unassigned Rajesh Battala <major.png> <open.png> Open Unresolved 20/Feb/14 20/Feb/14
> <newfeature.png> CLOUDSTACK-6104
> PVLAN support for CloudStack deployment over Nexus 1000v in VMware environment
> Sateesh Chodapuneedi Sateesh Chodapuneedi <major.png> <open.png> Open Unresolved 14/Feb/14 15/Feb/14
> <newfeature.png> CLOUDSTACK-6109
> Support of iSCSI as primary store in Hyper-V
> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved 14/Feb/14 14/Feb/14
> <newfeature.png> CLOUDSTACK-6106
> Support of VPC in HyperV
> Rajesh Battala Rajesh Battala <major.png> <open.png> Open Unresolved 14/Feb/14 14/Feb/14
> <newfeature.png> CLOUDSTACK-6090
> Virtual Router Service Failure Alerting
> Harikrishna Patnala Harikrishna Patnala <major.png> <open.png> Open Unresolved 13/Feb/14 13/Feb/14
> <newfeature.png> CLOUDSTACK-6052
> List VM enhancement to support querying with multiple VM IDs
> Koushik Das Koushik Das <major.png> <open.png> Open Unresolved 07/Feb/14 07/Feb/14
> <newfeature.png> CLOUDSTACK-5569
> enhance OVS plug-in to support region level VPC and guest networks that span zones
> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13 19/Dec/13
> <newfeature.png> CLOUDSTACK-5568
> introduce notion of guest network that spans multiple zones
> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13 19/Dec/13
> <newfeature.png> CLOUDSTACK-5567
> enable VPC at region level
> Murali Reddy Murali Reddy <major.png> <open.png> Open Unresolved 19/Dec/13 19/Dec/13
> <newfeature.png> CLOUDSTACK-5398
> Cloudstack network-element plugin to orchestrate Juniper's switches
> Unassigned Pradeep H Krishnamurthy <major.png> <open.png> Open Unresolved 06/Dec/13 06/Dec/13
>
>
>
Hugo as RM for 4.4 I would like support you in being strict on this.
First if a feature is not listed in JIRA right now, then it does not exist and is not planned for 4.4
These features should be in topic branches and merges should be called, if one of those gets merged without a MERGE request then we should revert. When a MERGE is called the person calling the merge needs to explain the testing done.
Postponing always encourages more postponing, we need to get off the habit of rushing code in and then fixing that code in the multiple RC votes.
My take is that we are slipping on RC and re-voting because we are forcing code into the release.
I did not check if the 4.4 branch exists already but I would be in favor of locking that branch now with you being the only one to commit to it.
-sebastien
> Cheers,
>
> Hugo
>
> On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org> wrote:
>
>> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>>>
>>
>> But you do agree that the re-spins uncovered bugs/issues that needed
>> to be fixed? Is it perhaps a mismatch in when the artifacts start
>> getting tested by the users+devs as opposed to when company-x might be
>> satisfied with their testing? More than 90% of the re-spins are
>> bugs/issues uncovered by users who needed RC candidates and weren't
>> testing artifacts on a daily basis (I could be wrong here). I don't
>> think someone with a large test engineering team would wait for the
>> RCs to get rolling. May be if we addressed that mismatch in timing we
>> could have smaller RC phases. Something like a soft-freeze and a
>> hard-freeze.
>>
>> post soft-freeze : users+devs do a daily test (mostly manually for
>> features they care about)
>> post hard-freeze : everyone only looks at a daily automated test
>> report and if all looks good, we release?
>>
>> --
>> Prasanna.,
>>
>> ------------------------
>> Powered by BigRock.com
>>
>
Re: 4.4 Feature Freeze
Posted by Hugo Trippaers <hu...@trippaers.nl>.
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 impression that when we move the deadline people will actually try to get more features in instead of working on stabilizing existing features.
“We can’t deliver features on the roadmap.” There is validity to this point, but on the other hand we already know the entire release schedule way ahead, this feature freeze date should not come as a surprise. But as i mentioned in an earlier mail, lets have this discussion. Post which features might not make it into the release so we can have a discussion if we should slip the release date to get this feature in. I think we all now that there are commercial parties working with this software to build releases and have customers demanding features, but if we don’t discuss that on list it’s hard for us to take it into account.
“Feature freeze wasn’t called” True, i wasn’t even aware that this was a requirement. We should add this to the procedure here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases so release managers know this is expected of them. It should not impact the dates as the dates are already fixed by the release schedule (every 4 months)
I’m still -1 on extending the feature freeze. I would rather extend the test/stability phase to we have some more time to fix issues before we get into the RC spinning.
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?
ASF JIRA
Project: CloudStack
Type: New Feature
Fix Version: 4.4.0
Resolution: Unresolved
Sorted by: Updated descending
1–15 of 15 as at: 28/Feb/14 15:07
T Key Summary Assignee Reporter P Status Resolution Created Updated Due
CLOUDSTACK-6181
Root resize
Unassigned Nux Open Unresolved 27/Feb/14 27/Feb/14
CLOUDSTACK-6161
distributed routing and network ACL with OVS plug-in
Murali Reddy Murali Reddy Open Unresolved 24/Feb/14 24/Feb/14
CLOUDSTACK-6092
Storage OverProvisioning as a Per Primary Basis
Saksham Srivastava Saksham Srivastava Open Unresolved 13/Feb/14 20/Feb/14
CLOUDSTACK-6144
HA for guest VMs running Hyper-V
Unassigned Rajesh Battala Open Unresolved 20/Feb/14 20/Feb/14
CLOUDSTACK-6143
Storage Live-Migration support for Hyper-V
Unassigned Rajesh Battala Open Unresolved 20/Feb/14 20/Feb/14
CLOUDSTACK-6142
Zone Wide Primary Store in Hyper-V
Unassigned Rajesh Battala Open Unresolved 20/Feb/14 20/Feb/14
CLOUDSTACK-6104
PVLAN support for CloudStack deployment over Nexus 1000v in VMware environment
Sateesh Chodapuneedi Sateesh Chodapuneedi Open Unresolved 14/Feb/14 15/Feb/14
CLOUDSTACK-6109
Support of iSCSI as primary store in Hyper-V
Rajesh Battala Rajesh Battala Open Unresolved 14/Feb/14 14/Feb/14
CLOUDSTACK-6106
Support of VPC in HyperV
Rajesh Battala Rajesh Battala Open Unresolved 14/Feb/14 14/Feb/14
CLOUDSTACK-6090
Virtual Router Service Failure Alerting
Harikrishna Patnala Harikrishna Patnala Open Unresolved 13/Feb/14 13/Feb/14
CLOUDSTACK-6052
List VM enhancement to support querying with multiple VM IDs
Koushik Das Koushik Das Open Unresolved 07/Feb/14 07/Feb/14
CLOUDSTACK-5569
enhance OVS plug-in to support region level VPC and guest networks that span zones
Murali Reddy Murali Reddy Open Unresolved 19/Dec/13 19/Dec/13
CLOUDSTACK-5568
introduce notion of guest network that spans multiple zones
Murali Reddy Murali Reddy Open Unresolved 19/Dec/13 19/Dec/13
CLOUDSTACK-5567
enable VPC at region level
Murali Reddy Murali Reddy Open Unresolved 19/Dec/13 19/Dec/13
CLOUDSTACK-5398
Cloudstack network-element plugin to orchestrate Juniper's switches
Unassigned Pradeep H Krishnamurthy Open Unresolved 06/Dec/13 06/Dec/13
Cheers,
Hugo
On 28 feb. 2014, at 10:17, Prasanna Santhanam <ts...@apache.org> wrote:
> On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>>
>
> But you do agree that the re-spins uncovered bugs/issues that needed
> to be fixed? Is it perhaps a mismatch in when the artifacts start
> getting tested by the users+devs as opposed to when company-x might be
> satisfied with their testing? More than 90% of the re-spins are
> bugs/issues uncovered by users who needed RC candidates and weren't
> testing artifacts on a daily basis (I could be wrong here). I don't
> think someone with a large test engineering team would wait for the
> RCs to get rolling. May be if we addressed that mismatch in timing we
> could have smaller RC phases. Something like a soft-freeze and a
> hard-freeze.
>
> post soft-freeze : users+devs do a daily test (mostly manually for
> features they care about)
> post hard-freeze : everyone only looks at a daily automated test
> report and if all looks good, we release?
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
>
Re: 4.4 Feature Freeze
Posted by Prasanna Santhanam <ts...@apache.org>.
On Fri, Feb 28, 2014 at 07:26:10AM +0000, 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 flexible with our dates.
>
But you do agree that the re-spins uncovered bugs/issues that needed
to be fixed? Is it perhaps a mismatch in when the artifacts start
getting tested by the users+devs as opposed to when company-x might be
satisfied with their testing? More than 90% of the re-spins are
bugs/issues uncovered by users who needed RC candidates and weren't
testing artifacts on a daily basis (I could be wrong here). I don't
think someone with a large test engineering team would wait for the
RCs to get rolling. May be if we addressed that mismatch in timing we
could have smaller RC phases. Something like a soft-freeze and a
hard-freeze.
post soft-freeze : users+devs do a daily test (mostly manually for
features they care about)
post hard-freeze : everyone only looks at a daily automated test
report and if all looks good, we release?
--
Prasanna.,
------------------------
Powered by BigRock.com
RE: 4.4 Feature Freeze
Posted by Alex Hitchins <al...@shapeblue.com>.
Does anyone else think that 'better' visualisation of releases and dates would help with keeping to schedules (testing, development, documentation)? Asking for tester commitment as part of submitting proposals or developing features may assist with this also.
I'm thinking something like a 1 year roadmap/overview in a simple Gantt or even list form, might help highlight development windows and ensure the community can easily see what's coming up where.
Just a thought.
Regards
Alex Hitchins
D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969
alex.hitchins@shapeblue.com
-----Original Message-----
From: Mike Tutkowski [mailto:mike.tutkowski@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 standpoint what we might do to limit pushing dates back.
One thing that I've had experience with in the storage industry (at HP and now SolidFire) is the idea of a risk-adjusted release window.
In the "best" of cases, you should expect the software to be released on X.
In the "worst" of cases, you should expect the software to be released on Y.
One issue with adapting that idea for CloudStack is that CloudStack releases are quite a bit more frequent than what we had at HP and SolidFire.
Another issue I see is with defining what a release candidate really means.
At HP and SolidFire, when we built a release candidate, that RC had a much higher probability of not being re-spun. I think this had to do with the amount of formal testing that went into each release. By the time we were ready to build a release candidate, it had been weeks before the last code change went in and there had been tons of testing performed (a lot of it
automated) during that interval.
I'm not sure, though, with four-month release cycles if that's doable for CloudStack.
On Fri, Feb 28, 2014 at 12:57 PM, Erik Weber <te...@gmail.com> wrote:
> Of course, as a customer there might be specific feature that I'd
> really want to get released as planned.
> And well, I'm not saying it's not possible to be flexible with a date
> or two in specific cases.
> I'm a bit more worried that postponing becomes the norm, e.g. that all
> future versions always get delayed, which in turn delays the next
> version. Before you know it you're down to three releases per year.
>
> As a customer, and service provider, having a bug free and stable
> environment is more important than having the hottest new features out
> there. Of course they're always welcome, but if I have to choose
> between 'über feature X but 2 months delayed' and 'fixes that critical
> bug you have on time' I'll take the latter one any day.
>
> And before anyway says it, we could of course roll our own versions,
> and just use the latest RC, but that'd be problematic for support
> contracts.
>
> Erik
>
>
> On Fri, Feb 28, 2014 at 6:59 PM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
> > Personally I'm not at much risk of missing a deadline if it's still
> > two weeks out. I was thinking more along the lines that others - who
> > have
> been
> > hard at work on 4.3 RC testing, as well - might miss their deadlines.
> >
> > I can see your point of view, Erik. In my case, it's the opposite:
> > customers would rather have feature X from SolidFire sooner rather
> > than wait another 1/3 of a year.
> >
> >
> > On Fri, Feb 28, 2014 at 7:40 AM, Erik Weber <te...@gmail.com> wrote:
> >
> > > As a customer of several companies involved with cloudstack i must
> > > say
> > that
> > > having a reliable time schedule is more important than having
> > > feature
> X.
> > > We've been waiting for 4.3 since we discovered a bug that got
> > > fixed in
> > 4.3
> > > but not in 4.2 branch and rendered us unable to use that version.
> > >
> > > If 4.3 had held it's schedule we would've been rolling almost one
> > > month ago, instead we are still wasting time waiting for a supported version.
> > >
> > > If 4.4 now were to be postponed and an important bug appears in
> > > 4.3
> with
> > a
> > > fix in 4.4 it would have me thinking about moving to other
> > > solutions
> if i
> > > know that it'll be 5-6 months before release.
> > >
> > > Erik
> > > 27. feb. 2014 20:57 skrev "Mike Tutkowski" <
> > mike.tutkowski@solidfire.com>
> > > følgende:
> > >
> > > > I'm not sure I would say that not moving the feature-freeze date
> > > > is a penalty, but it does have consequences for customers...as
> > > > does the
> fact
> > > > that we miss our release deadlines consistently.
> > > >
> > > > If you are working on a feature that hasn't been advertised to
> > > > your customers via a roadmap or some other mechanism, then it
> > > > doesn't
> really
> > > > matter, I suppose, if you release that feature today or, say,
> > > > four
> > months
> > > > from now when the next release comes out.
> > > >
> > > > However, many of us work under the direction of a roadmap that
> > > > has
> been
> > > > made visible to our customers. In such an environment, these
> customers
> > do
> > > > expect when you tell them feature X will be out in, say, 4.3
> > > > that it
> > > does,
> > > > in fact, come out in 4.3 and not four months later in 4.4.
> > > >
> > > > I just wanted to point this out because I've seen in several
> > > > e-mails
> > over
> > > > the past year the following idea: If a feature doesn't make it
> > > > into
> > this
> > > > release, no big deal - it can be put in the next release.
> > > >
> > > > While technically true, this does not take into consideration
> customer
> > > > expectations around feature-release dates.
> > > >
> > > > Personally, I'd rather push a feature-freeze date back by a
> > > > couple
> > weeks
> > > > than make customers (of mine or anyone else's) wait another 1/3
> > > > of a
> > year
> > > > or more for the feature(s) in question.
> > > >
> > > > At some point, however, we need to conduct a retrospective to
> > > > uncover
> > why
> > > > we are not hitting our deadlines. Perhaps the deadlines are too
> tight?
> > > > Perhaps there is a process issue missing (or in place) that
> > > > prevents
> us
> > > > from doing so? etc.
> > > >
> > > > Thanks!
> > > >
> > > >
> > > > On Wed, Feb 26, 2014 at 8:21 PM, John Kinsella
> > > > <jl...@stratosec.co>
> > wrote:
> > > >
> > > > > 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 issues, it's not uncommon for
> > > > > us
> to
> > > > allow
> > > > > them in late.
> > > > >
> > > > > What we have a stronger need for than 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 feature freeze date.
> > > > >
> > > > > John
> > > > >
> > > > > On Feb 26, 2014, at 7:10 PM, Ram Ganesh
> > > > > <Ra...@citrix.com>
> > 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 efforts. We shouldn't be penalizing them with this
> > > > > 2 week's feature
> > > > freeze
> > > > > schedule
> > > > > >
> > > > > > Thanks,
> > > > > > RamG
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: Animesh Chaturvedi
> > > > > >> [mailto:animesh.chaturvedi@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. As I
> > > > > >> called
> out
> > > in
> > > > > earlier
> > > > > >> mail the feature proposal date was not called out for 4.4
> > > > > >> and as
> > > such
> > > > > giving
> > > > > >> little extra room seems reasonable.
> > > > > >>
> > > > > >> Animesh
> > > > > >>
> > > > > >>> -----Original Message-----
> > > > > >>> From: Mike Tutkowski [mailto:mike.tutkowski@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
> > > > > >>> beginning to realize that a four-month release cycle has
> > > > > >>> not
> been
> > > > very
> > > > > >>> realistic for us yet.
> > > > > >>>
> > > > > >>> The main issue I encounter is our month-long RC cycle
> > > > > >>> where I
> > > spend a
> > > > > >>> bunch of time validating the RC and (during that
> > > > > >>> timeframe)
> less
> > > time
> > > > > >>> developing for the next release as I had initially planned.
> > > > > >>>
> > > > > >>> Perhaps instead of extending the cycle we could consider
> > > > > >>> ways
> to
> > > > > >>> actually meet the schedule on a consistent basis. That
> > > > > >>> would be
> > > fine,
> > > > > as
> > > > > >> well.
> > > > > >>>
> > > > > >>>
> > > > > >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <
> > hugo@trippaers.nl
> > > >
> > > > > >>> wrote:
> > > > > >>>
> > > > > >>>> -1 on postponing the feature freeze. We are having this
> > discussion
> > > > > >>>> after every release, however we agreed to do a 4 month
> > > > > >>>> cycle
> so
> > > > > >>>> let's stick
> > > > > >>> to it.
> > > > > >>>>
> > > > > >>>> If there are important features that are currently being
> > developed
> > > > > >>>> but might not make this cut-off date we should discuss
> > > > > >>>> that separately, but as a point of principle lets stick
> > > > > >>>> to the
> > release
> > > > > schedule as
> > > > > >> proposed.
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> Cheers,
> > > > > >>>>
> > > > > >>>> Hugo
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
> > > > > >>>> <tr...@weberize.com>
> > > > > >>>> wrote:
> > > > > >>>>
> > > > > >>>>> +1 to Daan.
> > > > > >>>>>
> > > > > >>>>> Tracy Phillips
> > > > > >>>>> Weberize, Inc.
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> > > > > >>>>> <daan.hoogland@gmail.com
> > > > > >>>>> wrote:
> > > > > >>>>>
> > > > > >>>>>> -1 for postponing the feature freeze. It will amount to
> > > > > >>>>>> more features in the release. I'd rather shorten the
> > > > > >>>>>> cycle and do
> > > more
> > > > > >>>>>> releases then to pack more bugs in a single go.
> > > > > >>>>>>
> > > > > >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <
> > ghxandsky@gmail.com>
> > > > > >>> wrote:
> > > > > >>>>>>> +1
> > > > > >>>>>>>
> > > > > >>>>>>>
> > > > > >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> > > > > >>>>>> Abhinandan.Prateek@citrix.com
> > > > > >>>>>>>> :
> > > > > >>>>>>>
> > > > > >>>>>>>> +1 for 4.4 feature freeze on 3/28.
> > > > > >>>>>>>>
> > > > > >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> > > > > >>>>>>>> <sa...@citrix.com> wrote:
> > > > > >>>>>>>>
> > > > > >>>>>>>>>> -----Original Message-----
> > > > > >>>>>>>>>> From: Mike Tutkowski [mailto:
> mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> > > > > >>>>>>>>>
> > > > > >>>>>>>>> Regards,
> > > > > >>>>>>>>> Sateesh
> > > > > >>>>>>>>>
> > > > > >>>>>>>>>> I also agree we should discuss 4+ month development
> cycles
> > > > > >> again.
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi
> > > > > >>>>>>>>>> < animesh.chaturvedi@citrix.com> wrote:
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>>> I will start a separate discussion on 4 month
> > > > > >>>>>>>>>>> cycle or longer, but wanted to call out one more important date.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> We have a last day for feature proposal date which
> > > > > >>>>>>>>>>> is typically a month before feature freeze date.
> > > > > >>>>>>>>>>> If
> > following
> > > > > >>>>>>>>>>> 4.3 schedule + 4
> > > > > >>>>>> month
> > > > > >>>>>>>>>>> it would have been 2/14 and we are already past that.
> > Since
> > > > > >>>>>>>>>>> it was
> > > > > >>>>>> not
> > > > > >>>>>>>>>>> announced for
> > > > > >>>>>>>>>>> 4.4 release yet my suggestion would be to keep
> > > > > >>>>>>>>>>> feature proposal
> > > > > >>>>>> open
> > > > > >>>>>>>>>>> for another week and push all the dates out by 2
> > > > > >>>>>>>>>>> weeks
> > to
> > > > > >>>>>>>>>>> give
> > > > > >>>>>> folks
> > > > > >>>>>>>>>>> opportunity to finish up their features for new
> proposals
> > > > > >>>>>>>>>>> that are
> > > > > >>>>>> yet
> > > > > >>>>>>>>>>> to come out.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> To be clear that would mean pushing out feature
> > > > > >>>>>>>>>>> freeze
> to
> > > > > >>>>>>>>>>> 3/28 from
> > > > > >>>>>>>>>>> 3/14 and all the other dates likewise.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> Thanks
> > > > > >>>>>>>>>>> Animesh
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>> -----Original Message-----
> > > > > >>>>>>>>>>>> From: Animesh Chaturvedi
> > > > > >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> > > > > >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> > > > > >>>>>>>>>>>> To: dev@cloudstack.apache.org
> > > > > >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
> > > > > >>>>>>>>>>>>
> > > > > >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we
> > > > > >>>>>>>>>>>> should discuss if
> > > > > >>>>>> we
> > > > > >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs
> > > > > >>>>>>>>>>>> take 2 months. I
> > > > > >>>>>> was
> > > > > >>>>>>>>>>>> going to open up the discussion after 4.3 is
> > > > > >>>>>>>>>>>> shipped
> > > though.
> > > > > >>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> -----Original Message-----
> > > > > >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On
> > > > > >>>>>>>>>>>>> Behalf
> Of
> > > Hugo
> > > > > >>>>>>>>>>>>> Trippaers
> > > > > >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> > > > > >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
> > > > > >>>>>>>>>>>>> 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.
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> So the proposed release schedule for 4.4 would
> > > > > >>>>>>>>>>>>> look
> > like
> > > > > >>>>>>>>>>>>> this (dates slightly modified to take efficiency
> > > > > >>>>>>>>>>>>> and
> > RM's
> > > > > >>>>>>>>>>>>> personal
> > > > > >>>>>> life
> > > > > >>>>>>>>>>>>> into
> > > > > >>>>>>>>>>> account ;-) ):
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> Feature Freeze: March 14, 2014
> > > > > >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014
> till
> > > > April
> > > > > >>>>>> 18,
> > > > > >>>>>>>>>> 2014
> > > > > >>>>>>>>>>>>> (direct access for committers)
> > > > > >>>>>>>>>>>>> Stability Fixes only: April 19,
> > > 2014
> > > > > till
> > > > > >>>>>>>>>>> release (cherry picks
> > > > > >>>>>>>>>>>>> by RM only)
> > > > > >>>>>>>>>>>>> First RC: May 9,
> 2014
> > > > > >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> Cheers,
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> Hugo
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > > > > >>>>>>>>>>>>> <su...@citrix.com>
> > > > > >>>>>>>>>>>>> wrote:
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> > > > > >>>>>>>>>>>>>> 0540<tel:+442036030540>
> > > > > >>>>>> |
> > > > > >>>>>>>>>> M:
> > > > > >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden,
> > London,
> > > > > >>>>>>>>>>>>>> WC2N
> > > > > >>>>>> 4HS
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> > > > > >>>>>>>>>>>>>> Our CloudStack Infrastructure
> > > > > >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> > > > > >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7
> > > > > >>>>>>>>>>>>> SLA for
> > > > > >>>>>> CloudStack
> > > > > >>>>>>>>>>>>> Environments.
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
> > > > > >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
> > > > > >>>>>>>>>>>>> training/>
> > > > > >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
> > > > > >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-traini
> > > > > >>>>>>>>>>>>> ng/>
> > > > > >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led,
> > > > > >>>>>>>>>>>>>> On-
> > > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > > >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led,
> > > > > >>>>>>>>>>>>>> On-
> > > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > > >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led,
> > > > > >>>>>>>>>>>>>> On-
> > > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > > >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led,
> > > > > >>>>>>>>>>>>>> On-
> > > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> This email and any attachments to it may be
> > confidential
> > > > > >>>>>>>>>>>>>> and
> > > > > >>>>>> are
> > > > > >>>>>>>>>>>>>> intended
> > > > > >>>>>>>>>>>>> solely for the use of the individual to whom it
> > > > > >>>>>>>>>>>>> is
> > > > addressed.
> > > > > >>>>>> Any
> > > > > >>>>>>>>>>>>> views or opinions expressed are solely those of
> > > > > >>>>>>>>>>>>> the
> > > author
> > > > > >>>>>>>>>>>>> and
> > > > > >>>>>> do
> > > > > >>>>>>>>>>>>> not necessarily represent those of Shape Blue
> > > > > >>>>>>>>>>>>> Ltd or related companies. If you are not the
> > > > > >>>>>>>>>>>>> intended
> > recipient
> > > > > >>>>>>>>>>>>> of this email, you must neither take any action
> > > > > >>>>>>>>>>>>> based
> > > upon
> > > > > >>>>>>>>>>>>> its contents, nor
> > > > > >>>>>> copy
> > > > > >>>>>>>>>>>>> or show it to anyone. Please contact the sender
> > > > > >>>>>>>>>>>>> if
> you
> > > > > >>>>>>>>>>>>> believe
> > > > > >>>>>> you
> > > > > >>>>>>>>>>>>> have received this email in error. Shape Blue
> > > > > >>>>>>>>>>>>> Ltd is
> a
> > > > > >>>>>>>>>>>>> company incorporated in England & Wales.
> > > > > >>>>>>>>>>>>> ShapeBlue Services India LLP
> > > > > >>>>>> is a
> > > > > >>>>>>>>>>>>> company incorporated in India and is operated
> > > > > >>>>>>>>>>>>> under license
> > > > > >>>>>> from
> > > > > >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria
> > > > > >>>>>>>>>>>>> Ltda
> is a
> > > > > >>>>>>>>>>>>> company incorporated in Brasil and is operated
> > > > > >>>>>>>>>>>>> under license from Shape Blue Ltd. ShapeBlue is
> > > > > >>>>>>>>>>> a
> > > > > >>>>>>>>>>>> registered trademark.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>> --
> > > > > >>>>>>>>>> *Mike Tutkowski*
> > > > > >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> > > > > >>>>>>>>>> e: mike.tutkowski@solidfire.com
> > > > > >>>>>>>>>> o: 303.746.7302
> > > > > >>>>>>>>>> Advancing the way the world uses the cloud<
> http://solidfire.com/solution/overview/?video=play>
> > > > > >>>>>>>>>> *(tm)*
> > > > > >>>>>>>>
> > > > > >>>>>>>>
> > > > > >>>>>>
> > > > > >>>>>>
> > > > > >>>>>>
> > > > > >>>>>> --
> > > > > >>>>>> Daan
> > > > > >>>>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>
> > > > > >>>
> > > > > >>> --
> > > > > >>> *Mike Tutkowski*
> > > > > >>> *Senior CloudStack Developer, SolidFire Inc.*
> > > > > >>> e: mike.tutkowski@solidfire.com
> > > > > >>> o: 303.746.7302
> > > > > >>> Advancing the way the world uses the
> > > > > >>> cloud<http://solidfire.com/solution/overview/?video=play>
> > > > > >>> *(tm)*
> > > > >
> > > > > Stratosec - Compliance as a Service
> > > > > o: 415.315.9385
> > > > > @johnlkinsella
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > *Mike Tutkowski*
> > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > e: mike.tutkowski@solidfire.com
> > > > o: 303.746.7302
> > > > Advancing the way the world uses the
> > > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > > *(tm)*
> > > >
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *(tm)*
> >
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
I agree that postponing should not be the norm.
I think we need to figure out from a process standpoint what we might do to
limit pushing dates back.
One thing that I've had experience with in the storage industry (at HP and
now SolidFire) is the idea of a risk-adjusted release window.
In the "best" of cases, you should expect the software to be released on X.
In the "worst" of cases, you should expect the software to be released on Y.
One issue with adapting that idea for CloudStack is that CloudStack
releases are quite a bit more frequent than what we had at HP and SolidFire.
Another issue I see is with defining what a release candidate really means.
At HP and SolidFire, when we built a release candidate, that RC had a much
higher probability of not being re-spun. I think this had to do with the
amount of formal testing that went into each release. By the time we were
ready to build a release candidate, it had been weeks before the last code
change went in and there had been tons of testing performed (a lot of it
automated) during that interval.
I'm not sure, though, with four-month release cycles if that's doable for
CloudStack.
On Fri, Feb 28, 2014 at 12:57 PM, Erik Weber <te...@gmail.com> wrote:
> Of course, as a customer there might be specific feature that I'd really
> want to get released as planned.
> And well, I'm not saying it's not possible to be flexible with a date or
> two in specific cases.
> I'm a bit more worried that postponing becomes the norm, e.g. that all
> future versions always get delayed,
> which in turn delays the next version. Before you know it you're down to
> three releases per year.
>
> As a customer, and service provider, having a bug free and stable
> environment is more important
> than having the hottest new features out there. Of course they're always
> welcome, but if I have to choose
> between 'über feature X but 2 months delayed' and 'fixes that critical bug
> you have on time' I'll take the latter
> one any day.
>
> And before anyway says it, we could of course roll our own versions, and
> just use the latest RC, but that'd
> be problematic for support contracts.
>
> Erik
>
>
> On Fri, Feb 28, 2014 at 6:59 PM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
> > Personally I'm not at much risk of missing a deadline if it's still two
> > weeks out. I was thinking more along the lines that others - who have
> been
> > hard at work on 4.3 RC testing, as well - might miss their deadlines.
> >
> > I can see your point of view, Erik. In my case, it's the opposite:
> > customers would rather have feature X from SolidFire sooner rather than
> > wait another 1/3 of a year.
> >
> >
> > On Fri, Feb 28, 2014 at 7:40 AM, Erik Weber <te...@gmail.com> wrote:
> >
> > > As a customer of several companies involved with cloudstack i must say
> > that
> > > having a reliable time schedule is more important than having feature
> X.
> > > We've been waiting for 4.3 since we discovered a bug that got fixed in
> > 4.3
> > > but not in 4.2 branch and rendered us unable to use that version.
> > >
> > > If 4.3 had held it's schedule we would've been rolling almost one month
> > > ago, instead we are still wasting time waiting for a supported version.
> > >
> > > If 4.4 now were to be postponed and an important bug appears in 4.3
> with
> > a
> > > fix in 4.4 it would have me thinking about moving to other solutions
> if i
> > > know that it'll be 5-6 months before release.
> > >
> > > Erik
> > > 27. feb. 2014 20:57 skrev "Mike Tutkowski" <
> > mike.tutkowski@solidfire.com>
> > > følgende:
> > >
> > > > I'm not sure I would say that not moving the feature-freeze date is a
> > > > penalty, but it does have consequences for customers...as does the
> fact
> > > > that we miss our release deadlines consistently.
> > > >
> > > > If you are working on a feature that hasn't been advertised to your
> > > > customers via a roadmap or some other mechanism, then it doesn't
> really
> > > > matter, I suppose, if you release that feature today or, say, four
> > months
> > > > from now when the next release comes out.
> > > >
> > > > However, many of us work under the direction of a roadmap that has
> been
> > > > made visible to our customers. In such an environment, these
> customers
> > do
> > > > expect when you tell them feature X will be out in, say, 4.3 that it
> > > does,
> > > > in fact, come out in 4.3 and not four months later in 4.4.
> > > >
> > > > I just wanted to point this out because I've seen in several e-mails
> > over
> > > > the past year the following idea: If a feature doesn't make it into
> > this
> > > > release, no big deal - it can be put in the next release.
> > > >
> > > > While technically true, this does not take into consideration
> customer
> > > > expectations around feature-release dates.
> > > >
> > > > Personally, I'd rather push a feature-freeze date back by a couple
> > weeks
> > > > than make customers (of mine or anyone else's) wait another 1/3 of a
> > year
> > > > or more for the feature(s) in question.
> > > >
> > > > At some point, however, we need to conduct a retrospective to uncover
> > why
> > > > we are not hitting our deadlines. Perhaps the deadlines are too
> tight?
> > > > Perhaps there is a process issue missing (or in place) that prevents
> us
> > > > from doing so? etc.
> > > >
> > > > Thanks!
> > > >
> > > >
> > > > On Wed, Feb 26, 2014 at 8:21 PM, John Kinsella <jl...@stratosec.co>
> > wrote:
> > > >
> > > > > 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 issues, it's not uncommon for us
> to
> > > > allow
> > > > > them in late.
> > > > >
> > > > > What we have a stronger need for than 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 feature freeze date.
> > > > >
> > > > > John
> > > > >
> > > > > On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com>
> > 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
> > > > > efforts. We shouldn't be penalizing them with this 2 week's feature
> > > > freeze
> > > > > schedule
> > > > > >
> > > > > > Thanks,
> > > > > > RamG
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called
> out
> > > in
> > > > > earlier
> > > > > >> mail the feature proposal date was not called out for 4.4 and as
> > > such
> > > > > giving
> > > > > >> little extra room seems reasonable.
> > > > > >>
> > > > > >> Animesh
> > > > > >>
> > > > > >>> -----Original Message-----
> > > > > >>> From: Mike Tutkowski [mailto:mike.tutkowski@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
> > > > > >>> beginning to realize that a four-month release cycle has not
> been
> > > > very
> > > > > >>> realistic for us yet.
> > > > > >>>
> > > > > >>> The main issue I encounter is our month-long RC cycle where I
> > > spend a
> > > > > >>> bunch of time validating the RC and (during that timeframe)
> less
> > > time
> > > > > >>> developing for the next release as I had initially planned.
> > > > > >>>
> > > > > >>> Perhaps instead of extending the cycle we could consider ways
> to
> > > > > >>> actually meet the schedule on a consistent basis. That would be
> > > fine,
> > > > > as
> > > > > >> well.
> > > > > >>>
> > > > > >>>
> > > > > >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <
> > hugo@trippaers.nl
> > > >
> > > > > >>> wrote:
> > > > > >>>
> > > > > >>>> -1 on postponing the feature freeze. We are having this
> > discussion
> > > > > >>>> after every release, however we agreed to do a 4 month cycle
> so
> > > > > >>>> let's stick
> > > > > >>> to it.
> > > > > >>>>
> > > > > >>>> If there are important features that are currently being
> > developed
> > > > > >>>> but might not make this cut-off date we should discuss that
> > > > > >>>> separately, but as a point of principle lets stick to the
> > release
> > > > > schedule as
> > > > > >> proposed.
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> Cheers,
> > > > > >>>>
> > > > > >>>> Hugo
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
> > > > > >>>> <tr...@weberize.com>
> > > > > >>>> wrote:
> > > > > >>>>
> > > > > >>>>> +1 to Daan.
> > > > > >>>>>
> > > > > >>>>> Tracy Phillips
> > > > > >>>>> Weberize, Inc.
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> > > > > >>>>> <daan.hoogland@gmail.com
> > > > > >>>>> wrote:
> > > > > >>>>>
> > > > > >>>>>> -1 for postponing the feature freeze. It will amount to more
> > > > > >>>>>> features in the release. I'd rather shorten the cycle and do
> > > more
> > > > > >>>>>> releases then to pack more bugs in a single go.
> > > > > >>>>>>
> > > > > >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <
> > ghxandsky@gmail.com>
> > > > > >>> wrote:
> > > > > >>>>>>> +1
> > > > > >>>>>>>
> > > > > >>>>>>>
> > > > > >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> > > > > >>>>>> Abhinandan.Prateek@citrix.com
> > > > > >>>>>>>> :
> > > > > >>>>>>>
> > > > > >>>>>>>> +1 for 4.4 feature freeze on 3/28.
> > > > > >>>>>>>>
> > > > > >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> > > > > >>>>>>>> <sa...@citrix.com> wrote:
> > > > > >>>>>>>>
> > > > > >>>>>>>>>> -----Original Message-----
> > > > > >>>>>>>>>> From: Mike Tutkowski [mailto:
> mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> > > > > >>>>>>>>>
> > > > > >>>>>>>>> Regards,
> > > > > >>>>>>>>> Sateesh
> > > > > >>>>>>>>>
> > > > > >>>>>>>>>> I also agree we should discuss 4+ month development
> cycles
> > > > > >> again.
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> > > > > >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
> > > > > >>>>>>>>>>> longer, but wanted to call out one more important date.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> We have a last day for feature proposal date which is
> > > > > >>>>>>>>>>> typically a month before feature freeze date. If
> > following
> > > > > >>>>>>>>>>> 4.3 schedule + 4
> > > > > >>>>>> month
> > > > > >>>>>>>>>>> it would have been 2/14 and we are already past that.
> > Since
> > > > > >>>>>>>>>>> it was
> > > > > >>>>>> not
> > > > > >>>>>>>>>>> announced for
> > > > > >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
> > > > > >>>>>>>>>>> proposal
> > > > > >>>>>> open
> > > > > >>>>>>>>>>> for another week and push all the dates out by 2 weeks
> > to
> > > > > >>>>>>>>>>> give
> > > > > >>>>>> folks
> > > > > >>>>>>>>>>> opportunity to finish up their features for new
> proposals
> > > > > >>>>>>>>>>> that are
> > > > > >>>>>> yet
> > > > > >>>>>>>>>>> to come out.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> To be clear that would mean pushing out feature freeze
> to
> > > > > >>>>>>>>>>> 3/28 from
> > > > > >>>>>>>>>>> 3/14 and all the other dates likewise.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> Thanks
> > > > > >>>>>>>>>>> Animesh
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>> -----Original Message-----
> > > > > >>>>>>>>>>>> From: Animesh Chaturvedi
> > > > > >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> > > > > >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> > > > > >>>>>>>>>>>> To: dev@cloudstack.apache.org
> > > > > >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
> > > > > >>>>>>>>>>>>
> > > > > >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
> > > > > >>>>>>>>>>>> discuss if
> > > > > >>>>>> we
> > > > > >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
> > > > > >>>>>>>>>>>> months. I
> > > > > >>>>>> was
> > > > > >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped
> > > though.
> > > > > >>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> -----Original Message-----
> > > > > >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf
> Of
> > > Hugo
> > > > > >>>>>>>>>>>>> Trippaers
> > > > > >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> > > > > >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
> > > > > >>>>>>>>>>>>> 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.
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look
> > like
> > > > > >>>>>>>>>>>>> this (dates slightly modified to take efficiency and
> > RM's
> > > > > >>>>>>>>>>>>> personal
> > > > > >>>>>> life
> > > > > >>>>>>>>>>>>> into
> > > > > >>>>>>>>>>> account ;-) ):
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> Feature Freeze: March 14, 2014
> > > > > >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014
> till
> > > > April
> > > > > >>>>>> 18,
> > > > > >>>>>>>>>> 2014
> > > > > >>>>>>>>>>>>> (direct access for committers)
> > > > > >>>>>>>>>>>>> Stability Fixes only: April 19,
> > > 2014
> > > > > till
> > > > > >>>>>>>>>>> release (cherry picks
> > > > > >>>>>>>>>>>>> by RM only)
> > > > > >>>>>>>>>>>>> First RC: May 9,
> 2014
> > > > > >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> Cheers,
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> Hugo
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > > > > >>>>>>>>>>>>> <su...@citrix.com>
> > > > > >>>>>>>>>>>>> wrote:
> > > > > >>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> > > > > >>>>>>>>>>>>>> 0540<tel:+442036030540>
> > > > > >>>>>> |
> > > > > >>>>>>>>>> M:
> > > > > >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden,
> > London,
> > > > > >>>>>>>>>>>>>> WC2N
> > > > > >>>>>> 4HS
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> > > > > >>>>>>>>>>>>>> Our CloudStack Infrastructure
> > > > > >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> > > > > >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> > > > > >>>>>> CloudStack
> > > > > >>>>>>>>>>>>> Environments.
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
> > > > > >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
> > > > > >>>>>>>>>>>>> training/>
> > > > > >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
> > > > > >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> > > > > >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> > > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > > >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> > > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > > >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> > > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > > >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> > > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > > >>>>>>>>>>>>>>
> > > > > >>>>>>>>>>>>>> This email and any attachments to it may be
> > confidential
> > > > > >>>>>>>>>>>>>> and
> > > > > >>>>>> are
> > > > > >>>>>>>>>>>>>> intended
> > > > > >>>>>>>>>>>>> solely for the use of the individual to whom it is
> > > > addressed.
> > > > > >>>>>> Any
> > > > > >>>>>>>>>>>>> views or opinions expressed are solely those of the
> > > author
> > > > > >>>>>>>>>>>>> and
> > > > > >>>>>> do
> > > > > >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
> > > > > >>>>>>>>>>>>> related companies. If you are not the intended
> > recipient
> > > > > >>>>>>>>>>>>> of this email, you must neither take any action based
> > > upon
> > > > > >>>>>>>>>>>>> its contents, nor
> > > > > >>>>>> copy
> > > > > >>>>>>>>>>>>> or show it to anyone. Please contact the sender if
> you
> > > > > >>>>>>>>>>>>> believe
> > > > > >>>>>> you
> > > > > >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is
> a
> > > > > >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
> > > > > >>>>>>>>>>>>> Services India LLP
> > > > > >>>>>> is a
> > > > > >>>>>>>>>>>>> company incorporated in India and is operated under
> > > > > >>>>>>>>>>>>> license
> > > > > >>>>>> from
> > > > > >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda
> is a
> > > > > >>>>>>>>>>>>> company incorporated in Brasil and is operated under
> > > > > >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
> > > > > >>>>>>>>>>> a
> > > > > >>>>>>>>>>>> registered trademark.
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>> --
> > > > > >>>>>>>>>> *Mike Tutkowski*
> > > > > >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> > > > > >>>>>>>>>> e: mike.tutkowski@solidfire.com
> > > > > >>>>>>>>>> o: 303.746.7302
> > > > > >>>>>>>>>> Advancing the way the world uses the
> > > > > >>>>>>>>>> cloud<
> http://solidfire.com/solution/overview/?video=play>
> > > > > >>>>>>>>>> *(tm)*
> > > > > >>>>>>>>
> > > > > >>>>>>>>
> > > > > >>>>>>
> > > > > >>>>>>
> > > > > >>>>>>
> > > > > >>>>>> --
> > > > > >>>>>> Daan
> > > > > >>>>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>
> > > > > >>>
> > > > > >>> --
> > > > > >>> *Mike Tutkowski*
> > > > > >>> *Senior CloudStack Developer, SolidFire Inc.*
> > > > > >>> e: mike.tutkowski@solidfire.com
> > > > > >>> o: 303.746.7302
> > > > > >>> Advancing the way the world uses the
> > > > > >>> cloud<http://solidfire.com/solution/overview/?video=play>
> > > > > >>> *(tm)*
> > > > >
> > > > > Stratosec - Compliance as a Service
> > > > > o: 415.315.9385
> > > > > @johnlkinsella
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > *Mike Tutkowski*
> > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > e: mike.tutkowski@solidfire.com
> > > > o: 303.746.7302
> > > > Advancing the way the world uses the
> > > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > > *(tm)*
> > > >
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *(tm)*
> >
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Erik Weber <te...@gmail.com>.
Of course, as a customer there might be specific feature that I'd really
want to get released as planned.
And well, I'm not saying it's not possible to be flexible with a date or
two in specific cases.
I'm a bit more worried that postponing becomes the norm, e.g. that all
future versions always get delayed,
which in turn delays the next version. Before you know it you're down to
three releases per year.
As a customer, and service provider, having a bug free and stable
environment is more important
than having the hottest new features out there. Of course they're always
welcome, but if I have to choose
between 'über feature X but 2 months delayed' and 'fixes that critical bug
you have on time' I'll take the latter
one any day.
And before anyway says it, we could of course roll our own versions, and
just use the latest RC, but that'd
be problematic for support contracts.
Erik
On Fri, Feb 28, 2014 at 6:59 PM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:
> Personally I'm not at much risk of missing a deadline if it's still two
> weeks out. I was thinking more along the lines that others - who have been
> hard at work on 4.3 RC testing, as well - might miss their deadlines.
>
> I can see your point of view, Erik. In my case, it's the opposite:
> customers would rather have feature X from SolidFire sooner rather than
> wait another 1/3 of a year.
>
>
> On Fri, Feb 28, 2014 at 7:40 AM, Erik Weber <te...@gmail.com> wrote:
>
> > As a customer of several companies involved with cloudstack i must say
> that
> > having a reliable time schedule is more important than having feature X.
> > We've been waiting for 4.3 since we discovered a bug that got fixed in
> 4.3
> > but not in 4.2 branch and rendered us unable to use that version.
> >
> > If 4.3 had held it's schedule we would've been rolling almost one month
> > ago, instead we are still wasting time waiting for a supported version.
> >
> > If 4.4 now were to be postponed and an important bug appears in 4.3 with
> a
> > fix in 4.4 it would have me thinking about moving to other solutions if i
> > know that it'll be 5-6 months before release.
> >
> > Erik
> > 27. feb. 2014 20:57 skrev "Mike Tutkowski" <
> mike.tutkowski@solidfire.com>
> > følgende:
> >
> > > I'm not sure I would say that not moving the feature-freeze date is a
> > > penalty, but it does have consequences for customers...as does the fact
> > > that we miss our release deadlines consistently.
> > >
> > > If you are working on a feature that hasn't been advertised to your
> > > customers via a roadmap or some other mechanism, then it doesn't really
> > > matter, I suppose, if you release that feature today or, say, four
> months
> > > from now when the next release comes out.
> > >
> > > However, many of us work under the direction of a roadmap that has been
> > > made visible to our customers. In such an environment, these customers
> do
> > > expect when you tell them feature X will be out in, say, 4.3 that it
> > does,
> > > in fact, come out in 4.3 and not four months later in 4.4.
> > >
> > > I just wanted to point this out because I've seen in several e-mails
> over
> > > the past year the following idea: If a feature doesn't make it into
> this
> > > release, no big deal - it can be put in the next release.
> > >
> > > While technically true, this does not take into consideration customer
> > > expectations around feature-release dates.
> > >
> > > Personally, I'd rather push a feature-freeze date back by a couple
> weeks
> > > than make customers (of mine or anyone else's) wait another 1/3 of a
> year
> > > or more for the feature(s) in question.
> > >
> > > At some point, however, we need to conduct a retrospective to uncover
> why
> > > we are not hitting our deadlines. Perhaps the deadlines are too tight?
> > > Perhaps there is a process issue missing (or in place) that prevents us
> > > from doing so? etc.
> > >
> > > Thanks!
> > >
> > >
> > > On Wed, Feb 26, 2014 at 8:21 PM, John Kinsella <jl...@stratosec.co>
> wrote:
> > >
> > > > 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 issues, it's not uncommon for us to
> > > allow
> > > > them in late.
> > > >
> > > > What we have a stronger need for than 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 feature freeze date.
> > > >
> > > > John
> > > >
> > > > On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com>
> 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
> > > > efforts. We shouldn't be penalizing them with this 2 week's feature
> > > freeze
> > > > schedule
> > > > >
> > > > > Thanks,
> > > > > RamG
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called out
> > in
> > > > earlier
> > > > >> mail the feature proposal date was not called out for 4.4 and as
> > such
> > > > giving
> > > > >> little extra room seems reasonable.
> > > > >>
> > > > >> Animesh
> > > > >>
> > > > >>> -----Original Message-----
> > > > >>> From: Mike Tutkowski [mailto:mike.tutkowski@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
> > > > >>> beginning to realize that a four-month release cycle has not been
> > > very
> > > > >>> realistic for us yet.
> > > > >>>
> > > > >>> The main issue I encounter is our month-long RC cycle where I
> > spend a
> > > > >>> bunch of time validating the RC and (during that timeframe) less
> > time
> > > > >>> developing for the next release as I had initially planned.
> > > > >>>
> > > > >>> Perhaps instead of extending the cycle we could consider ways to
> > > > >>> actually meet the schedule on a consistent basis. That would be
> > fine,
> > > > as
> > > > >> well.
> > > > >>>
> > > > >>>
> > > > >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <
> hugo@trippaers.nl
> > >
> > > > >>> wrote:
> > > > >>>
> > > > >>>> -1 on postponing the feature freeze. We are having this
> discussion
> > > > >>>> after every release, however we agreed to do a 4 month cycle so
> > > > >>>> let's stick
> > > > >>> to it.
> > > > >>>>
> > > > >>>> If there are important features that are currently being
> developed
> > > > >>>> but might not make this cut-off date we should discuss that
> > > > >>>> separately, but as a point of principle lets stick to the
> release
> > > > schedule as
> > > > >> proposed.
> > > > >>>>
> > > > >>>>
> > > > >>>> Cheers,
> > > > >>>>
> > > > >>>> Hugo
> > > > >>>>
> > > > >>>>
> > > > >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
> > > > >>>> <tr...@weberize.com>
> > > > >>>> wrote:
> > > > >>>>
> > > > >>>>> +1 to Daan.
> > > > >>>>>
> > > > >>>>> Tracy Phillips
> > > > >>>>> Weberize, Inc.
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> > > > >>>>> <daan.hoogland@gmail.com
> > > > >>>>> wrote:
> > > > >>>>>
> > > > >>>>>> -1 for postponing the feature freeze. It will amount to more
> > > > >>>>>> features in the release. I'd rather shorten the cycle and do
> > more
> > > > >>>>>> releases then to pack more bugs in a single go.
> > > > >>>>>>
> > > > >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <
> ghxandsky@gmail.com>
> > > > >>> wrote:
> > > > >>>>>>> +1
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> > > > >>>>>> Abhinandan.Prateek@citrix.com
> > > > >>>>>>>> :
> > > > >>>>>>>
> > > > >>>>>>>> +1 for 4.4 feature freeze on 3/28.
> > > > >>>>>>>>
> > > > >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> > > > >>>>>>>> <sa...@citrix.com> wrote:
> > > > >>>>>>>>
> > > > >>>>>>>>>> -----Original Message-----
> > > > >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> > > > >>>>>>>>>
> > > > >>>>>>>>> Regards,
> > > > >>>>>>>>> Sateesh
> > > > >>>>>>>>>
> > > > >>>>>>>>>> I also agree we should discuss 4+ month development cycles
> > > > >> again.
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> > > > >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
> > > > >>>>>>>>>>> longer, but wanted to call out one more important date.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> We have a last day for feature proposal date which is
> > > > >>>>>>>>>>> typically a month before feature freeze date. If
> following
> > > > >>>>>>>>>>> 4.3 schedule + 4
> > > > >>>>>> month
> > > > >>>>>>>>>>> it would have been 2/14 and we are already past that.
> Since
> > > > >>>>>>>>>>> it was
> > > > >>>>>> not
> > > > >>>>>>>>>>> announced for
> > > > >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
> > > > >>>>>>>>>>> proposal
> > > > >>>>>> open
> > > > >>>>>>>>>>> for another week and push all the dates out by 2 weeks
> to
> > > > >>>>>>>>>>> give
> > > > >>>>>> folks
> > > > >>>>>>>>>>> opportunity to finish up their features for new proposals
> > > > >>>>>>>>>>> that are
> > > > >>>>>> yet
> > > > >>>>>>>>>>> to come out.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
> > > > >>>>>>>>>>> 3/28 from
> > > > >>>>>>>>>>> 3/14 and all the other dates likewise.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> Thanks
> > > > >>>>>>>>>>> Animesh
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>> -----Original Message-----
> > > > >>>>>>>>>>>> From: Animesh Chaturvedi
> > > > >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> > > > >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> > > > >>>>>>>>>>>> To: dev@cloudstack.apache.org
> > > > >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
> > > > >>>>>>>>>>>> discuss if
> > > > >>>>>> we
> > > > >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
> > > > >>>>>>>>>>>> months. I
> > > > >>>>>> was
> > > > >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped
> > though.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>> -----Original Message-----
> > > > >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
> > Hugo
> > > > >>>>>>>>>>>>> Trippaers
> > > > >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> > > > >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
> > > > >>>>>>>>>>>>> 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.
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look
> like
> > > > >>>>>>>>>>>>> this (dates slightly modified to take efficiency and
> RM's
> > > > >>>>>>>>>>>>> personal
> > > > >>>>>> life
> > > > >>>>>>>>>>>>> into
> > > > >>>>>>>>>>> account ;-) ):
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Feature Freeze: March 14, 2014
> > > > >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till
> > > April
> > > > >>>>>> 18,
> > > > >>>>>>>>>> 2014
> > > > >>>>>>>>>>>>> (direct access for committers)
> > > > >>>>>>>>>>>>> Stability Fixes only: April 19,
> > 2014
> > > > till
> > > > >>>>>>>>>>> release (cherry picks
> > > > >>>>>>>>>>>>> by RM only)
> > > > >>>>>>>>>>>>> First RC: May 9, 2014
> > > > >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Cheers,
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Hugo
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > > > >>>>>>>>>>>>> <su...@citrix.com>
> > > > >>>>>>>>>>>>> wrote:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> > > > >>>>>>>>>>>>>> 0540<tel:+442036030540>
> > > > >>>>>> |
> > > > >>>>>>>>>> M:
> > > > >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden,
> London,
> > > > >>>>>>>>>>>>>> WC2N
> > > > >>>>>> 4HS
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> > > > >>>>>>>>>>>>>> Our CloudStack Infrastructure
> > > > >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> > > > >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> > > > >>>>>> CloudStack
> > > > >>>>>>>>>>>>> Environments.
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
> > > > >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
> > > > >>>>>>>>>>>>> training/>
> > > > >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
> > > > >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> > > > >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> > > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> This email and any attachments to it may be
> confidential
> > > > >>>>>>>>>>>>>> and
> > > > >>>>>> are
> > > > >>>>>>>>>>>>>> intended
> > > > >>>>>>>>>>>>> solely for the use of the individual to whom it is
> > > addressed.
> > > > >>>>>> Any
> > > > >>>>>>>>>>>>> views or opinions expressed are solely those of the
> > author
> > > > >>>>>>>>>>>>> and
> > > > >>>>>> do
> > > > >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
> > > > >>>>>>>>>>>>> related companies. If you are not the intended
> recipient
> > > > >>>>>>>>>>>>> of this email, you must neither take any action based
> > upon
> > > > >>>>>>>>>>>>> its contents, nor
> > > > >>>>>> copy
> > > > >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
> > > > >>>>>>>>>>>>> believe
> > > > >>>>>> you
> > > > >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
> > > > >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
> > > > >>>>>>>>>>>>> Services India LLP
> > > > >>>>>> is a
> > > > >>>>>>>>>>>>> company incorporated in India and is operated under
> > > > >>>>>>>>>>>>> license
> > > > >>>>>> from
> > > > >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > > > >>>>>>>>>>>>> company incorporated in Brasil and is operated under
> > > > >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
> > > > >>>>>>>>>>> a
> > > > >>>>>>>>>>>> registered trademark.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >>>>>>>>>> --
> > > > >>>>>>>>>> *Mike Tutkowski*
> > > > >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> > > > >>>>>>>>>> e: mike.tutkowski@solidfire.com
> > > > >>>>>>>>>> o: 303.746.7302
> > > > >>>>>>>>>> Advancing the way the world uses the
> > > > >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
> > > > >>>>>>>>>> *(tm)*
> > > > >>>>>>>>
> > > > >>>>>>>>
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> --
> > > > >>>>>> Daan
> > > > >>>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>
> > > > >>>
> > > > >>> --
> > > > >>> *Mike Tutkowski*
> > > > >>> *Senior CloudStack Developer, SolidFire Inc.*
> > > > >>> e: mike.tutkowski@solidfire.com
> > > > >>> o: 303.746.7302
> > > > >>> Advancing the way the world uses the
> > > > >>> cloud<http://solidfire.com/solution/overview/?video=play>
> > > > >>> *(tm)*
> > > >
> > > > Stratosec - Compliance as a Service
> > > > o: 415.315.9385
> > > > @johnlkinsella
> > > >
> > > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkowski@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > *(tm)*
> > >
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
>
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
Personally I'm not at much risk of missing a deadline if it's still two
weeks out. I was thinking more along the lines that others - who have been
hard at work on 4.3 RC testing, as well - might miss their deadlines.
I can see your point of view, Erik. In my case, it's the opposite:
customers would rather have feature X from SolidFire sooner rather than
wait another 1/3 of a year.
On Fri, Feb 28, 2014 at 7:40 AM, Erik Weber <te...@gmail.com> wrote:
> As a customer of several companies involved with cloudstack i must say that
> having a reliable time schedule is more important than having feature X.
> We've been waiting for 4.3 since we discovered a bug that got fixed in 4.3
> but not in 4.2 branch and rendered us unable to use that version.
>
> If 4.3 had held it's schedule we would've been rolling almost one month
> ago, instead we are still wasting time waiting for a supported version.
>
> If 4.4 now were to be postponed and an important bug appears in 4.3 with a
> fix in 4.4 it would have me thinking about moving to other solutions if i
> know that it'll be 5-6 months before release.
>
> Erik
> 27. feb. 2014 20:57 skrev "Mike Tutkowski" <mi...@solidfire.com>
> følgende:
>
> > I'm not sure I would say that not moving the feature-freeze date is a
> > penalty, but it does have consequences for customers...as does the fact
> > that we miss our release deadlines consistently.
> >
> > If you are working on a feature that hasn't been advertised to your
> > customers via a roadmap or some other mechanism, then it doesn't really
> > matter, I suppose, if you release that feature today or, say, four months
> > from now when the next release comes out.
> >
> > However, many of us work under the direction of a roadmap that has been
> > made visible to our customers. In such an environment, these customers do
> > expect when you tell them feature X will be out in, say, 4.3 that it
> does,
> > in fact, come out in 4.3 and not four months later in 4.4.
> >
> > I just wanted to point this out because I've seen in several e-mails over
> > the past year the following idea: If a feature doesn't make it into this
> > release, no big deal - it can be put in the next release.
> >
> > While technically true, this does not take into consideration customer
> > expectations around feature-release dates.
> >
> > Personally, I'd rather push a feature-freeze date back by a couple weeks
> > than make customers (of mine or anyone else's) wait another 1/3 of a year
> > or more for the feature(s) in question.
> >
> > At some point, however, we need to conduct a retrospective to uncover why
> > we are not hitting our deadlines. Perhaps the deadlines are too tight?
> > Perhaps there is a process issue missing (or in place) that prevents us
> > from doing so? etc.
> >
> > Thanks!
> >
> >
> > On Wed, Feb 26, 2014 at 8:21 PM, John Kinsella <jl...@stratosec.co> wrote:
> >
> > > 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 issues, it's not uncommon for us to
> > allow
> > > them in late.
> > >
> > > What we have a stronger need for than 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 feature freeze date.
> > >
> > > John
> > >
> > > On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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
> > > efforts. We shouldn't be penalizing them with this 2 week's feature
> > freeze
> > > schedule
> > > >
> > > > Thanks,
> > > > RamG
> > > >
> > > >> -----Original Message-----
> > > >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called out
> in
> > > earlier
> > > >> mail the feature proposal date was not called out for 4.4 and as
> such
> > > giving
> > > >> little extra room seems reasonable.
> > > >>
> > > >> Animesh
> > > >>
> > > >>> -----Original Message-----
> > > >>> From: Mike Tutkowski [mailto:mike.tutkowski@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
> > > >>> beginning to realize that a four-month release cycle has not been
> > very
> > > >>> realistic for us yet.
> > > >>>
> > > >>> The main issue I encounter is our month-long RC cycle where I
> spend a
> > > >>> bunch of time validating the RC and (during that timeframe) less
> time
> > > >>> developing for the next release as I had initially planned.
> > > >>>
> > > >>> Perhaps instead of extending the cycle we could consider ways to
> > > >>> actually meet the schedule on a consistent basis. That would be
> fine,
> > > as
> > > >> well.
> > > >>>
> > > >>>
> > > >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hugo@trippaers.nl
> >
> > > >>> wrote:
> > > >>>
> > > >>>> -1 on postponing the feature freeze. We are having this discussion
> > > >>>> after every release, however we agreed to do a 4 month cycle so
> > > >>>> let's stick
> > > >>> to it.
> > > >>>>
> > > >>>> If there are important features that are currently being developed
> > > >>>> but might not make this cut-off date we should discuss that
> > > >>>> separately, but as a point of principle lets stick to the release
> > > schedule as
> > > >> proposed.
> > > >>>>
> > > >>>>
> > > >>>> Cheers,
> > > >>>>
> > > >>>> Hugo
> > > >>>>
> > > >>>>
> > > >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
> > > >>>> <tr...@weberize.com>
> > > >>>> wrote:
> > > >>>>
> > > >>>>> +1 to Daan.
> > > >>>>>
> > > >>>>> Tracy Phillips
> > > >>>>> Weberize, Inc.
> > > >>>>>
> > > >>>>>
> > > >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> > > >>>>> <daan.hoogland@gmail.com
> > > >>>>> wrote:
> > > >>>>>
> > > >>>>>> -1 for postponing the feature freeze. It will amount to more
> > > >>>>>> features in the release. I'd rather shorten the cycle and do
> more
> > > >>>>>> releases then to pack more bugs in a single go.
> > > >>>>>>
> > > >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
> > > >>> wrote:
> > > >>>>>>> +1
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> > > >>>>>> Abhinandan.Prateek@citrix.com
> > > >>>>>>>> :
> > > >>>>>>>
> > > >>>>>>>> +1 for 4.4 feature freeze on 3/28.
> > > >>>>>>>>
> > > >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> > > >>>>>>>> <sa...@citrix.com> wrote:
> > > >>>>>>>>
> > > >>>>>>>>>> -----Original Message-----
> > > >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> > > >>>>>>>>>
> > > >>>>>>>>> Regards,
> > > >>>>>>>>> Sateesh
> > > >>>>>>>>>
> > > >>>>>>>>>> I also agree we should discuss 4+ month development cycles
> > > >> again.
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> > > >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
> > > >>>>>>>>>>
> > > >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
> > > >>>>>>>>>>> longer, but wanted to call out one more important date.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> We have a last day for feature proposal date which is
> > > >>>>>>>>>>> typically a month before feature freeze date. If following
> > > >>>>>>>>>>> 4.3 schedule + 4
> > > >>>>>> month
> > > >>>>>>>>>>> it would have been 2/14 and we are already past that. Since
> > > >>>>>>>>>>> it was
> > > >>>>>> not
> > > >>>>>>>>>>> announced for
> > > >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
> > > >>>>>>>>>>> proposal
> > > >>>>>> open
> > > >>>>>>>>>>> for another week and push all the dates out by 2 weeks to
> > > >>>>>>>>>>> give
> > > >>>>>> folks
> > > >>>>>>>>>>> opportunity to finish up their features for new proposals
> > > >>>>>>>>>>> that are
> > > >>>>>> yet
> > > >>>>>>>>>>> to come out.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
> > > >>>>>>>>>>> 3/28 from
> > > >>>>>>>>>>> 3/14 and all the other dates likewise.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Thanks
> > > >>>>>>>>>>> Animesh
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>> -----Original Message-----
> > > >>>>>>>>>>>> From: Animesh Chaturvedi
> > > >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> > > >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> > > >>>>>>>>>>>> To: dev@cloudstack.apache.org
> > > >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
> > > >>>>>>>>>>>> discuss if
> > > >>>>>> we
> > > >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
> > > >>>>>>>>>>>> months. I
> > > >>>>>> was
> > > >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped
> though.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>> -----Original Message-----
> > > >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
> Hugo
> > > >>>>>>>>>>>>> Trippaers
> > > >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> > > >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
> > > >>>>>>>>>>>>> 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.
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
> > > >>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
> > > >>>>>>>>>>>>> personal
> > > >>>>>> life
> > > >>>>>>>>>>>>> into
> > > >>>>>>>>>>> account ;-) ):
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Feature Freeze: March 14, 2014
> > > >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till
> > April
> > > >>>>>> 18,
> > > >>>>>>>>>> 2014
> > > >>>>>>>>>>>>> (direct access for committers)
> > > >>>>>>>>>>>>> Stability Fixes only: April 19,
> 2014
> > > till
> > > >>>>>>>>>>> release (cherry picks
> > > >>>>>>>>>>>>> by RM only)
> > > >>>>>>>>>>>>> First RC: May 9, 2014
> > > >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Cheers,
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Hugo
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > > >>>>>>>>>>>>> <su...@citrix.com>
> > > >>>>>>>>>>>>> wrote:
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> > > >>>>>>>>>>>>>> 0540<tel:+442036030540>
> > > >>>>>> |
> > > >>>>>>>>>> M:
> > > >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
> > > >>>>>>>>>>>>>> WC2N
> > > >>>>>> 4HS
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> > > >>>>>>>>>>>>>> Our CloudStack Infrastructure
> > > >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> > > >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> > > >>>>>> CloudStack
> > > >>>>>>>>>>>>> Environments.
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
> > > >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
> > > >>>>>>>>>>>>> training/>
> > > >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
> > > >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> > > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> This email and any attachments to it may be confidential
> > > >>>>>>>>>>>>>> and
> > > >>>>>> are
> > > >>>>>>>>>>>>>> intended
> > > >>>>>>>>>>>>> solely for the use of the individual to whom it is
> > addressed.
> > > >>>>>> Any
> > > >>>>>>>>>>>>> views or opinions expressed are solely those of the
> author
> > > >>>>>>>>>>>>> and
> > > >>>>>> do
> > > >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
> > > >>>>>>>>>>>>> related companies. If you are not the intended recipient
> > > >>>>>>>>>>>>> of this email, you must neither take any action based
> upon
> > > >>>>>>>>>>>>> its contents, nor
> > > >>>>>> copy
> > > >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
> > > >>>>>>>>>>>>> believe
> > > >>>>>> you
> > > >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
> > > >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
> > > >>>>>>>>>>>>> Services India LLP
> > > >>>>>> is a
> > > >>>>>>>>>>>>> company incorporated in India and is operated under
> > > >>>>>>>>>>>>> license
> > > >>>>>> from
> > > >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > > >>>>>>>>>>>>> company incorporated in Brasil and is operated under
> > > >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
> > > >>>>>>>>>>> a
> > > >>>>>>>>>>>> registered trademark.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>> --
> > > >>>>>>>>>> *Mike Tutkowski*
> > > >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> > > >>>>>>>>>> e: mike.tutkowski@solidfire.com
> > > >>>>>>>>>> o: 303.746.7302
> > > >>>>>>>>>> Advancing the way the world uses the
> > > >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
> > > >>>>>>>>>> *(tm)*
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> Daan
> > > >>>>>>
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> *Mike Tutkowski*
> > > >>> *Senior CloudStack Developer, SolidFire Inc.*
> > > >>> e: mike.tutkowski@solidfire.com
> > > >>> o: 303.746.7302
> > > >>> Advancing the way the world uses the
> > > >>> cloud<http://solidfire.com/solution/overview/?video=play>
> > > >>> *(tm)*
> > >
> > > Stratosec - Compliance as a Service
> > > o: 415.315.9385
> > > @johnlkinsella
> > >
> > >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *(tm)*
> >
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Abhinandan Prateek <Ab...@citrix.com>.
I think we should have a rigid feature proposal date. Then we can go thru
the features and the effort required and be flexible on feature freeze
date.
All features are not equal and some features will require some flexibility
in terms of feature freeze. Yes if some feature is complex and will not be
of sufficient quality even if the dates were bit flexible should be moved
out.
Will say that as committers we should be very rigid about the quality.
This means having a tight control on features that should go in. Once that
decision is made help the feature owners with some flexibility to get
quality code in.
-abhi
On 28/02/14 8:10 pm, "Erik Weber" <te...@gmail.com> wrote:
>As a customer of several companies involved with cloudstack i must say
>that
>having a reliable time schedule is more important than having feature X.
>We've been waiting for 4.3 since we discovered a bug that got fixed in 4.3
>but not in 4.2 branch and rendered us unable to use that version.
>
>If 4.3 had held it's schedule we would've been rolling almost one month
>ago, instead we are still wasting time waiting for a supported version.
>
>If 4.4 now were to be postponed and an important bug appears in 4.3 with a
>fix in 4.4 it would have me thinking about moving to other solutions if i
>know that it'll be 5-6 months before release.
>
>Erik
> 27. feb. 2014 20:57 skrev "Mike Tutkowski" <mi...@solidfire.com>
>følgende:
>
>> I'm not sure I would say that not moving the feature-freeze date is a
>> penalty, but it does have consequences for customers...as does the fact
>> that we miss our release deadlines consistently.
>>
>> If you are working on a feature that hasn't been advertised to your
>> customers via a roadmap or some other mechanism, then it doesn't really
>> matter, I suppose, if you release that feature today or, say, four
>>months
>> from now when the next release comes out.
>>
>> However, many of us work under the direction of a roadmap that has been
>> made visible to our customers. In such an environment, these customers
>>do
>> expect when you tell them feature X will be out in, say, 4.3 that it
>>does,
>> in fact, come out in 4.3 and not four months later in 4.4.
>>
>> I just wanted to point this out because I've seen in several e-mails
>>over
>> the past year the following idea: If a feature doesn't make it into this
>> release, no big deal - it can be put in the next release.
>>
>> While technically true, this does not take into consideration customer
>> expectations around feature-release dates.
>>
>> Personally, I'd rather push a feature-freeze date back by a couple weeks
>> than make customers (of mine or anyone else's) wait another 1/3 of a
>>year
>> or more for the feature(s) in question.
>>
>> At some point, however, we need to conduct a retrospective to uncover
>>why
>> we are not hitting our deadlines. Perhaps the deadlines are too tight?
>> Perhaps there is a process issue missing (or in place) that prevents us
>> from doing so? etc.
>>
>> Thanks!
>>
>>
>> On Wed, Feb 26, 2014 at 8:21 PM, John Kinsella <jl...@stratosec.co> wrote:
>>
>> > 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 issues, it's not uncommon for us to
>> allow
>> > them in late.
>> >
>> > What we have a stronger need for than 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 feature freeze date.
>> >
>> > John
>> >
>> > On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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
>> > efforts. We shouldn't be penalizing them with this 2 week's feature
>> freeze
>> > schedule
>> > >
>> > > Thanks,
>> > > RamG
>> > >
>> > >> -----Original Message-----
>> > >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called out
>>in
>> > earlier
>> > >> mail the feature proposal date was not called out for 4.4 and as
>>such
>> > giving
>> > >> little extra room seems reasonable.
>> > >>
>> > >> Animesh
>> > >>
>> > >>> -----Original Message-----
>> > >>> From: Mike Tutkowski [mailto:mike.tutkowski@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
>> > >>> beginning to realize that a four-month release cycle has not been
>> very
>> > >>> realistic for us yet.
>> > >>>
>> > >>> The main issue I encounter is our month-long RC cycle where I
>>spend a
>> > >>> bunch of time validating the RC and (during that timeframe) less
>>time
>> > >>> developing for the next release as I had initially planned.
>> > >>>
>> > >>> Perhaps instead of extending the cycle we could consider ways to
>> > >>> actually meet the schedule on a consistent basis. That would be
>>fine,
>> > as
>> > >> well.
>> > >>>
>> > >>>
>> > >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers
>><hu...@trippaers.nl>
>> > >>> wrote:
>> > >>>
>> > >>>> -1 on postponing the feature freeze. We are having this
>>discussion
>> > >>>> after every release, however we agreed to do a 4 month cycle so
>> > >>>> let's stick
>> > >>> to it.
>> > >>>>
>> > >>>> If there are important features that are currently being
>>developed
>> > >>>> but might not make this cut-off date we should discuss that
>> > >>>> separately, but as a point of principle lets stick to the release
>> > schedule as
>> > >> proposed.
>> > >>>>
>> > >>>>
>> > >>>> Cheers,
>> > >>>>
>> > >>>> Hugo
>> > >>>>
>> > >>>>
>> > >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>> > >>>> <tr...@weberize.com>
>> > >>>> wrote:
>> > >>>>
>> > >>>>> +1 to Daan.
>> > >>>>>
>> > >>>>> Tracy Phillips
>> > >>>>> Weberize, Inc.
>> > >>>>>
>> > >>>>>
>> > >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>> > >>>>> <daan.hoogland@gmail.com
>> > >>>>> wrote:
>> > >>>>>
>> > >>>>>> -1 for postponing the feature freeze. It will amount to more
>> > >>>>>> features in the release. I'd rather shorten the cycle and do
>>more
>> > >>>>>> releases then to pack more bugs in a single go.
>> > >>>>>>
>> > >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
>> > >>> wrote:
>> > >>>>>>> +1
>> > >>>>>>>
>> > >>>>>>>
>> > >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>> > >>>>>> Abhinandan.Prateek@citrix.com
>> > >>>>>>>> :
>> > >>>>>>>
>> > >>>>>>>> +1 for 4.4 feature freeze on 3/28.
>> > >>>>>>>>
>> > >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>> > >>>>>>>> <sa...@citrix.com> wrote:
>> > >>>>>>>>
>> > >>>>>>>>>> -----Original Message-----
>> > >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>> > >>>>>>>>>
>> > >>>>>>>>> Regards,
>> > >>>>>>>>> Sateesh
>> > >>>>>>>>>
>> > >>>>>>>>>> I also agree we should discuss 4+ month development cycles
>> > >> again.
>> > >>>>>>>>>>
>> > >>>>>>>>>>
>> > >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>> > >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>> > >>>>>>>>>>
>> > >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>> > >>>>>>>>>>> longer, but wanted to call out one more important date.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> We have a last day for feature proposal date which is
>> > >>>>>>>>>>> typically a month before feature freeze date. If following
>> > >>>>>>>>>>> 4.3 schedule + 4
>> > >>>>>> month
>> > >>>>>>>>>>> it would have been 2/14 and we are already past that.
>>Since
>> > >>>>>>>>>>> it was
>> > >>>>>> not
>> > >>>>>>>>>>> announced for
>> > >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>> > >>>>>>>>>>> proposal
>> > >>>>>> open
>> > >>>>>>>>>>> for another week and push all the dates out by 2 weeks to
>> > >>>>>>>>>>> give
>> > >>>>>> folks
>> > >>>>>>>>>>> opportunity to finish up their features for new proposals
>> > >>>>>>>>>>> that are
>> > >>>>>> yet
>> > >>>>>>>>>>> to come out.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>> > >>>>>>>>>>> 3/28 from
>> > >>>>>>>>>>> 3/14 and all the other dates likewise.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> Thanks
>> > >>>>>>>>>>> Animesh
>> > >>>>>>>>>>>
>> > >>>>>>>>>>>> -----Original Message-----
>> > >>>>>>>>>>>> From: Animesh Chaturvedi
>> > >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>> > >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>> > >>>>>>>>>>>> To: dev@cloudstack.apache.org
>> > >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>> > >>>>>>>>>>>>
>> > >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>> > >>>>>>>>>>>> discuss if
>> > >>>>>> we
>> > >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>> > >>>>>>>>>>>> months. I
>> > >>>>>> was
>> > >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped
>>though.
>> > >>>>>>>>>>>>
>> > >>>>>>>>>>>>> -----Original Message-----
>> > >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
>>Hugo
>> > >>>>>>>>>>>>> Trippaers
>> > >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>> > >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>> > >>>>>>>>>>>>> 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.
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
>> > >>>>>>>>>>>>> this (dates slightly modified to take efficiency and
>>RM's
>> > >>>>>>>>>>>>> personal
>> > >>>>>> life
>> > >>>>>>>>>>>>> into
>> > >>>>>>>>>>> account ;-) ):
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> Feature Freeze: March 14, 2014
>> > >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till
>> April
>> > >>>>>> 18,
>> > >>>>>>>>>> 2014
>> > >>>>>>>>>>>>> (direct access for committers)
>> > >>>>>>>>>>>>> Stability Fixes only: April 19,
>>2014
>> > till
>> > >>>>>>>>>>> release (cherry picks
>> > >>>>>>>>>>>>> by RM only)
>> > >>>>>>>>>>>>> First RC: May 9, 2014
>> > >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> Cheers,
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> Hugo
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>> > >>>>>>>>>>>>> <su...@citrix.com>
>> > >>>>>>>>>>>>> wrote:
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>> > >>>>>>>>>>>>>> 0540<tel:+442036030540>
>> > >>>>>> |
>> > >>>>>>>>>> M:
>> > >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
>> > >>>>>>>>>>>>>> WC2N
>> > >>>>>> 4HS
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>> > >>>>>>>>>>>>>> Our CloudStack Infrastructure
>> > >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>> > >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>> > >>>>>> CloudStack
>> > >>>>>>>>>>>>> Environments.
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>> > >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>> > >>>>>>>>>>>>> training/>
>> > >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>> > >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> This email and any attachments to it may be
>>confidential
>> > >>>>>>>>>>>>>> and
>> > >>>>>> are
>> > >>>>>>>>>>>>>> intended
>> > >>>>>>>>>>>>> solely for the use of the individual to whom it is
>> addressed.
>> > >>>>>> Any
>> > >>>>>>>>>>>>> views or opinions expressed are solely those of the
>>author
>> > >>>>>>>>>>>>> and
>> > >>>>>> do
>> > >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>> > >>>>>>>>>>>>> related companies. If you are not the intended recipient
>> > >>>>>>>>>>>>> of this email, you must neither take any action based
>>upon
>> > >>>>>>>>>>>>> its contents, nor
>> > >>>>>> copy
>> > >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>> > >>>>>>>>>>>>> believe
>> > >>>>>> you
>> > >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>> > >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>> > >>>>>>>>>>>>> Services India LLP
>> > >>>>>> is a
>> > >>>>>>>>>>>>> company incorporated in India and is operated under
>> > >>>>>>>>>>>>> license
>> > >>>>>> from
>> > >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>> > >>>>>>>>>>>>> company incorporated in Brasil and is operated under
>> > >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>> > >>>>>>>>>>> a
>> > >>>>>>>>>>>> registered trademark.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>>
>> > >>>>>>>>>>
>> > >>>>>>>>>>
>> > >>>>>>>>>> --
>> > >>>>>>>>>> *Mike Tutkowski*
>> > >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>> > >>>>>>>>>> e: mike.tutkowski@solidfire.com
>> > >>>>>>>>>> o: 303.746.7302
>> > >>>>>>>>>> Advancing the way the world uses the
>> > >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>> > >>>>>>>>>> *(tm)*
>> > >>>>>>>>
>> > >>>>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> --
>> > >>>>>> Daan
>> > >>>>>>
>> > >>>>
>> > >>>>
>> > >>>
>> > >>>
>> > >>> --
>> > >>> *Mike Tutkowski*
>> > >>> *Senior CloudStack Developer, SolidFire Inc.*
>> > >>> e: mike.tutkowski@solidfire.com
>> > >>> o: 303.746.7302
>> > >>> Advancing the way the world uses the
>> > >>> cloud<http://solidfire.com/solution/overview/?video=play>
>> > >>> *(tm)*
>> >
>> > Stratosec - Compliance as a Service
>> > o: 415.315.9385
>> > @johnlkinsella
>> >
>> >
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud<http://solidfire.com/solution/overview/?video=play>
>> *(tm)*
>>
Re: 4.4 Feature Freeze
Posted by Erik Weber <te...@gmail.com>.
As a customer of several companies involved with cloudstack i must say that
having a reliable time schedule is more important than having feature X.
We've been waiting for 4.3 since we discovered a bug that got fixed in 4.3
but not in 4.2 branch and rendered us unable to use that version.
If 4.3 had held it's schedule we would've been rolling almost one month
ago, instead we are still wasting time waiting for a supported version.
If 4.4 now were to be postponed and an important bug appears in 4.3 with a
fix in 4.4 it would have me thinking about moving to other solutions if i
know that it'll be 5-6 months before release.
Erik
27. feb. 2014 20:57 skrev "Mike Tutkowski" <mi...@solidfire.com>
følgende:
> I'm not sure I would say that not moving the feature-freeze date is a
> penalty, but it does have consequences for customers...as does the fact
> that we miss our release deadlines consistently.
>
> If you are working on a feature that hasn't been advertised to your
> customers via a roadmap or some other mechanism, then it doesn't really
> matter, I suppose, if you release that feature today or, say, four months
> from now when the next release comes out.
>
> However, many of us work under the direction of a roadmap that has been
> made visible to our customers. In such an environment, these customers do
> expect when you tell them feature X will be out in, say, 4.3 that it does,
> in fact, come out in 4.3 and not four months later in 4.4.
>
> I just wanted to point this out because I've seen in several e-mails over
> the past year the following idea: If a feature doesn't make it into this
> release, no big deal - it can be put in the next release.
>
> While technically true, this does not take into consideration customer
> expectations around feature-release dates.
>
> Personally, I'd rather push a feature-freeze date back by a couple weeks
> than make customers (of mine or anyone else's) wait another 1/3 of a year
> or more for the feature(s) in question.
>
> At some point, however, we need to conduct a retrospective to uncover why
> we are not hitting our deadlines. Perhaps the deadlines are too tight?
> Perhaps there is a process issue missing (or in place) that prevents us
> from doing so? etc.
>
> Thanks!
>
>
> On Wed, Feb 26, 2014 at 8:21 PM, John Kinsella <jl...@stratosec.co> wrote:
>
> > 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 issues, it's not uncommon for us to
> allow
> > them in late.
> >
> > What we have a stronger need for than 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 feature freeze date.
> >
> > John
> >
> > On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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
> > efforts. We shouldn't be penalizing them with this 2 week's feature
> freeze
> > schedule
> > >
> > > Thanks,
> > > RamG
> > >
> > >> -----Original Message-----
> > >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called out in
> > earlier
> > >> mail the feature proposal date was not called out for 4.4 and as such
> > giving
> > >> little extra room seems reasonable.
> > >>
> > >> Animesh
> > >>
> > >>> -----Original Message-----
> > >>> From: Mike Tutkowski [mailto:mike.tutkowski@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
> > >>> beginning to realize that a four-month release cycle has not been
> very
> > >>> realistic for us yet.
> > >>>
> > >>> The main issue I encounter is our month-long RC cycle where I spend a
> > >>> bunch of time validating the RC and (during that timeframe) less time
> > >>> developing for the next release as I had initially planned.
> > >>>
> > >>> Perhaps instead of extending the cycle we could consider ways to
> > >>> actually meet the schedule on a consistent basis. That would be fine,
> > as
> > >> well.
> > >>>
> > >>>
> > >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
> > >>> wrote:
> > >>>
> > >>>> -1 on postponing the feature freeze. We are having this discussion
> > >>>> after every release, however we agreed to do a 4 month cycle so
> > >>>> let's stick
> > >>> to it.
> > >>>>
> > >>>> If there are important features that are currently being developed
> > >>>> but might not make this cut-off date we should discuss that
> > >>>> separately, but as a point of principle lets stick to the release
> > schedule as
> > >> proposed.
> > >>>>
> > >>>>
> > >>>> Cheers,
> > >>>>
> > >>>> Hugo
> > >>>>
> > >>>>
> > >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
> > >>>> <tr...@weberize.com>
> > >>>> wrote:
> > >>>>
> > >>>>> +1 to Daan.
> > >>>>>
> > >>>>> Tracy Phillips
> > >>>>> Weberize, Inc.
> > >>>>>
> > >>>>>
> > >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> > >>>>> <daan.hoogland@gmail.com
> > >>>>> wrote:
> > >>>>>
> > >>>>>> -1 for postponing the feature freeze. It will amount to more
> > >>>>>> features in the release. I'd rather shorten the cycle and do more
> > >>>>>> releases then to pack more bugs in a single go.
> > >>>>>>
> > >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
> > >>> wrote:
> > >>>>>>> +1
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> > >>>>>> Abhinandan.Prateek@citrix.com
> > >>>>>>>> :
> > >>>>>>>
> > >>>>>>>> +1 for 4.4 feature freeze on 3/28.
> > >>>>>>>>
> > >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> > >>>>>>>> <sa...@citrix.com> wrote:
> > >>>>>>>>
> > >>>>>>>>>> -----Original Message-----
> > >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> > >>>>>>>>>
> > >>>>>>>>> Regards,
> > >>>>>>>>> Sateesh
> > >>>>>>>>>
> > >>>>>>>>>> I also agree we should discuss 4+ month development cycles
> > >> again.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> > >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
> > >>>>>>>>>>> longer, but wanted to call out one more important date.
> > >>>>>>>>>>>
> > >>>>>>>>>>> We have a last day for feature proposal date which is
> > >>>>>>>>>>> typically a month before feature freeze date. If following
> > >>>>>>>>>>> 4.3 schedule + 4
> > >>>>>> month
> > >>>>>>>>>>> it would have been 2/14 and we are already past that. Since
> > >>>>>>>>>>> it was
> > >>>>>> not
> > >>>>>>>>>>> announced for
> > >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
> > >>>>>>>>>>> proposal
> > >>>>>> open
> > >>>>>>>>>>> for another week and push all the dates out by 2 weeks to
> > >>>>>>>>>>> give
> > >>>>>> folks
> > >>>>>>>>>>> opportunity to finish up their features for new proposals
> > >>>>>>>>>>> that are
> > >>>>>> yet
> > >>>>>>>>>>> to come out.
> > >>>>>>>>>>>
> > >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
> > >>>>>>>>>>> 3/28 from
> > >>>>>>>>>>> 3/14 and all the other dates likewise.
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> Thanks
> > >>>>>>>>>>> Animesh
> > >>>>>>>>>>>
> > >>>>>>>>>>>> -----Original Message-----
> > >>>>>>>>>>>> From: Animesh Chaturvedi
> > >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> > >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> > >>>>>>>>>>>> To: dev@cloudstack.apache.org
> > >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
> > >>>>>>>>>>>> discuss if
> > >>>>>> we
> > >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
> > >>>>>>>>>>>> months. I
> > >>>>>> was
> > >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>> -----Original Message-----
> > >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
> > >>>>>>>>>>>>> Trippaers
> > >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> > >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
> > >>>>>>>>>>>>> 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.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
> > >>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
> > >>>>>>>>>>>>> personal
> > >>>>>> life
> > >>>>>>>>>>>>> into
> > >>>>>>>>>>> account ;-) ):
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Feature Freeze: March 14, 2014
> > >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till
> April
> > >>>>>> 18,
> > >>>>>>>>>> 2014
> > >>>>>>>>>>>>> (direct access for committers)
> > >>>>>>>>>>>>> Stability Fixes only: April 19, 2014
> > till
> > >>>>>>>>>>> release (cherry picks
> > >>>>>>>>>>>>> by RM only)
> > >>>>>>>>>>>>> First RC: May 9, 2014
> > >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Cheers,
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Hugo
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > >>>>>>>>>>>>> <su...@citrix.com>
> > >>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> > >>>>>>>>>>>>>> 0540<tel:+442036030540>
> > >>>>>> |
> > >>>>>>>>>> M:
> > >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
> > >>>>>>>>>>>>>> WC2N
> > >>>>>> 4HS
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> > >>>>>>>>>>>>>> Our CloudStack Infrastructure
> > >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> > >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> > >>>>>> CloudStack
> > >>>>>>>>>>>>> Environments.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
> > >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
> > >>>>>>>>>>>>> training/>
> > >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
> > >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> This email and any attachments to it may be confidential
> > >>>>>>>>>>>>>> and
> > >>>>>> are
> > >>>>>>>>>>>>>> intended
> > >>>>>>>>>>>>> solely for the use of the individual to whom it is
> addressed.
> > >>>>>> Any
> > >>>>>>>>>>>>> views or opinions expressed are solely those of the author
> > >>>>>>>>>>>>> and
> > >>>>>> do
> > >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
> > >>>>>>>>>>>>> related companies. If you are not the intended recipient
> > >>>>>>>>>>>>> of this email, you must neither take any action based upon
> > >>>>>>>>>>>>> its contents, nor
> > >>>>>> copy
> > >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
> > >>>>>>>>>>>>> believe
> > >>>>>> you
> > >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
> > >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
> > >>>>>>>>>>>>> Services India LLP
> > >>>>>> is a
> > >>>>>>>>>>>>> company incorporated in India and is operated under
> > >>>>>>>>>>>>> license
> > >>>>>> from
> > >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > >>>>>>>>>>>>> company incorporated in Brasil and is operated under
> > >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
> > >>>>>>>>>>> a
> > >>>>>>>>>>>> registered trademark.
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> --
> > >>>>>>>>>> *Mike Tutkowski*
> > >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> > >>>>>>>>>> e: mike.tutkowski@solidfire.com
> > >>>>>>>>>> o: 303.746.7302
> > >>>>>>>>>> Advancing the way the world uses the
> > >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
> > >>>>>>>>>> *(tm)*
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> Daan
> > >>>>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> *Mike Tutkowski*
> > >>> *Senior CloudStack Developer, SolidFire Inc.*
> > >>> e: mike.tutkowski@solidfire.com
> > >>> o: 303.746.7302
> > >>> Advancing the way the world uses the
> > >>> cloud<http://solidfire.com/solution/overview/?video=play>
> > >>> *(tm)*
> >
> > Stratosec - Compliance as a Service
> > o: 415.315.9385
> > @johnlkinsella
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
>
Re: 4.4 Feature Freeze
Posted by Daan Hoogland <da...@gmail.com>.
I don't agree, we don't *have* to be flexible wih our dates. We *can*
also be flexible with our release contents and number of releases. The
main point to not let slip is; we *must* be strict on quality.
On Fri, Feb 28, 2014 at 8:26 AM, Ram Ganesh <Ra...@citrix.com> 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 flexible with our dates.
>
> Thanks,
> RamG
>
>
>> -----Original Message-----
>> From: Mike Tutkowski [mailto:mike.tutkowski@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 consequences for customers...as does the fact that we miss
>> our release deadlines consistently.
>>
>> If you are working on a feature that hasn't been advertised to your
>> customers via a roadmap or some other mechanism, then it doesn't really
>> matter, I suppose, if you release that feature today or, say, four months
>> from now when the next release comes out.
>>
>> However, many of us work under the direction of a roadmap that has been
>> made visible to our customers. In such an environment, these customers do
>> expect when you tell them feature X will be out in, say, 4.3 that it does, in
>> fact, come out in 4.3 and not four months later in 4.4.
>>
>> I just wanted to point this out because I've seen in several e-mails over the
>> past year the following idea: If a feature doesn't make it into this release, no
>> big deal - it can be put in the next release.
>>
>> While technically true, this does not take into consideration customer
>> expectations around feature-release dates.
>>
>> Personally, I'd rather push a feature-freeze date back by a couple weeks
>> than make customers (of mine or anyone else's) wait another 1/3 of a year or
>> more for the feature(s) in question.
>>
>> At some point, however, we need to conduct a retrospective to uncover why
>> we are not hitting our deadlines. Perhaps the deadlines are too tight?
>> Perhaps there is a process issue missing (or in place) that prevents us from
>> doing so? etc.
>>
>> Thanks!
>>
>>
>> On Wed, Feb 26, 2014 at 8:21 PM, John Kinsella <jl...@stratosec.co> wrote:
>>
>> > 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 issues, it's not uncommon
>> > for us to allow them in late.
>> >
>> > What we have a stronger need for than 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 feature freeze date.
>> >
>> > John
>> >
>> > On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com>
>> 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
>> > efforts. We shouldn't be penalizing them with this 2 week's feature
>> > freeze schedule
>> > >
>> > > Thanks,
>> > > RamG
>> > >
>> > >> -----Original Message-----
>> > >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I
>> > >> called out in
>> > earlier
>> > >> mail the feature proposal date was not called out for 4.4 and as
>> > >> such
>> > giving
>> > >> little extra room seems reasonable.
>> > >>
>> > >> Animesh
>> > >>
>> > >>> -----Original Message-----
>> > >>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
>> > >>> been very realistic for us yet.
>> > >>>
>> > >>> The main issue I encounter is our month-long RC cycle where I
>> > >>> spend a bunch of time validating the RC and (during that
>> > >>> timeframe) less time developing for the next release as I had initially
>> planned.
>> > >>>
>> > >>> Perhaps instead of extending the cycle we could consider ways to
>> > >>> actually meet the schedule on a consistent basis. That would be
>> > >>> fine,
>> > as
>> > >> well.
>> > >>>
>> > >>>
>> > >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers
>> > >>> <hu...@trippaers.nl>
>> > >>> wrote:
>> > >>>
>> > >>>> -1 on postponing the feature freeze. We are having this
>> > >>>> discussion after every release, however we agreed to do a 4 month
>> > >>>> cycle so let's stick
>> > >>> to it.
>> > >>>>
>> > >>>> If there are important features that are currently being
>> > >>>> developed but might not make this cut-off date we should discuss
>> > >>>> that separately, but as a point of principle lets stick to the
>> > >>>> release
>> > schedule as
>> > >> proposed.
>> > >>>>
>> > >>>>
>> > >>>> Cheers,
>> > >>>>
>> > >>>> Hugo
>> > >>>>
>> > >>>>
>> > >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>> > >>>> <tr...@weberize.com>
>> > >>>> wrote:
>> > >>>>
>> > >>>>> +1 to Daan.
>> > >>>>>
>> > >>>>> Tracy Phillips
>> > >>>>> Weberize, Inc.
>> > >>>>>
>> > >>>>>
>> > >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>> > >>>>> <daan.hoogland@gmail.com
>> > >>>>> wrote:
>> > >>>>>
>> > >>>>>> -1 for postponing the feature freeze. It will amount to more
>> > >>>>>> features in the release. I'd rather shorten the cycle and do
>> > >>>>>> more releases then to pack more bugs in a single go.
>> > >>>>>>
>> > >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star
>> <gh...@gmail.com>
>> > >>> wrote:
>> > >>>>>>> +1
>> > >>>>>>>
>> > >>>>>>>
>> > >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>> > >>>>>> Abhinandan.Prateek@citrix.com
>> > >>>>>>>> :
>> > >>>>>>>
>> > >>>>>>>> +1 for 4.4 feature freeze on 3/28.
>> > >>>>>>>>
>> > >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>> > >>>>>>>> <sa...@citrix.com> wrote:
>> > >>>>>>>>
>> > >>>>>>>>>> -----Original Message-----
>> > >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>> > >>>>>>>>>
>> > >>>>>>>>> Regards,
>> > >>>>>>>>> Sateesh
>> > >>>>>>>>>
>> > >>>>>>>>>> I also agree we should discuss 4+ month development cycles
>> > >> again.
>> > >>>>>>>>>>
>> > >>>>>>>>>>
>> > >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>> > >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>> > >>>>>>>>>>
>> > >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>> > >>>>>>>>>>> longer, but wanted to call out one more important date.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> We have a last day for feature proposal date which is
>> > >>>>>>>>>>> typically a month before feature freeze date. If following
>> > >>>>>>>>>>> 4.3 schedule + 4
>> > >>>>>> month
>> > >>>>>>>>>>> it would have been 2/14 and we are already past that.
>> > >>>>>>>>>>> Since it was
>> > >>>>>> not
>> > >>>>>>>>>>> announced for
>> > >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>> > >>>>>>>>>>> proposal
>> > >>>>>> open
>> > >>>>>>>>>>> for another week and push all the dates out by 2 weeks to
>> > >>>>>>>>>>> give
>> > >>>>>> folks
>> > >>>>>>>>>>> opportunity to finish up their features for new proposals
>> > >>>>>>>>>>> that are
>> > >>>>>> yet
>> > >>>>>>>>>>> to come out.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>> > >>>>>>>>>>> 3/28 from
>> > >>>>>>>>>>> 3/14 and all the other dates likewise.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> Thanks
>> > >>>>>>>>>>> Animesh
>> > >>>>>>>>>>>
>> > >>>>>>>>>>>> -----Original Message-----
>> > >>>>>>>>>>>> From: Animesh Chaturvedi
>> > >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>> > >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>> > >>>>>>>>>>>> To: dev@cloudstack.apache.org
>> > >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>> > >>>>>>>>>>>>
>> > >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>> > >>>>>>>>>>>> discuss if
>> > >>>>>> we
>> > >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>> > >>>>>>>>>>>> months. I
>> > >>>>>> was
>> > >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped
>> though.
>> > >>>>>>>>>>>>
>> > >>>>>>>>>>>>> -----Original Message-----
>> > >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
>> > >>>>>>>>>>>>> Hugo Trippaers
>> > >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>> > >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>> > >>>>>>>>>>>>> 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.
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
>> > >>>>>>>>>>>>> this (dates slightly modified to take efficiency and
>> > >>>>>>>>>>>>> RM's personal
>> > >>>>>> life
>> > >>>>>>>>>>>>> into
>> > >>>>>>>>>>> account ;-) ):
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> Feature Freeze: March 14, 2014
>> > >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>> > >>>>>> 18,
>> > >>>>>>>>>> 2014
>> > >>>>>>>>>>>>> (direct access for committers)
>> > >>>>>>>>>>>>> Stability Fixes only: April 19, 2014
>> > till
>> > >>>>>>>>>>> release (cherry picks
>> > >>>>>>>>>>>>> by RM only)
>> > >>>>>>>>>>>>> First RC: May 9, 2014
>> > >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> Cheers,
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> Hugo
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>> > >>>>>>>>>>>>> <su...@citrix.com>
>> > >>>>>>>>>>>>> wrote:
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>> > >>>>>>>>>>>>>> 0540<tel:+442036030540>
>> > >>>>>> |
>> > >>>>>>>>>> M:
>> > >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden,
>> London,
>> > >>>>>>>>>>>>>> WC2N
>> > >>>>>> 4HS
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>> > >>>>>>>>>>>>>> Our CloudStack Infrastructure
>> > >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>> > >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>> > >>>>>> CloudStack
>> > >>>>>>>>>>>>> Environments.
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>> > >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>> > >>>>>>>>>>>>> training/>
>> > >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>> > >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> This email and any attachments to it may be
>> > >>>>>>>>>>>>>> confidential and
>> > >>>>>> are
>> > >>>>>>>>>>>>>> intended
>> > >>>>>>>>>>>>> solely for the use of the individual to whom it is
>> addressed.
>> > >>>>>> Any
>> > >>>>>>>>>>>>> views or opinions expressed are solely those of the
>> > >>>>>>>>>>>>> author and
>> > >>>>>> do
>> > >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>> > >>>>>>>>>>>>> related companies. If you are not the intended recipient
>> > >>>>>>>>>>>>> of this email, you must neither take any action based
>> > >>>>>>>>>>>>> upon its contents, nor
>> > >>>>>> copy
>> > >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>> > >>>>>>>>>>>>> believe
>> > >>>>>> you
>> > >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>> > >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>> > >>>>>>>>>>>>> Services India LLP
>> > >>>>>> is a
>> > >>>>>>>>>>>>> company incorporated in India and is operated under
>> > >>>>>>>>>>>>> license
>> > >>>>>> from
>> > >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>> > >>>>>>>>>>>>> company incorporated in Brasil and is operated under
>> > >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>> > >>>>>>>>>>> a
>> > >>>>>>>>>>>> registered trademark.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>>
>> > >>>>>>>>>>
>> > >>>>>>>>>>
>> > >>>>>>>>>> --
>> > >>>>>>>>>> *Mike Tutkowski*
>> > >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>> > >>>>>>>>>> e: mike.tutkowski@solidfire.com
>> > >>>>>>>>>> o: 303.746.7302
>> > >>>>>>>>>> Advancing the way the world uses the
>> > >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>> > >>>>>>>>>> *(tm)*
>> > >>>>>>>>
>> > >>>>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> --
>> > >>>>>> Daan
>> > >>>>>>
>> > >>>>
>> > >>>>
>> > >>>
>> > >>>
>> > >>> --
>> > >>> *Mike Tutkowski*
>> > >>> *Senior CloudStack Developer, SolidFire Inc.*
>> > >>> e: mike.tutkowski@solidfire.com
>> > >>> o: 303.746.7302
>> > >>> Advancing the way the world uses the
>> > >>> cloud<http://solidfire.com/solution/overview/?video=play>
>> > >>> *(tm)*
>> >
>> > Stratosec - Compliance as a Service
>> > o: 415.315.9385
>> > @johnlkinsella
>> >
>> >
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud<http://solidfire.com/solution/overview/?video=play>
>> *(tm)*
--
Daan
RE: 4.4 Feature Freeze
Posted by Ram Ganesh <Ra...@citrix.com>.
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 flexible with our dates.
Thanks,
RamG
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@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 consequences for customers...as does the fact that we miss
> our release deadlines consistently.
>
> If you are working on a feature that hasn't been advertised to your
> customers via a roadmap or some other mechanism, then it doesn't really
> matter, I suppose, if you release that feature today or, say, four months
> from now when the next release comes out.
>
> However, many of us work under the direction of a roadmap that has been
> made visible to our customers. In such an environment, these customers do
> expect when you tell them feature X will be out in, say, 4.3 that it does, in
> fact, come out in 4.3 and not four months later in 4.4.
>
> I just wanted to point this out because I've seen in several e-mails over the
> past year the following idea: If a feature doesn't make it into this release, no
> big deal - it can be put in the next release.
>
> While technically true, this does not take into consideration customer
> expectations around feature-release dates.
>
> Personally, I'd rather push a feature-freeze date back by a couple weeks
> than make customers (of mine or anyone else's) wait another 1/3 of a year or
> more for the feature(s) in question.
>
> At some point, however, we need to conduct a retrospective to uncover why
> we are not hitting our deadlines. Perhaps the deadlines are too tight?
> Perhaps there is a process issue missing (or in place) that prevents us from
> doing so? etc.
>
> Thanks!
>
>
> On Wed, Feb 26, 2014 at 8:21 PM, John Kinsella <jl...@stratosec.co> wrote:
>
> > 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 issues, it's not uncommon
> > for us to allow them in late.
> >
> > What we have a stronger need for than 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 feature freeze date.
> >
> > John
> >
> > On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com>
> 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
> > efforts. We shouldn't be penalizing them with this 2 week's feature
> > freeze schedule
> > >
> > > Thanks,
> > > RamG
> > >
> > >> -----Original Message-----
> > >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I
> > >> called out in
> > earlier
> > >> mail the feature proposal date was not called out for 4.4 and as
> > >> such
> > giving
> > >> little extra room seems reasonable.
> > >>
> > >> Animesh
> > >>
> > >>> -----Original Message-----
> > >>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
> > >>> been very realistic for us yet.
> > >>>
> > >>> The main issue I encounter is our month-long RC cycle where I
> > >>> spend a bunch of time validating the RC and (during that
> > >>> timeframe) less time developing for the next release as I had initially
> planned.
> > >>>
> > >>> Perhaps instead of extending the cycle we could consider ways to
> > >>> actually meet the schedule on a consistent basis. That would be
> > >>> fine,
> > as
> > >> well.
> > >>>
> > >>>
> > >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers
> > >>> <hu...@trippaers.nl>
> > >>> wrote:
> > >>>
> > >>>> -1 on postponing the feature freeze. We are having this
> > >>>> discussion after every release, however we agreed to do a 4 month
> > >>>> cycle so let's stick
> > >>> to it.
> > >>>>
> > >>>> If there are important features that are currently being
> > >>>> developed but might not make this cut-off date we should discuss
> > >>>> that separately, but as a point of principle lets stick to the
> > >>>> release
> > schedule as
> > >> proposed.
> > >>>>
> > >>>>
> > >>>> Cheers,
> > >>>>
> > >>>> Hugo
> > >>>>
> > >>>>
> > >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
> > >>>> <tr...@weberize.com>
> > >>>> wrote:
> > >>>>
> > >>>>> +1 to Daan.
> > >>>>>
> > >>>>> Tracy Phillips
> > >>>>> Weberize, Inc.
> > >>>>>
> > >>>>>
> > >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> > >>>>> <daan.hoogland@gmail.com
> > >>>>> wrote:
> > >>>>>
> > >>>>>> -1 for postponing the feature freeze. It will amount to more
> > >>>>>> features in the release. I'd rather shorten the cycle and do
> > >>>>>> more releases then to pack more bugs in a single go.
> > >>>>>>
> > >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star
> <gh...@gmail.com>
> > >>> wrote:
> > >>>>>>> +1
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> > >>>>>> Abhinandan.Prateek@citrix.com
> > >>>>>>>> :
> > >>>>>>>
> > >>>>>>>> +1 for 4.4 feature freeze on 3/28.
> > >>>>>>>>
> > >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> > >>>>>>>> <sa...@citrix.com> wrote:
> > >>>>>>>>
> > >>>>>>>>>> -----Original Message-----
> > >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> > >>>>>>>>>
> > >>>>>>>>> Regards,
> > >>>>>>>>> Sateesh
> > >>>>>>>>>
> > >>>>>>>>>> I also agree we should discuss 4+ month development cycles
> > >> again.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> > >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
> > >>>>>>>>>>> longer, but wanted to call out one more important date.
> > >>>>>>>>>>>
> > >>>>>>>>>>> We have a last day for feature proposal date which is
> > >>>>>>>>>>> typically a month before feature freeze date. If following
> > >>>>>>>>>>> 4.3 schedule + 4
> > >>>>>> month
> > >>>>>>>>>>> it would have been 2/14 and we are already past that.
> > >>>>>>>>>>> Since it was
> > >>>>>> not
> > >>>>>>>>>>> announced for
> > >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
> > >>>>>>>>>>> proposal
> > >>>>>> open
> > >>>>>>>>>>> for another week and push all the dates out by 2 weeks to
> > >>>>>>>>>>> give
> > >>>>>> folks
> > >>>>>>>>>>> opportunity to finish up their features for new proposals
> > >>>>>>>>>>> that are
> > >>>>>> yet
> > >>>>>>>>>>> to come out.
> > >>>>>>>>>>>
> > >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
> > >>>>>>>>>>> 3/28 from
> > >>>>>>>>>>> 3/14 and all the other dates likewise.
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> Thanks
> > >>>>>>>>>>> Animesh
> > >>>>>>>>>>>
> > >>>>>>>>>>>> -----Original Message-----
> > >>>>>>>>>>>> From: Animesh Chaturvedi
> > >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> > >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> > >>>>>>>>>>>> To: dev@cloudstack.apache.org
> > >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
> > >>>>>>>>>>>> discuss if
> > >>>>>> we
> > >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
> > >>>>>>>>>>>> months. I
> > >>>>>> was
> > >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped
> though.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>> -----Original Message-----
> > >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
> > >>>>>>>>>>>>> Hugo Trippaers
> > >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> > >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
> > >>>>>>>>>>>>> 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.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
> > >>>>>>>>>>>>> this (dates slightly modified to take efficiency and
> > >>>>>>>>>>>>> RM's personal
> > >>>>>> life
> > >>>>>>>>>>>>> into
> > >>>>>>>>>>> account ;-) ):
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Feature Freeze: March 14, 2014
> > >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
> > >>>>>> 18,
> > >>>>>>>>>> 2014
> > >>>>>>>>>>>>> (direct access for committers)
> > >>>>>>>>>>>>> Stability Fixes only: April 19, 2014
> > till
> > >>>>>>>>>>> release (cherry picks
> > >>>>>>>>>>>>> by RM only)
> > >>>>>>>>>>>>> First RC: May 9, 2014
> > >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Cheers,
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Hugo
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > >>>>>>>>>>>>> <su...@citrix.com>
> > >>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> > >>>>>>>>>>>>>> 0540<tel:+442036030540>
> > >>>>>> |
> > >>>>>>>>>> M:
> > >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden,
> London,
> > >>>>>>>>>>>>>> WC2N
> > >>>>>> 4HS
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> > >>>>>>>>>>>>>> Our CloudStack Infrastructure
> > >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> > >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> > >>>>>> CloudStack
> > >>>>>>>>>>>>> Environments.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
> > >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
> > >>>>>>>>>>>>> training/>
> > >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
> > >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> > >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> This email and any attachments to it may be
> > >>>>>>>>>>>>>> confidential and
> > >>>>>> are
> > >>>>>>>>>>>>>> intended
> > >>>>>>>>>>>>> solely for the use of the individual to whom it is
> addressed.
> > >>>>>> Any
> > >>>>>>>>>>>>> views or opinions expressed are solely those of the
> > >>>>>>>>>>>>> author and
> > >>>>>> do
> > >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
> > >>>>>>>>>>>>> related companies. If you are not the intended recipient
> > >>>>>>>>>>>>> of this email, you must neither take any action based
> > >>>>>>>>>>>>> upon its contents, nor
> > >>>>>> copy
> > >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
> > >>>>>>>>>>>>> believe
> > >>>>>> you
> > >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
> > >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
> > >>>>>>>>>>>>> Services India LLP
> > >>>>>> is a
> > >>>>>>>>>>>>> company incorporated in India and is operated under
> > >>>>>>>>>>>>> license
> > >>>>>> from
> > >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > >>>>>>>>>>>>> company incorporated in Brasil and is operated under
> > >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
> > >>>>>>>>>>> a
> > >>>>>>>>>>>> registered trademark.
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> --
> > >>>>>>>>>> *Mike Tutkowski*
> > >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> > >>>>>>>>>> e: mike.tutkowski@solidfire.com
> > >>>>>>>>>> o: 303.746.7302
> > >>>>>>>>>> Advancing the way the world uses the
> > >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
> > >>>>>>>>>> *(tm)*
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> Daan
> > >>>>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> *Mike Tutkowski*
> > >>> *Senior CloudStack Developer, SolidFire Inc.*
> > >>> e: mike.tutkowski@solidfire.com
> > >>> o: 303.746.7302
> > >>> Advancing the way the world uses the
> > >>> cloud<http://solidfire.com/solution/overview/?video=play>
> > >>> *(tm)*
> >
> > Stratosec - Compliance as a Service
> > o: 415.315.9385
> > @johnlkinsella
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
I'm not sure I would say that not moving the feature-freeze date is a
penalty, but it does have consequences for customers...as does the fact
that we miss our release deadlines consistently.
If you are working on a feature that hasn't been advertised to your
customers via a roadmap or some other mechanism, then it doesn't really
matter, I suppose, if you release that feature today or, say, four months
from now when the next release comes out.
However, many of us work under the direction of a roadmap that has been
made visible to our customers. In such an environment, these customers do
expect when you tell them feature X will be out in, say, 4.3 that it does,
in fact, come out in 4.3 and not four months later in 4.4.
I just wanted to point this out because I've seen in several e-mails over
the past year the following idea: If a feature doesn't make it into this
release, no big deal - it can be put in the next release.
While technically true, this does not take into consideration customer
expectations around feature-release dates.
Personally, I'd rather push a feature-freeze date back by a couple weeks
than make customers (of mine or anyone else's) wait another 1/3 of a year
or more for the feature(s) in question.
At some point, however, we need to conduct a retrospective to uncover why
we are not hitting our deadlines. Perhaps the deadlines are too tight?
Perhaps there is a process issue missing (or in place) that prevents us
from doing so? etc.
Thanks!
On Wed, Feb 26, 2014 at 8:21 PM, John Kinsella <jl...@stratosec.co> wrote:
> 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 issues, it's not uncommon for us to allow
> them in late.
>
> What we have a stronger need for than 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 feature freeze date.
>
> John
>
> On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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
> efforts. We shouldn't be penalizing them with this 2 week's feature freeze
> schedule
> >
> > Thanks,
> > RamG
> >
> >> -----Original Message-----
> >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called out in
> earlier
> >> mail the feature proposal date was not called out for 4.4 and as such
> giving
> >> little extra room seems reasonable.
> >>
> >> Animesh
> >>
> >>> -----Original Message-----
> >>> From: Mike Tutkowski [mailto:mike.tutkowski@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
> >>> beginning to realize that a four-month release cycle has not been very
> >>> realistic for us yet.
> >>>
> >>> The main issue I encounter is our month-long RC cycle where I spend a
> >>> bunch of time validating the RC and (during that timeframe) less time
> >>> developing for the next release as I had initially planned.
> >>>
> >>> Perhaps instead of extending the cycle we could consider ways to
> >>> actually meet the schedule on a consistent basis. That would be fine,
> as
> >> well.
> >>>
> >>>
> >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
> >>> wrote:
> >>>
> >>>> -1 on postponing the feature freeze. We are having this discussion
> >>>> after every release, however we agreed to do a 4 month cycle so
> >>>> let's stick
> >>> to it.
> >>>>
> >>>> If there are important features that are currently being developed
> >>>> but might not make this cut-off date we should discuss that
> >>>> separately, but as a point of principle lets stick to the release
> schedule as
> >> proposed.
> >>>>
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Hugo
> >>>>
> >>>>
> >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
> >>>> <tr...@weberize.com>
> >>>> wrote:
> >>>>
> >>>>> +1 to Daan.
> >>>>>
> >>>>> Tracy Phillips
> >>>>> Weberize, Inc.
> >>>>>
> >>>>>
> >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> >>>>> <daan.hoogland@gmail.com
> >>>>> wrote:
> >>>>>
> >>>>>> -1 for postponing the feature freeze. It will amount to more
> >>>>>> features in the release. I'd rather shorten the cycle and do more
> >>>>>> releases then to pack more bugs in a single go.
> >>>>>>
> >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
> >>> wrote:
> >>>>>>> +1
> >>>>>>>
> >>>>>>>
> >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> >>>>>> Abhinandan.Prateek@citrix.com
> >>>>>>>> :
> >>>>>>>
> >>>>>>>> +1 for 4.4 feature freeze on 3/28.
> >>>>>>>>
> >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> >>>>>>>> <sa...@citrix.com> wrote:
> >>>>>>>>
> >>>>>>>>>> -----Original Message-----
> >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Sateesh
> >>>>>>>>>
> >>>>>>>>>> I also agree we should discuss 4+ month development cycles
> >> again.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
> >>>>>>>>>>> longer, but wanted to call out one more important date.
> >>>>>>>>>>>
> >>>>>>>>>>> We have a last day for feature proposal date which is
> >>>>>>>>>>> typically a month before feature freeze date. If following
> >>>>>>>>>>> 4.3 schedule + 4
> >>>>>> month
> >>>>>>>>>>> it would have been 2/14 and we are already past that. Since
> >>>>>>>>>>> it was
> >>>>>> not
> >>>>>>>>>>> announced for
> >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
> >>>>>>>>>>> proposal
> >>>>>> open
> >>>>>>>>>>> for another week and push all the dates out by 2 weeks to
> >>>>>>>>>>> give
> >>>>>> folks
> >>>>>>>>>>> opportunity to finish up their features for new proposals
> >>>>>>>>>>> that are
> >>>>>> yet
> >>>>>>>>>>> to come out.
> >>>>>>>>>>>
> >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
> >>>>>>>>>>> 3/28 from
> >>>>>>>>>>> 3/14 and all the other dates likewise.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks
> >>>>>>>>>>> Animesh
> >>>>>>>>>>>
> >>>>>>>>>>>> -----Original Message-----
> >>>>>>>>>>>> From: Animesh Chaturvedi
> >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> >>>>>>>>>>>> To: dev@cloudstack.apache.org
> >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
> >>>>>>>>>>>>
> >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
> >>>>>>>>>>>> discuss if
> >>>>>> we
> >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
> >>>>>>>>>>>> months. I
> >>>>>> was
> >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
> >>>>>>>>>>>>
> >>>>>>>>>>>>> -----Original Message-----
> >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
> >>>>>>>>>>>>> Trippaers
> >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
> >>>>>>>>>>>>> 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.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
> >>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
> >>>>>>>>>>>>> personal
> >>>>>> life
> >>>>>>>>>>>>> into
> >>>>>>>>>>> account ;-) ):
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Feature Freeze: March 14, 2014
> >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
> >>>>>> 18,
> >>>>>>>>>> 2014
> >>>>>>>>>>>>> (direct access for committers)
> >>>>>>>>>>>>> Stability Fixes only: April 19, 2014
> till
> >>>>>>>>>>> release (cherry picks
> >>>>>>>>>>>>> by RM only)
> >>>>>>>>>>>>> First RC: May 9, 2014
> >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hugo
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> >>>>>>>>>>>>> <su...@citrix.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> >>>>>>>>>>>>>> 0540<tel:+442036030540>
> >>>>>> |
> >>>>>>>>>> M:
> >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
> >>>>>>>>>>>>>> WC2N
> >>>>>> 4HS
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> >>>>>>>>>>>>>> Our CloudStack Infrastructure
> >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> >>>>>> CloudStack
> >>>>>>>>>>>>> Environments.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
> >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
> >>>>>>>>>>>>> training/>
> >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
> >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> This email and any attachments to it may be confidential
> >>>>>>>>>>>>>> and
> >>>>>> are
> >>>>>>>>>>>>>> intended
> >>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
> >>>>>> Any
> >>>>>>>>>>>>> views or opinions expressed are solely those of the author
> >>>>>>>>>>>>> and
> >>>>>> do
> >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
> >>>>>>>>>>>>> related companies. If you are not the intended recipient
> >>>>>>>>>>>>> of this email, you must neither take any action based upon
> >>>>>>>>>>>>> its contents, nor
> >>>>>> copy
> >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
> >>>>>>>>>>>>> believe
> >>>>>> you
> >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
> >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
> >>>>>>>>>>>>> Services India LLP
> >>>>>> is a
> >>>>>>>>>>>>> company incorporated in India and is operated under
> >>>>>>>>>>>>> license
> >>>>>> from
> >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> >>>>>>>>>>>>> company incorporated in Brasil and is operated under
> >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
> >>>>>>>>>>> a
> >>>>>>>>>>>> registered trademark.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> *Mike Tutkowski*
> >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> >>>>>>>>>> e: mike.tutkowski@solidfire.com
> >>>>>>>>>> o: 303.746.7302
> >>>>>>>>>> Advancing the way the world uses the
> >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
> >>>>>>>>>> *(tm)*
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Daan
> >>>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>> *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkowski@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the
> >>> cloud<http://solidfire.com/solution/overview/?video=play>
> >>> *(tm)*
>
> Stratosec - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
RE: 4.4 Feature Freeze
Posted by Raja Pullela <ra...@citrix.com>.
+1 for the 3/28 Feature Freeze.
If we try to close on the Feature Freeze sooner than when we are ready, we will end up finding more blockers/criticals and end up spending more time on bug fixing. This could potentially result in moving the RC?
So, bottom line - it is like we pay now or pay later!
-----Original Message-----
From: Marcus [mailto:shadowsor@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 have a hard time straddling the two during this phase.
On Wed, Feb 26, 2014 at 9:08 PM, Ram Ganesh <Ra...@citrix.com> wrote:
> I agree on the RC process! Few thoughts from my end
>
> - I see a rush of "request to cherry pick 4.3" requests from committers. This may be a burden for an RM. We can simplify it by RM responding to the email with "OK to commit" or "Not ok to commit" email response. This should free up some time for RM to concentrate on other critical issues
> - Between 2 RC cycles we need to have enough time so that
> other blocker bugs are identified and we finalize only these need to
> be fixed in the next RC cycle. What we found is new blocker issues are
> raised during every RC cycle. Also we need to take a hard look at the
> bug raised during these RC cycle and do a reality check if these are
> actually blocker bugs or can be fixed in one of our maintenance
> builds\cycles
>
> If my memory serves better during 4.1 release we had an opposite
> problem wherein we though developers moved on with 4.2 release and
> thereby impacting the quality of 4.1 release. I would say we should be
> flexible with our dates but definitely not way off the radar
>
> Thanks,
> RamG
>
>> -----Original Message-----
>> From: John Kinsella [mailto:jlk@stratosec.co]
>> 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 issues, it's not
>> uncommon for us to allow them in late.
>>
>> What we have a stronger need for than 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 feature freeze date.
>>
>> John
>>
>> On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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 efforts. We shouldn't be penalizing them with this 2
>> > week's feature freeze schedule
>> >
>> > Thanks,
>> > RamG
>> >
>> >> -----Original Message-----
>> >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I
>> >> called out in earlier mail the feature proposal date was not
>> >> called out for
>> >> 4.4 and as such giving little extra room seems reasonable.
>> >>
>> >> Animesh
>> >>
>> >>> -----Original Message-----
>> >>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has
>> >>> not been very realistic for us yet.
>> >>>
>> >>> The main issue I encounter is our month-long RC cycle where I
>> >>> spend a bunch of time validating the RC and (during that
>> >>> timeframe) less time developing for the next release as I had initially planned.
>> >>>
>> >>> Perhaps instead of extending the cycle we could consider ways to
>> >>> actually meet the schedule on a consistent basis. That would be
>> >>> fine, as
>> >> well.
>> >>>
>> >>>
>> >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers
>> >>> <hu...@trippaers.nl>
>> >>> wrote:
>> >>>
>> >>>> -1 on postponing the feature freeze. We are having this
>> >>>> discussion after every release, however we agreed to do a 4
>> >>>> month cycle so let's stick
>> >>> to it.
>> >>>>
>> >>>> If there are important features that are currently being
>> >>>> developed but might not make this cut-off date we should discuss
>> >>>> that separately, but as a point of principle lets stick to the
>> >>>> release schedule as
>> >> proposed.
>> >>>>
>> >>>>
>> >>>> Cheers,
>> >>>>
>> >>>> Hugo
>> >>>>
>> >>>>
>> >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>> >>>> <tr...@weberize.com>
>> >>>> wrote:
>> >>>>
>> >>>>> +1 to Daan.
>> >>>>>
>> >>>>> Tracy Phillips
>> >>>>> Weberize, Inc.
>> >>>>>
>> >>>>>
>> >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>> >>>>> <daan.hoogland@gmail.com
>> >>>>> wrote:
>> >>>>>
>> >>>>>> -1 for postponing the feature freeze. It will amount to more
>> >>>>>> features in the release. I'd rather shorten the cycle and do
>> >>>>>> more releases then to pack more bugs in a single go.
>> >>>>>>
>> >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star
>> >>>>>> <gh...@gmail.com>
>> >>> wrote:
>> >>>>>>> +1
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>> >>>>>> Abhinandan.Prateek@citrix.com
>> >>>>>>>> :
>> >>>>>>>
>> >>>>>>>> +1 for 4.4 feature freeze on 3/28.
>> >>>>>>>>
>> >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>> >>>>>>>> <sa...@citrix.com> wrote:
>> >>>>>>>>
>> >>>>>>>>>> -----Original Message-----
>> >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>> >>>>>>>>>
>> >>>>>>>>> Regards,
>> >>>>>>>>> Sateesh
>> >>>>>>>>>
>> >>>>>>>>>> I also agree we should discuss 4+ month development cycles
>> >> again.
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>> >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>> >>>>>>>>>>> longer, but wanted to call out one more important date.
>> >>>>>>>>>>>
>> >>>>>>>>>>> We have a last day for feature proposal date which is
>> >>>>>>>>>>> typically a month before feature freeze date. If
>> >>>>>>>>>>> following
>> >>>>>>>>>>> 4.3 schedule + 4
>> >>>>>> month
>> >>>>>>>>>>> it would have been 2/14 and we are already past that.
>> >>>>>>>>>>> Since it was
>> >>>>>> not
>> >>>>>>>>>>> announced for
>> >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>> >>>>>>>>>>> proposal
>> >>>>>> open
>> >>>>>>>>>>> for another week and push all the dates out by 2 weeks
>> >>>>>>>>>>> to give
>> >>>>>> folks
>> >>>>>>>>>>> opportunity to finish up their features for new proposals
>> >>>>>>>>>>> that are
>> >>>>>> yet
>> >>>>>>>>>>> to come out.
>> >>>>>>>>>>>
>> >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>> >>>>>>>>>>> 3/28 from
>> >>>>>>>>>>> 3/14 and all the other dates likewise.
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> Thanks
>> >>>>>>>>>>> Animesh
>> >>>>>>>>>>>
>> >>>>>>>>>>>> -----Original Message-----
>> >>>>>>>>>>>> From: Animesh Chaturvedi
>> >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>> >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>> >>>>>>>>>>>> To: dev@cloudstack.apache.org
>> >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>> >>>>>>>>>>>> discuss if
>> >>>>>> we
>> >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>> >>>>>>>>>>>> months. I
>> >>>>>> was
>> >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>> -----Original Message-----
>> >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
>> Hugo
>> >>>>>>>>>>>>> Trippaers
>> >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>> >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>> >>>>>>>>>>>>> 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.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look
>> >>>>>>>>>>>>> like this (dates slightly modified to take efficiency
>> >>>>>>>>>>>>> and RM's personal
>> >>>>>> life
>> >>>>>>>>>>>>> into
>> >>>>>>>>>>> account ;-) ):
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Feature Freeze: March 14, 2014
>> >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>> >>>>>> 18,
>> >>>>>>>>>> 2014
>> >>>>>>>>>>>>> (direct access for committers)
>> >>>>>>>>>>>>> Stability Fixes only: April 19, 2014 till
>> >>>>>>>>>>> release (cherry picks
>> >>>>>>>>>>>>> by RM only)
>> >>>>>>>>>>>>> First RC: May 9, 2014
>> >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Cheers,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Hugo
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>> >>>>>>>>>>>>> <su...@citrix.com>
>> >>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>> >>>>>>>>>>>>>> 0540<tel:+442036030540>
>> >>>>>> |
>> >>>>>>>>>> M:
>> >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden,
>> London,
>> >>>>>>>>>>>>>> WC2N
>> >>>>>> 4HS
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>> >>>>>>>>>>>>>> Our CloudStack Infrastructure
>> >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>> >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>> >>>>>> CloudStack
>> >>>>>>>>>>>>> Environments.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>> >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>> >>>>>>>>>>>>> training/>
>> >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>> >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> This email and any attachments to it may be
>> >>>>>>>>>>>>>> confidential and
>> >>>>>> are
>> >>>>>>>>>>>>>> intended
>> >>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
>> >>>>>> Any
>> >>>>>>>>>>>>> views or opinions expressed are solely those of the
>> >>>>>>>>>>>>> author and
>> >>>>>> do
>> >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>> >>>>>>>>>>>>> related companies. If you are not the intended
>> >>>>>>>>>>>>> recipient of this email, you must neither take any
>> >>>>>>>>>>>>> action based upon its contents, nor
>> >>>>>> copy
>> >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>> >>>>>>>>>>>>> believe
>> >>>>>> you
>> >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>> >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>> >>>>>>>>>>>>> Services India LLP
>> >>>>>> is a
>> >>>>>>>>>>>>> company incorporated in India and is operated under
>> >>>>>>>>>>>>> license
>> >>>>>> from
>> >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>> >>>>>>>>>>>>> company incorporated in Brasil and is operated under
>> >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>> >>>>>>>>>>> a
>> >>>>>>>>>>>> registered trademark.
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> --
>> >>>>>>>>>> *Mike Tutkowski*
>> >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>> >>>>>>>>>> e: mike.tutkowski@solidfire.com
>> >>>>>>>>>> o: 303.746.7302
>> >>>>>>>>>> Advancing the way the world uses the
>> >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>> >>>>>>>>>> *(tm)*
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Daan
>> >>>>>>
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> *Mike Tutkowski*
>> >>> *Senior CloudStack Developer, SolidFire Inc.*
>> >>> e: mike.tutkowski@solidfire.com
>> >>> o: 303.746.7302
>> >>> Advancing the way the world uses the
>> >>> cloud<http://solidfire.com/solution/overview/?video=play>
>> >>> *(tm)*
>>
>> Stratosec - Compliance as a Service
>> o: 415.315.9385
>> @johnlkinsella
>
Re: 4.4 Feature Freeze
Posted by Marcus <sh...@gmail.com>.
Perhaps we just need to reduce overlap. Most people work on 4.3 until
it's out the door, I think. Personally, I have a hard time straddling
the two during this phase.
On Wed, Feb 26, 2014 at 9:08 PM, Ram Ganesh <Ra...@citrix.com> wrote:
> I agree on the RC process! Few thoughts from my end
>
> - I see a rush of "request to cherry pick 4.3" requests from committers. This may be a burden for an RM. We can simplify it by RM responding to the email with "OK to commit" or "Not ok to commit" email response. This should free up some time for RM to concentrate on other critical issues
> - Between 2 RC cycles we need to have enough time so that other blocker bugs are identified and we finalize only these need to be fixed in the next RC cycle. What we found is new blocker issues are raised during every RC cycle. Also we need to take a hard look at the bug raised during these RC cycle and do a reality check if these are actually blocker bugs or can be fixed in one of our maintenance builds\cycles
>
> If my memory serves better during 4.1 release we had an opposite problem wherein we though developers moved on with 4.2 release and thereby impacting the quality of 4.1 release. I would say we should be flexible with our dates but definitely not way off the radar
>
> Thanks,
> RamG
>
>> -----Original Message-----
>> From: John Kinsella [mailto:jlk@stratosec.co]
>> 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 issues, it's not uncommon for us to allow them
>> in late.
>>
>> What we have a stronger need for than 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 feature freeze date.
>>
>> John
>>
>> On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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
>> > efforts. We shouldn't be penalizing them with this 2 week's feature
>> > freeze schedule
>> >
>> > Thanks,
>> > RamG
>> >
>> >> -----Original Message-----
>> >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called
>> >> out in earlier mail the feature proposal date was not called out for
>> >> 4.4 and as such giving little extra room seems reasonable.
>> >>
>> >> Animesh
>> >>
>> >>> -----Original Message-----
>> >>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
>> >>> been very realistic for us yet.
>> >>>
>> >>> The main issue I encounter is our month-long RC cycle where I spend
>> >>> a bunch of time validating the RC and (during that timeframe) less
>> >>> time developing for the next release as I had initially planned.
>> >>>
>> >>> Perhaps instead of extending the cycle we could consider ways to
>> >>> actually meet the schedule on a consistent basis. That would be
>> >>> fine, as
>> >> well.
>> >>>
>> >>>
>> >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
>> >>> wrote:
>> >>>
>> >>>> -1 on postponing the feature freeze. We are having this discussion
>> >>>> after every release, however we agreed to do a 4 month cycle so
>> >>>> let's stick
>> >>> to it.
>> >>>>
>> >>>> If there are important features that are currently being developed
>> >>>> but might not make this cut-off date we should discuss that
>> >>>> separately, but as a point of principle lets stick to the release
>> >>>> schedule as
>> >> proposed.
>> >>>>
>> >>>>
>> >>>> Cheers,
>> >>>>
>> >>>> Hugo
>> >>>>
>> >>>>
>> >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>> >>>> <tr...@weberize.com>
>> >>>> wrote:
>> >>>>
>> >>>>> +1 to Daan.
>> >>>>>
>> >>>>> Tracy Phillips
>> >>>>> Weberize, Inc.
>> >>>>>
>> >>>>>
>> >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>> >>>>> <daan.hoogland@gmail.com
>> >>>>> wrote:
>> >>>>>
>> >>>>>> -1 for postponing the feature freeze. It will amount to more
>> >>>>>> features in the release. I'd rather shorten the cycle and do more
>> >>>>>> releases then to pack more bugs in a single go.
>> >>>>>>
>> >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
>> >>> wrote:
>> >>>>>>> +1
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>> >>>>>> Abhinandan.Prateek@citrix.com
>> >>>>>>>> :
>> >>>>>>>
>> >>>>>>>> +1 for 4.4 feature freeze on 3/28.
>> >>>>>>>>
>> >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>> >>>>>>>> <sa...@citrix.com> wrote:
>> >>>>>>>>
>> >>>>>>>>>> -----Original Message-----
>> >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>> >>>>>>>>>
>> >>>>>>>>> Regards,
>> >>>>>>>>> Sateesh
>> >>>>>>>>>
>> >>>>>>>>>> I also agree we should discuss 4+ month development cycles
>> >> again.
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>> >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>> >>>>>>>>>>> longer, but wanted to call out one more important date.
>> >>>>>>>>>>>
>> >>>>>>>>>>> We have a last day for feature proposal date which is
>> >>>>>>>>>>> typically a month before feature freeze date. If following
>> >>>>>>>>>>> 4.3 schedule + 4
>> >>>>>> month
>> >>>>>>>>>>> it would have been 2/14 and we are already past that. Since
>> >>>>>>>>>>> it was
>> >>>>>> not
>> >>>>>>>>>>> announced for
>> >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>> >>>>>>>>>>> proposal
>> >>>>>> open
>> >>>>>>>>>>> for another week and push all the dates out by 2 weeks to
>> >>>>>>>>>>> give
>> >>>>>> folks
>> >>>>>>>>>>> opportunity to finish up their features for new proposals
>> >>>>>>>>>>> that are
>> >>>>>> yet
>> >>>>>>>>>>> to come out.
>> >>>>>>>>>>>
>> >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>> >>>>>>>>>>> 3/28 from
>> >>>>>>>>>>> 3/14 and all the other dates likewise.
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> Thanks
>> >>>>>>>>>>> Animesh
>> >>>>>>>>>>>
>> >>>>>>>>>>>> -----Original Message-----
>> >>>>>>>>>>>> From: Animesh Chaturvedi
>> >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>> >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>> >>>>>>>>>>>> To: dev@cloudstack.apache.org
>> >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>> >>>>>>>>>>>> discuss if
>> >>>>>> we
>> >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>> >>>>>>>>>>>> months. I
>> >>>>>> was
>> >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>> -----Original Message-----
>> >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
>> Hugo
>> >>>>>>>>>>>>> Trippaers
>> >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>> >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>> >>>>>>>>>>>>> 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.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
>> >>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
>> >>>>>>>>>>>>> personal
>> >>>>>> life
>> >>>>>>>>>>>>> into
>> >>>>>>>>>>> account ;-) ):
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Feature Freeze: March 14, 2014
>> >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>> >>>>>> 18,
>> >>>>>>>>>> 2014
>> >>>>>>>>>>>>> (direct access for committers)
>> >>>>>>>>>>>>> Stability Fixes only: April 19, 2014 till
>> >>>>>>>>>>> release (cherry picks
>> >>>>>>>>>>>>> by RM only)
>> >>>>>>>>>>>>> First RC: May 9, 2014
>> >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Cheers,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Hugo
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>> >>>>>>>>>>>>> <su...@citrix.com>
>> >>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>> >>>>>>>>>>>>>> 0540<tel:+442036030540>
>> >>>>>> |
>> >>>>>>>>>> M:
>> >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden,
>> London,
>> >>>>>>>>>>>>>> WC2N
>> >>>>>> 4HS
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>> >>>>>>>>>>>>>> Our CloudStack Infrastructure
>> >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>> >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>> >>>>>> CloudStack
>> >>>>>>>>>>>>> Environments.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>> >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>> >>>>>>>>>>>>> training/>
>> >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>> >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> This email and any attachments to it may be confidential
>> >>>>>>>>>>>>>> and
>> >>>>>> are
>> >>>>>>>>>>>>>> intended
>> >>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
>> >>>>>> Any
>> >>>>>>>>>>>>> views or opinions expressed are solely those of the author
>> >>>>>>>>>>>>> and
>> >>>>>> do
>> >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>> >>>>>>>>>>>>> related companies. If you are not the intended recipient
>> >>>>>>>>>>>>> of this email, you must neither take any action based upon
>> >>>>>>>>>>>>> its contents, nor
>> >>>>>> copy
>> >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>> >>>>>>>>>>>>> believe
>> >>>>>> you
>> >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>> >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>> >>>>>>>>>>>>> Services India LLP
>> >>>>>> is a
>> >>>>>>>>>>>>> company incorporated in India and is operated under
>> >>>>>>>>>>>>> license
>> >>>>>> from
>> >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>> >>>>>>>>>>>>> company incorporated in Brasil and is operated under
>> >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>> >>>>>>>>>>> a
>> >>>>>>>>>>>> registered trademark.
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> --
>> >>>>>>>>>> *Mike Tutkowski*
>> >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>> >>>>>>>>>> e: mike.tutkowski@solidfire.com
>> >>>>>>>>>> o: 303.746.7302
>> >>>>>>>>>> Advancing the way the world uses the
>> >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>> >>>>>>>>>> *(tm)*
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Daan
>> >>>>>>
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> *Mike Tutkowski*
>> >>> *Senior CloudStack Developer, SolidFire Inc.*
>> >>> e: mike.tutkowski@solidfire.com
>> >>> o: 303.746.7302
>> >>> Advancing the way the world uses the
>> >>> cloud<http://solidfire.com/solution/overview/?video=play>
>> >>> *(tm)*
>>
>> Stratosec - Compliance as a Service
>> o: 415.315.9385
>> @johnlkinsella
>
RE: 4.4 Feature Freeze
Posted by Ram Ganesh <Ra...@citrix.com>.
I agree on the RC process! Few thoughts from my end
- I see a rush of "request to cherry pick 4.3" requests from committers. This may be a burden for an RM. We can simplify it by RM responding to the email with "OK to commit" or "Not ok to commit" email response. This should free up some time for RM to concentrate on other critical issues
- Between 2 RC cycles we need to have enough time so that other blocker bugs are identified and we finalize only these need to be fixed in the next RC cycle. What we found is new blocker issues are raised during every RC cycle. Also we need to take a hard look at the bug raised during these RC cycle and do a reality check if these are actually blocker bugs or can be fixed in one of our maintenance builds\cycles
If my memory serves better during 4.1 release we had an opposite problem wherein we though developers moved on with 4.2 release and thereby impacting the quality of 4.1 release. I would say we should be flexible with our dates but definitely not way off the radar
Thanks,
RamG
> -----Original Message-----
> From: John Kinsella [mailto:jlk@stratosec.co]
> 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 issues, it's not uncommon for us to allow them
> in late.
>
> What we have a stronger need for than 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 feature freeze date.
>
> John
>
> On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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
> > efforts. We shouldn't be penalizing them with this 2 week's feature
> > freeze schedule
> >
> > Thanks,
> > RamG
> >
> >> -----Original Message-----
> >> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called
> >> out in earlier mail the feature proposal date was not called out for
> >> 4.4 and as such giving little extra room seems reasonable.
> >>
> >> Animesh
> >>
> >>> -----Original Message-----
> >>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
> >>> been very realistic for us yet.
> >>>
> >>> The main issue I encounter is our month-long RC cycle where I spend
> >>> a bunch of time validating the RC and (during that timeframe) less
> >>> time developing for the next release as I had initially planned.
> >>>
> >>> Perhaps instead of extending the cycle we could consider ways to
> >>> actually meet the schedule on a consistent basis. That would be
> >>> fine, as
> >> well.
> >>>
> >>>
> >>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
> >>> wrote:
> >>>
> >>>> -1 on postponing the feature freeze. We are having this discussion
> >>>> after every release, however we agreed to do a 4 month cycle so
> >>>> let's stick
> >>> to it.
> >>>>
> >>>> If there are important features that are currently being developed
> >>>> but might not make this cut-off date we should discuss that
> >>>> separately, but as a point of principle lets stick to the release
> >>>> schedule as
> >> proposed.
> >>>>
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Hugo
> >>>>
> >>>>
> >>>> On 26 feb. 2014, at 15:23, Tracy Phillips
> >>>> <tr...@weberize.com>
> >>>> wrote:
> >>>>
> >>>>> +1 to Daan.
> >>>>>
> >>>>> Tracy Phillips
> >>>>> Weberize, Inc.
> >>>>>
> >>>>>
> >>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> >>>>> <daan.hoogland@gmail.com
> >>>>> wrote:
> >>>>>
> >>>>>> -1 for postponing the feature freeze. It will amount to more
> >>>>>> features in the release. I'd rather shorten the cycle and do more
> >>>>>> releases then to pack more bugs in a single go.
> >>>>>>
> >>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
> >>> wrote:
> >>>>>>> +1
> >>>>>>>
> >>>>>>>
> >>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> >>>>>> Abhinandan.Prateek@citrix.com
> >>>>>>>> :
> >>>>>>>
> >>>>>>>> +1 for 4.4 feature freeze on 3/28.
> >>>>>>>>
> >>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> >>>>>>>> <sa...@citrix.com> wrote:
> >>>>>>>>
> >>>>>>>>>> -----Original Message-----
> >>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Sateesh
> >>>>>>>>>
> >>>>>>>>>> I also agree we should discuss 4+ month development cycles
> >> again.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> >>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> I will start a separate discussion on 4 month cycle or
> >>>>>>>>>>> longer, but wanted to call out one more important date.
> >>>>>>>>>>>
> >>>>>>>>>>> We have a last day for feature proposal date which is
> >>>>>>>>>>> typically a month before feature freeze date. If following
> >>>>>>>>>>> 4.3 schedule + 4
> >>>>>> month
> >>>>>>>>>>> it would have been 2/14 and we are already past that. Since
> >>>>>>>>>>> it was
> >>>>>> not
> >>>>>>>>>>> announced for
> >>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
> >>>>>>>>>>> proposal
> >>>>>> open
> >>>>>>>>>>> for another week and push all the dates out by 2 weeks to
> >>>>>>>>>>> give
> >>>>>> folks
> >>>>>>>>>>> opportunity to finish up their features for new proposals
> >>>>>>>>>>> that are
> >>>>>> yet
> >>>>>>>>>>> to come out.
> >>>>>>>>>>>
> >>>>>>>>>>> To be clear that would mean pushing out feature freeze to
> >>>>>>>>>>> 3/28 from
> >>>>>>>>>>> 3/14 and all the other dates likewise.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks
> >>>>>>>>>>> Animesh
> >>>>>>>>>>>
> >>>>>>>>>>>> -----Original Message-----
> >>>>>>>>>>>> From: Animesh Chaturvedi
> >>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> >>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> >>>>>>>>>>>> To: dev@cloudstack.apache.org
> >>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
> >>>>>>>>>>>>
> >>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
> >>>>>>>>>>>> discuss if
> >>>>>> we
> >>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
> >>>>>>>>>>>> months. I
> >>>>>> was
> >>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
> >>>>>>>>>>>>
> >>>>>>>>>>>>> -----Original Message-----
> >>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
> Hugo
> >>>>>>>>>>>>> Trippaers
> >>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> >>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
> >>>>>>>>>>>>> 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.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
> >>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
> >>>>>>>>>>>>> personal
> >>>>>> life
> >>>>>>>>>>>>> into
> >>>>>>>>>>> account ;-) ):
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Feature Freeze: March 14, 2014
> >>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
> >>>>>> 18,
> >>>>>>>>>> 2014
> >>>>>>>>>>>>> (direct access for committers)
> >>>>>>>>>>>>> Stability Fixes only: April 19, 2014 till
> >>>>>>>>>>> release (cherry picks
> >>>>>>>>>>>>> by RM only)
> >>>>>>>>>>>>> First RC: May 9, 2014
> >>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hugo
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> >>>>>>>>>>>>> <su...@citrix.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> >>>>>>>>>>>>>> 0540<tel:+442036030540>
> >>>>>> |
> >>>>>>>>>> M:
> >>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden,
> London,
> >>>>>>>>>>>>>> WC2N
> >>>>>> 4HS
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> >>>>>>>>>>>>>> Our CloudStack Infrastructure
> >>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> >>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> >>>>>> CloudStack
> >>>>>>>>>>>>> Environments.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
> >>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
> >>>>>>>>>>>>> training/>
> >>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
> >>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> >>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> This email and any attachments to it may be confidential
> >>>>>>>>>>>>>> and
> >>>>>> are
> >>>>>>>>>>>>>> intended
> >>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
> >>>>>> Any
> >>>>>>>>>>>>> views or opinions expressed are solely those of the author
> >>>>>>>>>>>>> and
> >>>>>> do
> >>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
> >>>>>>>>>>>>> related companies. If you are not the intended recipient
> >>>>>>>>>>>>> of this email, you must neither take any action based upon
> >>>>>>>>>>>>> its contents, nor
> >>>>>> copy
> >>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
> >>>>>>>>>>>>> believe
> >>>>>> you
> >>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
> >>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
> >>>>>>>>>>>>> Services India LLP
> >>>>>> is a
> >>>>>>>>>>>>> company incorporated in India and is operated under
> >>>>>>>>>>>>> license
> >>>>>> from
> >>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> >>>>>>>>>>>>> company incorporated in Brasil and is operated under
> >>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
> >>>>>>>>>>> a
> >>>>>>>>>>>> registered trademark.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> *Mike Tutkowski*
> >>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> >>>>>>>>>> e: mike.tutkowski@solidfire.com
> >>>>>>>>>> o: 303.746.7302
> >>>>>>>>>> Advancing the way the world uses the
> >>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
> >>>>>>>>>> *(tm)*
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Daan
> >>>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>> *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkowski@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the
> >>> cloud<http://solidfire.com/solution/overview/?video=play>
> >>> *(tm)*
>
> Stratosec - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella
Re: 4.4 Feature Freeze
Posted by Marcus <sh...@gmail.com>.
Christopher, 4.1 was also delayed several months.
I'm also -1 on moving it, even though I'm not sure it will have much
impact. The key is in how we look at merge requests, and whether or
not things are even being done in branches or directly to master.
People are going to rush to stuff things in, regardless of the date.
If we don't move the date, we may even have lower quality code
submitted, just to get in. The thing that tips it for me is that we'll
have fewer features if we don't move the date. Also, I have a few
things myself that I've been working hard on to make the current date,
I don't think there should be an expectation going forward that the
date will just be pushed out, we should expect to meet those targets.
On Tue, Mar 4, 2014 at 9:29 AM, SuichII, Christopher
<Ch...@netapp.com> wrote:
> I'd be a fan of using 4.4 as a learning process for the community and an attempt to meet our proposed schedule. While I can appreciate the desire to get features into 4.4, there appears to be a significant backlog on JIRA and we've now had two consecutive versions (I'm not sure about 4.1) not meet their original release dates. We could use this time to work through the backlog and continue to improve our automation, test coverage and release process.
>
> --
> Chris Suich
> chris.suich@netapp.com
> NetApp Software Engineer
> Data Center Platforms - Cloud Solutions
> Citrix, Cisco & Red Hat
>
> On Mar 4, 2014, at 11:07 AM, Giles Sirett <gi...@shapeblue.com> wrote:
>
>> I'm coming in late to this debate, but have been watching closely.
>>
>> I am -1 on moving the freeze date
>> To put it more generally: I am -1 on ANYTHING that will have a potential impact on quality right now.
>> Whatever anybody says, I can bet that a shorter code freeze (even temporary) will have an impact on quality
>>
>> I am not a developer, but I see the downstream fallout of features being rushed in with the users of this software
>>
>> From my experience in the field: customers (users) do not rush to upgrade ACS anyway. Most of the orgs I know would accept a 3 month delay if they knew the quality was going to be, on average, higher (obviously, we all have that one feature that *we* want and think is low risk - but I'm generalising here)
>>
>> We've already got a pretty frequent release cycle . This will be frustrating for some of you guys I know (understand many people working like crazy to build new features) , but we all know the release cycle, we all know the code freeze window.
>>
>> I fully understand that 4.3 has been a pain to get out of the door and is the root cause of this situation. If we have less time to test 4.4, we run the risk of having the same happen again.
>>
>> 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.Sirett@shapeblue.com
>>
>>
>>
>>
>> -----Original Message-----
>> From: Sebastien Goasguen [mailto:runseb@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 <su...@citrix.com> 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 state as of now. There are only 2 weeks left to close on coding and developers would rush to check in the code. This only results in poor quality code.
>>
>> Why the rush ? if it's not done, it's not done and will get in later. Why rush to merge code that you know will have bugs ?
>>
>>>
>>> Thanks
>>> /sudha
>>>
>>> -----Original Message-----
>>> From: John Kinsella [mailto:jlk@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 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.
>>>
>>> What we have a stronger need for than 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 feature freeze date.
>>>
>>> John
>>>
>>> On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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 efforts. We shouldn't be penalizing them with this 2
>>>> week's feature freeze schedule
>>>>
>>>> Thanks,
>>>> RamG
>>>>
>>>>> -----Original Message-----
>>>>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called
>>>>> out in earlier mail the feature proposal date was not called out for
>>>>> 4.4 and as such giving little extra room seems reasonable.
>>>>>
>>>>> Animesh
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
>>>>>> been very realistic for us yet.
>>>>>>
>>>>>> The main issue I encounter is our month-long RC cycle where I spend
>>>>>> a bunch of time validating the RC and (during that timeframe) less
>>>>>> time developing for the next release as I had initially planned.
>>>>>>
>>>>>> Perhaps instead of extending the cycle we could consider ways to
>>>>>> actually meet the schedule on a consistent basis. That would be
>>>>>> fine, as
>>>>> well.
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
>>>>>> wrote:
>>>>>>
>>>>>>> -1 on postponing the feature freeze. We are having this discussion
>>>>>>> after every release, however we agreed to do a 4 month cycle so
>>>>>>> let's stick
>>>>>> to it.
>>>>>>>
>>>>>>> If there are important features that are currently being developed
>>>>>>> but might not make this cut-off date we should discuss that
>>>>>>> separately, but as a point of principle lets stick to the release
>>>>>>> schedule as
>>>>> proposed.
>>>>>>>
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Hugo
>>>>>>>
>>>>>>>
>>>>>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>>>>>>> <tr...@weberize.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 to Daan.
>>>>>>>>
>>>>>>>> Tracy Phillips
>>>>>>>> Weberize, Inc.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>>>>>>>> <daan.hoogland@gmail.com
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> -1 for postponing the feature freeze. It will amount to more
>>>>>>>>> features in the release. I'd rather shorten the cycle and do
>>>>>>>>> more releases then to pack more bugs in a single go.
>>>>>>>>>
>>>>>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
>>>>>> wrote:
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>>>>>>>>> Abhinandan.Prateek@citrix.com
>>>>>>>>>>> :
>>>>>>>>>>
>>>>>>>>>>> +1 for 4.4 feature freeze on 3/28.
>>>>>>>>>>>
>>>>>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>>>>>>>>>>> <sa...@citrix.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Sateesh
>>>>>>>>>>>>
>>>>>>>>>>>>> I also agree we should discuss 4+ month development cycles
>>>>> again.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>>>>>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>>>>>>>>>>>>>> longer, but wanted to call out one more important date.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We have a last day for feature proposal date which is
>>>>>>>>>>>>>> typically a month before feature freeze date. If following
>>>>>>>>>>>>>> 4.3 schedule + 4
>>>>>>>>> month
>>>>>>>>>>>>>> it would have been 2/14 and we are already past that. Since
>>>>>>>>>>>>>> it was
>>>>>>>>> not
>>>>>>>>>>>>>> announced for
>>>>>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>>>>>>>>>>>>>> proposal
>>>>>>>>> open
>>>>>>>>>>>>>> for another week and push all the dates out by 2 weeks to
>>>>>>>>>>>>>> give
>>>>>>>>> folks
>>>>>>>>>>>>>> opportunity to finish up their features for new proposals
>>>>>>>>>>>>>> that are
>>>>>>>>> yet
>>>>>>>>>>>>>> to come out.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>>>>>>>>>>>>>> 3/28 from
>>>>>>>>>>>>>> 3/14 and all the other dates likewise.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>> Animesh
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>>> From: Animesh Chaturvedi
>>>>>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>>>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>>>>>>>>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>>>>>>>>>>>>>>> discuss if
>>>>>>>>> we
>>>>>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>>>>>>>>>>>>>>> months. I
>>>>>>>>> was
>>>>>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
>>>>>>>>>>>>>>>> Hugo Trippaers
>>>>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>>>>>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>>>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
>>>>>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
>>>>>>>>>>>>>>>> personal
>>>>>>>>> life
>>>>>>>>>>>>>>>> into
>>>>>>>>>>>>>> account ;-) ):
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Feature Freeze: March 14, 2014
>>>>>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>>>>>>>>> 18,
>>>>>>>>>>>>> 2014
>>>>>>>>>>>>>>>> (direct access for committers)
>>>>>>>>>>>>>>>> Stability Fixes only: April 19, 2014 till
>>>>>>>>>>>>>> release (cherry picks
>>>>>>>>>>>>>>>> by RM only)
>>>>>>>>>>>>>>>> First RC: May 9, 2014
>>>>>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hugo
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>>>>>>>>>>>>>>>> <su...@citrix.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>>>>>>>>>>>>>>>>> 0540<tel:+442036030540>
>>>>>>>>> |
>>>>>>>>>>>>> M:
>>>>>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
>>>>>>>>>>>>>>>>> WC2N
>>>>>>>>> 4HS
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>>>>>>>>>>>>>>>>> Our CloudStack Infrastructure
>>>>>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>>>>>>>>> CloudStack
>>>>>>>>>>>>>>>> Environments.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>>>>>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>>>>> training/>
>>>>>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>>>>>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>>>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>>>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>>>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>>>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This email and any attachments to it may be confidential
>>>>>>>>>>>>>>>>> and
>>>>>>>>> are
>>>>>>>>>>>>>>>>> intended
>>>>>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
>>>>>>>>> Any
>>>>>>>>>>>>>>>> views or opinions expressed are solely those of the
>>>>>>>>>>>>>>>> author and
>>>>>>>>> do
>>>>>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>>>>>>>>>>>>>>>> related companies. If you are not the intended recipient
>>>>>>>>>>>>>>>> of this email, you must neither take any action based
>>>>>>>>>>>>>>>> upon its contents, nor
>>>>>>>>> copy
>>>>>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>>>>>>>>>>>>>>>> believe
>>>>>>>>> you
>>>>>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>>>>>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>>>>>>>>>>>>>>>> Services India LLP
>>>>>>>>> is a
>>>>>>>>>>>>>>>> company incorporated in India and is operated under
>>>>>>>>>>>>>>>> license
>>>>>>>>> from
>>>>>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>>>>>>>>>>>>>>>> company incorporated in Brasil and is operated under
>>>>>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>>>>>>>>>>>>>> a
>>>>>>>>>>>>>>> registered trademark.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> *Mike Tutkowski*
>>>>>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>>>>>>>>>>> e: mike.tutkowski@solidfire.com
>>>>>>>>>>>>> o: 303.746.7302
>>>>>>>>>>>>> Advancing the way the world uses the
>>>>>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>>>>>>>>>>> *(tm)*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Daan
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Mike Tutkowski*
>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>>>> e: mike.tutkowski@solidfire.com
>>>>>> o: 303.746.7302
>>>>>> Advancing the way the world uses the
>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>>>> *(tm)*
>>>
>>> Stratosec - Compliance as a Service
>>> o: 415.315.9385
>>> @johnlkinsella
>>>
>>
>> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>
Re: 4.4 Feature Freeze
Posted by "SuichII, Christopher" <Ch...@netapp.com>.
I’d be a fan of using 4.4 as a learning process for the community and an attempt to meet our proposed schedule. While I can appreciate the desire to get features into 4.4, there appears to be a significant backlog on JIRA and we’ve now had two consecutive versions (I’m not sure about 4.1) not meet their original release dates. We could use this time to work through the backlog and continue to improve our automation, test coverage and release process.
--
Chris Suich
chris.suich@netapp.com
NetApp Software Engineer
Data Center Platforms – Cloud Solutions
Citrix, Cisco & Red Hat
On Mar 4, 2014, at 11:07 AM, Giles Sirett <gi...@shapeblue.com> wrote:
> I'm coming in late to this debate, but have been watching closely.
>
> I am -1 on moving the freeze date
> To put it more generally: I am -1 on ANYTHING that will have a potential impact on quality right now.
> Whatever anybody says, I can bet that a shorter code freeze (even temporary) will have an impact on quality
>
> I am not a developer, but I see the downstream fallout of features being rushed in with the users of this software
>
> From my experience in the field: customers (users) do not rush to upgrade ACS anyway. Most of the orgs I know would accept a 3 month delay if they knew the quality was going to be, on average, higher (obviously, we all have that one feature that *we* want and think is low risk - but I'm generalising here)
>
> We've already got a pretty frequent release cycle . This will be frustrating for some of you guys I know (understand many people working like crazy to build new features) , but we all know the release cycle, we all know the code freeze window.
>
> I fully understand that 4.3 has been a pain to get out of the door and is the root cause of this situation. If we have less time to test 4.4, we run the risk of having the same happen again.
>
> 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.Sirett@shapeblue.com
>
>
>
>
> -----Original Message-----
> From: Sebastien Goasguen [mailto:runseb@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 <su...@citrix.com> 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 state as of now. There are only 2 weeks left to close on coding and developers would rush to check in the code. This only results in poor quality code.
>
> Why the rush ? if it's not done, it's not done and will get in later. Why rush to merge code that you know will have bugs ?
>
>>
>> Thanks
>> /sudha
>>
>> -----Original Message-----
>> From: John Kinsella [mailto:jlk@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 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.
>>
>> What we have a stronger need for than 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 feature freeze date.
>>
>> John
>>
>> On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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 efforts. We shouldn't be penalizing them with this 2
>>> week's feature freeze schedule
>>>
>>> Thanks,
>>> RamG
>>>
>>>> -----Original Message-----
>>>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called
>>>> out in earlier mail the feature proposal date was not called out for
>>>> 4.4 and as such giving little extra room seems reasonable.
>>>>
>>>> Animesh
>>>>
>>>>> -----Original Message-----
>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
>>>>> been very realistic for us yet.
>>>>>
>>>>> The main issue I encounter is our month-long RC cycle where I spend
>>>>> a bunch of time validating the RC and (during that timeframe) less
>>>>> time developing for the next release as I had initially planned.
>>>>>
>>>>> Perhaps instead of extending the cycle we could consider ways to
>>>>> actually meet the schedule on a consistent basis. That would be
>>>>> fine, as
>>>> well.
>>>>>
>>>>>
>>>>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
>>>>> wrote:
>>>>>
>>>>>> -1 on postponing the feature freeze. We are having this discussion
>>>>>> after every release, however we agreed to do a 4 month cycle so
>>>>>> let's stick
>>>>> to it.
>>>>>>
>>>>>> If there are important features that are currently being developed
>>>>>> but might not make this cut-off date we should discuss that
>>>>>> separately, but as a point of principle lets stick to the release
>>>>>> schedule as
>>>> proposed.
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Hugo
>>>>>>
>>>>>>
>>>>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>>>>>> <tr...@weberize.com>
>>>>>> wrote:
>>>>>>
>>>>>>> +1 to Daan.
>>>>>>>
>>>>>>> Tracy Phillips
>>>>>>> Weberize, Inc.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>>>>>>> <daan.hoogland@gmail.com
>>>>>>> wrote:
>>>>>>>
>>>>>>>> -1 for postponing the feature freeze. It will amount to more
>>>>>>>> features in the release. I'd rather shorten the cycle and do
>>>>>>>> more releases then to pack more bugs in a single go.
>>>>>>>>
>>>>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
>>>>> wrote:
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>>>>>>>> Abhinandan.Prateek@citrix.com
>>>>>>>>>> :
>>>>>>>>>
>>>>>>>>>> +1 for 4.4 feature freeze on 3/28.
>>>>>>>>>>
>>>>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>>>>>>>>>> <sa...@citrix.com> wrote:
>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Sateesh
>>>>>>>>>>>
>>>>>>>>>>>> I also agree we should discuss 4+ month development cycles
>>>> again.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>>>>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>>>>>>>>>>>>> longer, but wanted to call out one more important date.
>>>>>>>>>>>>>
>>>>>>>>>>>>> We have a last day for feature proposal date which is
>>>>>>>>>>>>> typically a month before feature freeze date. If following
>>>>>>>>>>>>> 4.3 schedule + 4
>>>>>>>> month
>>>>>>>>>>>>> it would have been 2/14 and we are already past that. Since
>>>>>>>>>>>>> it was
>>>>>>>> not
>>>>>>>>>>>>> announced for
>>>>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>>>>>>>>>>>>> proposal
>>>>>>>> open
>>>>>>>>>>>>> for another week and push all the dates out by 2 weeks to
>>>>>>>>>>>>> give
>>>>>>>> folks
>>>>>>>>>>>>> opportunity to finish up their features for new proposals
>>>>>>>>>>>>> that are
>>>>>>>> yet
>>>>>>>>>>>>> to come out.
>>>>>>>>>>>>>
>>>>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>>>>>>>>>>>>> 3/28 from
>>>>>>>>>>>>> 3/14 and all the other dates likewise.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>> Animesh
>>>>>>>>>>>>>
>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>> From: Animesh Chaturvedi
>>>>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>>>>>>>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>>>>>>>>>>>>>> discuss if
>>>>>>>> we
>>>>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>>>>>>>>>>>>>> months. I
>>>>>>>> was
>>>>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
>>>>>>>>>>>>>>> Hugo Trippaers
>>>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>>>>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
>>>>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
>>>>>>>>>>>>>>> personal
>>>>>>>> life
>>>>>>>>>>>>>>> into
>>>>>>>>>>>>> account ;-) ):
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Feature Freeze: March 14, 2014
>>>>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>>>>>>>> 18,
>>>>>>>>>>>> 2014
>>>>>>>>>>>>>>> (direct access for committers)
>>>>>>>>>>>>>>> Stability Fixes only: April 19, 2014 till
>>>>>>>>>>>>> release (cherry picks
>>>>>>>>>>>>>>> by RM only)
>>>>>>>>>>>>>>> First RC: May 9, 2014
>>>>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hugo
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>>>>>>>>>>>>>>> <su...@citrix.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>>>>>>>>>>>>>>>> 0540<tel:+442036030540>
>>>>>>>> |
>>>>>>>>>>>> M:
>>>>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
>>>>>>>>>>>>>>>> WC2N
>>>>>>>> 4HS
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>>>>>>>>>>>>>>>> Our CloudStack Infrastructure
>>>>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>>>>>>>> CloudStack
>>>>>>>>>>>>>>> Environments.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>>>>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>>>> training/>
>>>>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>>>>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> This email and any attachments to it may be confidential
>>>>>>>>>>>>>>>> and
>>>>>>>> are
>>>>>>>>>>>>>>>> intended
>>>>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
>>>>>>>> Any
>>>>>>>>>>>>>>> views or opinions expressed are solely those of the
>>>>>>>>>>>>>>> author and
>>>>>>>> do
>>>>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>>>>>>>>>>>>>>> related companies. If you are not the intended recipient
>>>>>>>>>>>>>>> of this email, you must neither take any action based
>>>>>>>>>>>>>>> upon its contents, nor
>>>>>>>> copy
>>>>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>>>>>>>>>>>>>>> believe
>>>>>>>> you
>>>>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>>>>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>>>>>>>>>>>>>>> Services India LLP
>>>>>>>> is a
>>>>>>>>>>>>>>> company incorporated in India and is operated under
>>>>>>>>>>>>>>> license
>>>>>>>> from
>>>>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>>>>>>>>>>>>>>> company incorporated in Brasil and is operated under
>>>>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>>>>>>>>>>>>> a
>>>>>>>>>>>>>> registered trademark.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> *Mike Tutkowski*
>>>>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>>>>>>>>>> e: mike.tutkowski@solidfire.com
>>>>>>>>>>>> o: 303.746.7302
>>>>>>>>>>>> Advancing the way the world uses the
>>>>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>>>>>>>>>> *(tm)*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Daan
>>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Mike Tutkowski*
>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>>> e: mike.tutkowski@solidfire.com
>>>>> o: 303.746.7302
>>>>> Advancing the way the world uses the
>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>>> *(tm)*
>>
>> Stratosec - Compliance as a Service
>> o: 415.315.9385
>> @johnlkinsella
>>
>
> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: 4.4 Feature Freeze
Posted by Jayapal Reddy Uradi <ja...@citrix.com>.
Hi,
The below feature is proposed in dev list but somehow the fix version is not set correctly, update it now.
CLOUDSTACK-2692<https://issues.apache.org/jira/browse/CLOUDSTACK-2692> Add load balancing support for multiple ips to nic
Thanks,
Jayapal
On 04-Mar-2014, at 9:37 PM, Giles Sirett <gi...@shapeblue.com>>
wrote:
I'm coming in late to this debate, but have been watching closely.
I am -1 on moving the freeze date
To put it more generally: I am -1 on ANYTHING that will have a potential impact on quality right now.
Whatever anybody says, I can bet that a shorter code freeze (even temporary) will have an impact on quality
I am not a developer, but I see the downstream fallout of features being rushed in with the users of this software
>From my experience in the field: customers (users) do not rush to upgrade ACS anyway. Most of the orgs I know would accept a 3 month delay if they knew the quality was going to be, on average, higher (obviously, we all have that one feature that *we* want and think is low risk - but I'm generalising here)
We've already got a pretty frequent release cycle . This will be frustrating for some of you guys I know (understand many people working like crazy to build new features) , but we all know the release cycle, we all know the code freeze window.
I fully understand that 4.3 has been a pain to get out of the door and is the root cause of this situation. If we have less time to test 4.4, we run the risk of having the same happen again.
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.Sirett@shapeblue.com<ma...@shapeblue.com>
-----Original Message-----
From: Sebastien Goasguen [mailto:runseb@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 <su...@citrix.com> 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 state as of now. There are only 2 weeks left to close on coding and developers would rush to check in the code. This only results in poor quality code.
Why the rush ? if it's not done, it's not done and will get in later. Why rush to merge code that you know will have bugs ?
Thanks
/sudha
-----Original Message-----
From: John Kinsella [mailto:jlk@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 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.
What we have a stronger need for than 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 feature freeze date.
John
On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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 efforts. We shouldn't be penalizing them with this 2
week's feature freeze schedule
Thanks,
RamG
-----Original Message-----
From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called
out in earlier mail the feature proposal date was not called out for
4.4 and as such giving little extra room seems reasonable.
Animesh
-----Original Message-----
From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
been very realistic for us yet.
The main issue I encounter is our month-long RC cycle where I spend
a bunch of time validating the RC and (during that timeframe) less
time developing for the next release as I had initially planned.
Perhaps instead of extending the cycle we could consider ways to
actually meet the schedule on a consistent basis. That would be
fine, as
well.
On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
wrote:
-1 on postponing the feature freeze. We are having this discussion
after every release, however we agreed to do a 4 month cycle so
let's stick
to it.
If there are important features that are currently being developed
but might not make this cut-off date we should discuss that
separately, but as a point of principle lets stick to the release
schedule as
proposed.
Cheers,
Hugo
On 26 feb. 2014, at 15:23, Tracy Phillips
<tr...@weberize.com>
wrote:
+1 to Daan.
Tracy Phillips
Weberize, Inc.
On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
<daan.hoogland@gmail.com
wrote:
-1 for postponing the feature freeze. It will amount to more
features in the release. I'd rather shorten the cycle and do
more releases then to pack more bugs in a single go.
On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
wrote:
+1
2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
Abhinandan.Prateek@citrix.com
:
+1 for 4.4 feature freeze on 3/28.
On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
<sa...@citrix.com> wrote:
-----Original Message-----
From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
Regards,
Sateesh
I also agree we should discuss 4+ month development cycles
again.
On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
animesh.chaturvedi@citrix.com> wrote:
I will start a separate discussion on 4 month cycle or
longer, but wanted to call out one more important date.
We have a last day for feature proposal date which is
typically a month before feature freeze date. If following
4.3 schedule + 4
month
it would have been 2/14 and we are already past that. Since
it was
not
announced for
4.4 release yet my suggestion would be to keep feature
proposal
open
for another week and push all the dates out by 2 weeks to
give
folks
opportunity to finish up their features for new proposals
that are
yet
to come out.
To be clear that would mean pushing out feature freeze to
3/28 from
3/14 and all the other dates likewise.
Thanks
Animesh
-----Original Message-----
From: Animesh Chaturvedi
[mailto:animesh.chaturvedi@citrix.com]
Sent: Tuesday, February 25, 2014 1:05 PM
To: dev@cloudstack.apache.org
Subject: RE: 4.4 Feature Freeze
With the experience of 4.2 and 4.3 I think we should
discuss if
we
can realistically achieve 4 month cycle our RCs take 2
months. I
was
going to open up the discussion after 4.3 is shipped though.
-----Original Message-----
From: Trippie [mailto:trippie@gmail.com] On Behalf Of
Hugo Trippaers
Sent: Tuesday, February 25, 2014 8:50 AM
To: <de...@cloudstack.apache.org>
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.
So the proposed release schedule for 4.4 would look like
this (dates slightly modified to take efficiency and RM's
personal
life
into
account ;-) ):
Feature Freeze: March 14, 2014
Testing/Bug Fixes: March 15, 2014 till April
18,
2014
(direct access for committers)
Stability Fixes only: April 19, 2014 till
release (cherry picks
by RM only)
First RC: May 9, 2014
Optimistic Release Date: May 19, 2014
Cheers,
Hugo
On 25 feb. 2014, at 16:35, Sudha Ponnaganti
<su...@citrix.com>
wrote:
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.hitchins@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 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 523 587 | S: +44 20 3603
0540<tel:+442036030540>
|
M:
+44<tel:+447968161581> 7788 423 969
ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
WC2N
4HS
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure
Support<http://shapeblue.com/cloudstack-
infrastructure-support/> offers the best 24/7 SLA for
CloudStack
Environments.
Apache CloudStack Bootcamp training courses
**NEW!** CloudStack 4.2.1
training<http://shapeblue.com/cloudstack-
training/>
18th-19th February 2014, Brazil.
Classroom<http://shapeblue.com/cloudstack-training/>
17th-23rd March 2014, Region A. Instructor led, On-
line<http://shapeblue.com/cloudstack-training/>
24th-28th March 2014, Region B. Instructor led, On-
line<http://shapeblue.com/cloudstack-training/>
16th-20th June 2014, Region A. Instructor led, On-
line<http://shapeblue.com/cloudstack-training/>
23rd-27th June 2014, Region B. Instructor led, On-
line<http://shapeblue.com/cloudstack-training/>
This email and any attachments to it may be confidential
and
are
intended
solely for the use of the individual to whom it is addressed.
Any
views or opinions expressed are solely those of the
author and
do
not necessarily represent those of Shape Blue Ltd or
related companies. If you are not the intended recipient
of this email, you must neither take any action based
upon its contents, nor
copy
or show it to anyone. Please contact the sender if you
believe
you
have received this email in error. Shape Blue Ltd is a
company incorporated in England & Wales. ShapeBlue
Services India LLP
is a
company incorporated in India and is operated under
license
from
Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
company incorporated in Brasil and is operated under
license from Shape Blue Ltd. ShapeBlue is
a
registered trademark.
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
--
Daan
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Stratosec - Compliance as a Service
o: 415.315.9385
@johnlkinsella
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
RE: 4.4 Feature Freeze
Posted by Giles Sirett <gi...@shapeblue.com>.
I'm coming in late to this debate, but have been watching closely.
I am -1 on moving the freeze date
To put it more generally: I am -1 on ANYTHING that will have a potential impact on quality right now.
Whatever anybody says, I can bet that a shorter code freeze (even temporary) will have an impact on quality
I am not a developer, but I see the downstream fallout of features being rushed in with the users of this software
>From my experience in the field: customers (users) do not rush to upgrade ACS anyway. Most of the orgs I know would accept a 3 month delay if they knew the quality was going to be, on average, higher (obviously, we all have that one feature that *we* want and think is low risk - but I'm generalising here)
We've already got a pretty frequent release cycle . This will be frustrating for some of you guys I know (understand many people working like crazy to build new features) , but we all know the release cycle, we all know the code freeze window.
I fully understand that 4.3 has been a pain to get out of the door and is the root cause of this situation. If we have less time to test 4.4, we run the risk of having the same happen again.
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.Sirett@shapeblue.com
-----Original Message-----
From: Sebastien Goasguen [mailto:runseb@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 <su...@citrix.com> 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 state as of now. There are only 2 weeks left to close on coding and developers would rush to check in the code. This only results in poor quality code.
Why the rush ? if it's not done, it's not done and will get in later. Why rush to merge code that you know will have bugs ?
>
> Thanks
> /sudha
>
> -----Original Message-----
> From: John Kinsella [mailto:jlk@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 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.
>
> What we have a stronger need for than 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 feature freeze date.
>
> John
>
> On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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 efforts. We shouldn't be penalizing them with this 2
>> week's feature freeze schedule
>>
>> Thanks,
>> RamG
>>
>>> -----Original Message-----
>>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called
>>> out in earlier mail the feature proposal date was not called out for
>>> 4.4 and as such giving little extra room seems reasonable.
>>>
>>> Animesh
>>>
>>>> -----Original Message-----
>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
>>>> been very realistic for us yet.
>>>>
>>>> The main issue I encounter is our month-long RC cycle where I spend
>>>> a bunch of time validating the RC and (during that timeframe) less
>>>> time developing for the next release as I had initially planned.
>>>>
>>>> Perhaps instead of extending the cycle we could consider ways to
>>>> actually meet the schedule on a consistent basis. That would be
>>>> fine, as
>>> well.
>>>>
>>>>
>>>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
>>>> wrote:
>>>>
>>>>> -1 on postponing the feature freeze. We are having this discussion
>>>>> after every release, however we agreed to do a 4 month cycle so
>>>>> let's stick
>>>> to it.
>>>>>
>>>>> If there are important features that are currently being developed
>>>>> but might not make this cut-off date we should discuss that
>>>>> separately, but as a point of principle lets stick to the release
>>>>> schedule as
>>> proposed.
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Hugo
>>>>>
>>>>>
>>>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>>>>> <tr...@weberize.com>
>>>>> wrote:
>>>>>
>>>>>> +1 to Daan.
>>>>>>
>>>>>> Tracy Phillips
>>>>>> Weberize, Inc.
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>>>>>> <daan.hoogland@gmail.com
>>>>>> wrote:
>>>>>>
>>>>>>> -1 for postponing the feature freeze. It will amount to more
>>>>>>> features in the release. I'd rather shorten the cycle and do
>>>>>>> more releases then to pack more bugs in a single go.
>>>>>>>
>>>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
>>>> wrote:
>>>>>>>> +1
>>>>>>>>
>>>>>>>>
>>>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>>>>>>> Abhinandan.Prateek@citrix.com
>>>>>>>>> :
>>>>>>>>
>>>>>>>>> +1 for 4.4 feature freeze on 3/28.
>>>>>>>>>
>>>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>>>>>>>>> <sa...@citrix.com> wrote:
>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Sateesh
>>>>>>>>>>
>>>>>>>>>>> I also agree we should discuss 4+ month development cycles
>>> again.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>>>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>>>>>>>>>>>> longer, but wanted to call out one more important date.
>>>>>>>>>>>>
>>>>>>>>>>>> We have a last day for feature proposal date which is
>>>>>>>>>>>> typically a month before feature freeze date. If following
>>>>>>>>>>>> 4.3 schedule + 4
>>>>>>> month
>>>>>>>>>>>> it would have been 2/14 and we are already past that. Since
>>>>>>>>>>>> it was
>>>>>>> not
>>>>>>>>>>>> announced for
>>>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>>>>>>>>>>>> proposal
>>>>>>> open
>>>>>>>>>>>> for another week and push all the dates out by 2 weeks to
>>>>>>>>>>>> give
>>>>>>> folks
>>>>>>>>>>>> opportunity to finish up their features for new proposals
>>>>>>>>>>>> that are
>>>>>>> yet
>>>>>>>>>>>> to come out.
>>>>>>>>>>>>
>>>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>>>>>>>>>>>> 3/28 from
>>>>>>>>>>>> 3/14 and all the other dates likewise.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>> Animesh
>>>>>>>>>>>>
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: Animesh Chaturvedi
>>>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>>>>>>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>>>>>>>>>>>>>
>>>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>>>>>>>>>>>>> discuss if
>>>>>>> we
>>>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>>>>>>>>>>>>> months. I
>>>>>>> was
>>>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of
>>>>>>>>>>>>>> Hugo Trippaers
>>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>>>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
>>>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
>>>>>>>>>>>>>> personal
>>>>>>> life
>>>>>>>>>>>>>> into
>>>>>>>>>>>> account ;-) ):
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Feature Freeze: March 14, 2014
>>>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>>>>>>> 18,
>>>>>>>>>>> 2014
>>>>>>>>>>>>>> (direct access for committers)
>>>>>>>>>>>>>> Stability Fixes only: April 19, 2014 till
>>>>>>>>>>>> release (cherry picks
>>>>>>>>>>>>>> by RM only)
>>>>>>>>>>>>>> First RC: May 9, 2014
>>>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hugo
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>>>>>>>>>>>>>> <su...@citrix.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>>>>>>>>>>>>>>> 0540<tel:+442036030540>
>>>>>>> |
>>>>>>>>>>> M:
>>>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
>>>>>>>>>>>>>>> WC2N
>>>>>>> 4HS
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>>>>>>>>>>>>>>> Our CloudStack Infrastructure
>>>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>>>>>>> CloudStack
>>>>>>>>>>>>>> Environments.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>>>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>>> training/>
>>>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>>>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This email and any attachments to it may be confidential
>>>>>>>>>>>>>>> and
>>>>>>> are
>>>>>>>>>>>>>>> intended
>>>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
>>>>>>> Any
>>>>>>>>>>>>>> views or opinions expressed are solely those of the
>>>>>>>>>>>>>> author and
>>>>>>> do
>>>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>>>>>>>>>>>>>> related companies. If you are not the intended recipient
>>>>>>>>>>>>>> of this email, you must neither take any action based
>>>>>>>>>>>>>> upon its contents, nor
>>>>>>> copy
>>>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>>>>>>>>>>>>>> believe
>>>>>>> you
>>>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>>>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>>>>>>>>>>>>>> Services India LLP
>>>>>>> is a
>>>>>>>>>>>>>> company incorporated in India and is operated under
>>>>>>>>>>>>>> license
>>>>>>> from
>>>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>>>>>>>>>>>>>> company incorporated in Brasil and is operated under
>>>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>>>>>>>>>>>> a
>>>>>>>>>>>>> registered trademark.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> *Mike Tutkowski*
>>>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>>>>>>>>> e: mike.tutkowski@solidfire.com
>>>>>>>>>>> o: 303.746.7302
>>>>>>>>>>> Advancing the way the world uses the
>>>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>>>>>>>>> *(tm)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Daan
>>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Mike Tutkowski*
>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>> e: mike.tutkowski@solidfire.com
>>>> o: 303.746.7302
>>>> Advancing the way the world uses the
>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>> *(tm)*
>
> Stratosec - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella
>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: 4.4 Feature Freeze
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Feb 26, 2014, at 10:44 PM, Sudha Ponnaganti <su...@citrix.com> 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 state as of now. There are only 2 weeks left to close on coding and developers would rush to check in the code. This only results in poor quality code.
Why the rush ? if it's not done, it's not done and will get in later. Why rush to merge code that you know will have bugs ?
>
> Thanks
> /sudha
>
> -----Original Message-----
> From: John Kinsella [mailto:jlk@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 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.
>
> What we have a stronger need for than 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 feature freeze date.
>
> John
>
> On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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
>> efforts. We shouldn't be penalizing them with this 2 week's feature
>> freeze schedule
>>
>> Thanks,
>> RamG
>>
>>> -----Original Message-----
>>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called
>>> out in earlier mail the feature proposal date was not called out for
>>> 4.4 and as such giving little extra room seems reasonable.
>>>
>>> Animesh
>>>
>>>> -----Original Message-----
>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
>>>> been very realistic for us yet.
>>>>
>>>> The main issue I encounter is our month-long RC cycle where I spend
>>>> a bunch of time validating the RC and (during that timeframe) less
>>>> time developing for the next release as I had initially planned.
>>>>
>>>> Perhaps instead of extending the cycle we could consider ways to
>>>> actually meet the schedule on a consistent basis. That would be
>>>> fine, as
>>> well.
>>>>
>>>>
>>>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
>>>> wrote:
>>>>
>>>>> -1 on postponing the feature freeze. We are having this discussion
>>>>> after every release, however we agreed to do a 4 month cycle so
>>>>> let's stick
>>>> to it.
>>>>>
>>>>> If there are important features that are currently being developed
>>>>> but might not make this cut-off date we should discuss that
>>>>> separately, but as a point of principle lets stick to the release
>>>>> schedule as
>>> proposed.
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Hugo
>>>>>
>>>>>
>>>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>>>>> <tr...@weberize.com>
>>>>> wrote:
>>>>>
>>>>>> +1 to Daan.
>>>>>>
>>>>>> Tracy Phillips
>>>>>> Weberize, Inc.
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>>>>>> <daan.hoogland@gmail.com
>>>>>> wrote:
>>>>>>
>>>>>>> -1 for postponing the feature freeze. It will amount to more
>>>>>>> features in the release. I'd rather shorten the cycle and do more
>>>>>>> releases then to pack more bugs in a single go.
>>>>>>>
>>>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
>>>> wrote:
>>>>>>>> +1
>>>>>>>>
>>>>>>>>
>>>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>>>>>>> Abhinandan.Prateek@citrix.com
>>>>>>>>> :
>>>>>>>>
>>>>>>>>> +1 for 4.4 feature freeze on 3/28.
>>>>>>>>>
>>>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>>>>>>>>> <sa...@citrix.com> wrote:
>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Sateesh
>>>>>>>>>>
>>>>>>>>>>> I also agree we should discuss 4+ month development cycles
>>> again.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>>>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>>>>>>>>>>>> longer, but wanted to call out one more important date.
>>>>>>>>>>>>
>>>>>>>>>>>> We have a last day for feature proposal date which is
>>>>>>>>>>>> typically a month before feature freeze date. If following
>>>>>>>>>>>> 4.3 schedule + 4
>>>>>>> month
>>>>>>>>>>>> it would have been 2/14 and we are already past that. Since
>>>>>>>>>>>> it was
>>>>>>> not
>>>>>>>>>>>> announced for
>>>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>>>>>>>>>>>> proposal
>>>>>>> open
>>>>>>>>>>>> for another week and push all the dates out by 2 weeks to
>>>>>>>>>>>> give
>>>>>>> folks
>>>>>>>>>>>> opportunity to finish up their features for new proposals
>>>>>>>>>>>> that are
>>>>>>> yet
>>>>>>>>>>>> to come out.
>>>>>>>>>>>>
>>>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>>>>>>>>>>>> 3/28 from
>>>>>>>>>>>> 3/14 and all the other dates likewise.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>> Animesh
>>>>>>>>>>>>
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: Animesh Chaturvedi
>>>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>>>>>>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>>>>>>>>>>>>>
>>>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>>>>>>>>>>>>> discuss if
>>>>>>> we
>>>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>>>>>>>>>>>>> months. I
>>>>>>> was
>>>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
>>>>>>>>>>>>>> Trippaers
>>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>>>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
>>>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
>>>>>>>>>>>>>> personal
>>>>>>> life
>>>>>>>>>>>>>> into
>>>>>>>>>>>> account ;-) ):
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Feature Freeze: March 14, 2014
>>>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>>>>>>> 18,
>>>>>>>>>>> 2014
>>>>>>>>>>>>>> (direct access for committers)
>>>>>>>>>>>>>> Stability Fixes only: April 19, 2014 till
>>>>>>>>>>>> release (cherry picks
>>>>>>>>>>>>>> by RM only)
>>>>>>>>>>>>>> First RC: May 9, 2014
>>>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hugo
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>>>>>>>>>>>>>> <su...@citrix.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>>>>>>>>>>>>>>> 0540<tel:+442036030540>
>>>>>>> |
>>>>>>>>>>> M:
>>>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
>>>>>>>>>>>>>>> WC2N
>>>>>>> 4HS
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>>>>>>>>>>>>>>> Our CloudStack Infrastructure
>>>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>>>>>>> CloudStack
>>>>>>>>>>>>>> Environments.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>>>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>>> training/>
>>>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>>>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This email and any attachments to it may be confidential
>>>>>>>>>>>>>>> and
>>>>>>> are
>>>>>>>>>>>>>>> intended
>>>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
>>>>>>> Any
>>>>>>>>>>>>>> views or opinions expressed are solely those of the author
>>>>>>>>>>>>>> and
>>>>>>> do
>>>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>>>>>>>>>>>>>> related companies. If you are not the intended recipient
>>>>>>>>>>>>>> of this email, you must neither take any action based upon
>>>>>>>>>>>>>> its contents, nor
>>>>>>> copy
>>>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>>>>>>>>>>>>>> believe
>>>>>>> you
>>>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>>>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>>>>>>>>>>>>>> Services India LLP
>>>>>>> is a
>>>>>>>>>>>>>> company incorporated in India and is operated under
>>>>>>>>>>>>>> license
>>>>>>> from
>>>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>>>>>>>>>>>>>> company incorporated in Brasil and is operated under
>>>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>>>>>>>>>>>> a
>>>>>>>>>>>>> registered trademark.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> *Mike Tutkowski*
>>>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>>>>>>>>> e: mike.tutkowski@solidfire.com
>>>>>>>>>>> o: 303.746.7302
>>>>>>>>>>> Advancing the way the world uses the
>>>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>>>>>>>>> *(tm)*
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Daan
>>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Mike Tutkowski*
>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>> e: mike.tutkowski@solidfire.com
>>>> o: 303.746.7302
>>>> Advancing the way the world uses the
>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>> *(tm)*
>
> Stratosec - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella
>
RE: 4.4 Feature Freeze
Posted by Sudha Ponnaganti <su...@citrix.com>.
+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 state as of now. There are only 2 weeks left to close on coding and developers would rush to check in the code. This only results in poor quality code.
Thanks
/sudha
-----Original Message-----
From: John Kinsella [mailto:jlk@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 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.
What we have a stronger need for than 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 feature freeze date.
John
On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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
> efforts. We shouldn't be penalizing them with this 2 week's feature
> freeze schedule
>
> Thanks,
> RamG
>
>> -----Original Message-----
>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called
>> out in earlier mail the feature proposal date was not called out for
>> 4.4 and as such giving little extra room seems reasonable.
>>
>> Animesh
>>
>>> -----Original Message-----
>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 beginning to realize that a four-month release cycle has not
>>> been very realistic for us yet.
>>>
>>> The main issue I encounter is our month-long RC cycle where I spend
>>> a bunch of time validating the RC and (during that timeframe) less
>>> time developing for the next release as I had initially planned.
>>>
>>> Perhaps instead of extending the cycle we could consider ways to
>>> actually meet the schedule on a consistent basis. That would be
>>> fine, as
>> well.
>>>
>>>
>>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
>>> wrote:
>>>
>>>> -1 on postponing the feature freeze. We are having this discussion
>>>> after every release, however we agreed to do a 4 month cycle so
>>>> let's stick
>>> to it.
>>>>
>>>> If there are important features that are currently being developed
>>>> but might not make this cut-off date we should discuss that
>>>> separately, but as a point of principle lets stick to the release
>>>> schedule as
>> proposed.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Hugo
>>>>
>>>>
>>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>>>> <tr...@weberize.com>
>>>> wrote:
>>>>
>>>>> +1 to Daan.
>>>>>
>>>>> Tracy Phillips
>>>>> Weberize, Inc.
>>>>>
>>>>>
>>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>>>>> <daan.hoogland@gmail.com
>>>>> wrote:
>>>>>
>>>>>> -1 for postponing the feature freeze. It will amount to more
>>>>>> features in the release. I'd rather shorten the cycle and do more
>>>>>> releases then to pack more bugs in a single go.
>>>>>>
>>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
>>> wrote:
>>>>>>> +1
>>>>>>>
>>>>>>>
>>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>>>>>> Abhinandan.Prateek@citrix.com
>>>>>>>> :
>>>>>>>
>>>>>>>> +1 for 4.4 feature freeze on 3/28.
>>>>>>>>
>>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>>>>>>>> <sa...@citrix.com> wrote:
>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Sateesh
>>>>>>>>>
>>>>>>>>>> I also agree we should discuss 4+ month development cycles
>> again.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>>>>>>>>>>> longer, but wanted to call out one more important date.
>>>>>>>>>>>
>>>>>>>>>>> We have a last day for feature proposal date which is
>>>>>>>>>>> typically a month before feature freeze date. If following
>>>>>>>>>>> 4.3 schedule + 4
>>>>>> month
>>>>>>>>>>> it would have been 2/14 and we are already past that. Since
>>>>>>>>>>> it was
>>>>>> not
>>>>>>>>>>> announced for
>>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>>>>>>>>>>> proposal
>>>>>> open
>>>>>>>>>>> for another week and push all the dates out by 2 weeks to
>>>>>>>>>>> give
>>>>>> folks
>>>>>>>>>>> opportunity to finish up their features for new proposals
>>>>>>>>>>> that are
>>>>>> yet
>>>>>>>>>>> to come out.
>>>>>>>>>>>
>>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>>>>>>>>>>> 3/28 from
>>>>>>>>>>> 3/14 and all the other dates likewise.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>> Animesh
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: Animesh Chaturvedi
>>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>>>>>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>>>>>>>>>>>>
>>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>>>>>>>>>>>> discuss if
>>>>>> we
>>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>>>>>>>>>>>> months. I
>>>>>> was
>>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
>>>>>>>>>>>>
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
>>>>>>>>>>>>> Trippaers
>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>
>>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
>>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
>>>>>>>>>>>>> personal
>>>>>> life
>>>>>>>>>>>>> into
>>>>>>>>>>> account ;-) ):
>>>>>>>>>>>>>
>>>>>>>>>>>>> Feature Freeze: March 14, 2014
>>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>>>>>> 18,
>>>>>>>>>> 2014
>>>>>>>>>>>>> (direct access for committers)
>>>>>>>>>>>>> Stability Fixes only: April 19, 2014 till
>>>>>>>>>>> release (cherry picks
>>>>>>>>>>>>> by RM only)
>>>>>>>>>>>>> First RC: May 9, 2014
>>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hugo
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>>>>>>>>>>>>> <su...@citrix.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>>>>>>>>>>>>>> 0540<tel:+442036030540>
>>>>>> |
>>>>>>>>>> M:
>>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
>>>>>>>>>>>>>> WC2N
>>>>>> 4HS
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>>>>>>>>>>>>>> Our CloudStack Infrastructure
>>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>>>>>> CloudStack
>>>>>>>>>>>>> Environments.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>> training/>
>>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> This email and any attachments to it may be confidential
>>>>>>>>>>>>>> and
>>>>>> are
>>>>>>>>>>>>>> intended
>>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
>>>>>> Any
>>>>>>>>>>>>> views or opinions expressed are solely those of the author
>>>>>>>>>>>>> and
>>>>>> do
>>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>>>>>>>>>>>>> related companies. If you are not the intended recipient
>>>>>>>>>>>>> of this email, you must neither take any action based upon
>>>>>>>>>>>>> its contents, nor
>>>>>> copy
>>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>>>>>>>>>>>>> believe
>>>>>> you
>>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>>>>>>>>>>>>> Services India LLP
>>>>>> is a
>>>>>>>>>>>>> company incorporated in India and is operated under
>>>>>>>>>>>>> license
>>>>>> from
>>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>>>>>>>>>>>>> company incorporated in Brasil and is operated under
>>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>>>>>>>>>>> a
>>>>>>>>>>>> registered trademark.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Mike Tutkowski*
>>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>>>>>>>> e: mike.tutkowski@solidfire.com
>>>>>>>>>> o: 303.746.7302
>>>>>>>>>> Advancing the way the world uses the
>>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>>>>>>>> *(tm)*
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Daan
>>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkowski@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>> *(tm)*
Stratosec - Compliance as a Service
o: 415.315.9385
@johnlkinsella
Re: 4.4 Feature Freeze
Posted by John Kinsella <jl...@stratosec.co>.
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 issues, it’s not uncommon for us to allow them in late.
What we have a stronger need for than 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 feature freeze date.
John
On Feb 26, 2014, at 7:10 PM, Ram Ganesh <Ra...@citrix.com> 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 efforts. We shouldn't be penalizing them with this 2 week's feature freeze schedule
>
> Thanks,
> RamG
>
>> -----Original Message-----
>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called out in earlier
>> mail the feature proposal date was not called out for 4.4 and as such giving
>> little extra room seems reasonable.
>>
>> Animesh
>>
>>> -----Original Message-----
>>> From: Mike Tutkowski [mailto:mike.tutkowski@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
>>> beginning to realize that a four-month release cycle has not been very
>>> realistic for us yet.
>>>
>>> The main issue I encounter is our month-long RC cycle where I spend a
>>> bunch of time validating the RC and (during that timeframe) less time
>>> developing for the next release as I had initially planned.
>>>
>>> Perhaps instead of extending the cycle we could consider ways to
>>> actually meet the schedule on a consistent basis. That would be fine, as
>> well.
>>>
>>>
>>> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
>>> wrote:
>>>
>>>> -1 on postponing the feature freeze. We are having this discussion
>>>> after every release, however we agreed to do a 4 month cycle so
>>>> let's stick
>>> to it.
>>>>
>>>> If there are important features that are currently being developed
>>>> but might not make this cut-off date we should discuss that
>>>> separately, but as a point of principle lets stick to the release schedule as
>> proposed.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Hugo
>>>>
>>>>
>>>> On 26 feb. 2014, at 15:23, Tracy Phillips
>>>> <tr...@weberize.com>
>>>> wrote:
>>>>
>>>>> +1 to Daan.
>>>>>
>>>>> Tracy Phillips
>>>>> Weberize, Inc.
>>>>>
>>>>>
>>>>> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
>>>>> <daan.hoogland@gmail.com
>>>>> wrote:
>>>>>
>>>>>> -1 for postponing the feature freeze. It will amount to more
>>>>>> features in the release. I'd rather shorten the cycle and do more
>>>>>> releases then to pack more bugs in a single go.
>>>>>>
>>>>>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
>>> wrote:
>>>>>>> +1
>>>>>>>
>>>>>>>
>>>>>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>>>>>> Abhinandan.Prateek@citrix.com
>>>>>>>> :
>>>>>>>
>>>>>>>> +1 for 4.4 feature freeze on 3/28.
>>>>>>>>
>>>>>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>>>>>>>> <sa...@citrix.com> wrote:
>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Sateesh
>>>>>>>>>
>>>>>>>>>> I also agree we should discuss 4+ month development cycles
>> again.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>>>>>>>>>> animesh.chaturvedi@citrix.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I will start a separate discussion on 4 month cycle or
>>>>>>>>>>> longer, but wanted to call out one more important date.
>>>>>>>>>>>
>>>>>>>>>>> We have a last day for feature proposal date which is
>>>>>>>>>>> typically a month before feature freeze date. If following
>>>>>>>>>>> 4.3 schedule + 4
>>>>>> month
>>>>>>>>>>> it would have been 2/14 and we are already past that. Since
>>>>>>>>>>> it was
>>>>>> not
>>>>>>>>>>> announced for
>>>>>>>>>>> 4.4 release yet my suggestion would be to keep feature
>>>>>>>>>>> proposal
>>>>>> open
>>>>>>>>>>> for another week and push all the dates out by 2 weeks to
>>>>>>>>>>> give
>>>>>> folks
>>>>>>>>>>> opportunity to finish up their features for new proposals
>>>>>>>>>>> that are
>>>>>> yet
>>>>>>>>>>> to come out.
>>>>>>>>>>>
>>>>>>>>>>> To be clear that would mean pushing out feature freeze to
>>>>>>>>>>> 3/28 from
>>>>>>>>>>> 3/14 and all the other dates likewise.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>> Animesh
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: Animesh Chaturvedi
>>>>>>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>>>>>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>>>>>> Subject: RE: 4.4 Feature Freeze
>>>>>>>>>>>>
>>>>>>>>>>>> With the experience of 4.2 and 4.3 I think we should
>>>>>>>>>>>> discuss if
>>>>>> we
>>>>>>>>>>>> can realistically achieve 4 month cycle our RCs take 2
>>>>>>>>>>>> months. I
>>>>>> was
>>>>>>>>>>>> going to open up the discussion after 4.3 is shipped though.
>>>>>>>>>>>>
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
>>>>>>>>>>>>> Trippaers
>>>>>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>>>>>>>>>>>>> To: <de...@cloudstack.apache.org>
>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>
>>>>>>>>>>>>> So the proposed release schedule for 4.4 would look like
>>>>>>>>>>>>> this (dates slightly modified to take efficiency and RM's
>>>>>>>>>>>>> personal
>>>>>> life
>>>>>>>>>>>>> into
>>>>>>>>>>> account ;-) ):
>>>>>>>>>>>>>
>>>>>>>>>>>>> Feature Freeze: March 14, 2014
>>>>>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>>>>>> 18,
>>>>>>>>>> 2014
>>>>>>>>>>>>> (direct access for committers)
>>>>>>>>>>>>> Stability Fixes only: April 19, 2014 till
>>>>>>>>>>> release (cherry picks
>>>>>>>>>>>>> by RM only)
>>>>>>>>>>>>> First RC: May 9, 2014
>>>>>>>>>>>>> Optimistic Release Date: May 19, 2014
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hugo
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>>>>>>>>>>>>> <su...@citrix.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
>>>>>>>>>>>>>> 0540<tel:+442036030540>
>>>>>> |
>>>>>>>>>> M:
>>>>>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
>>>>>>>>>>>>>> WC2N
>>>>>> 4HS
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>>>>>>>>>>>>>> Our CloudStack Infrastructure
>>>>>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>>>>>> CloudStack
>>>>>>>>>>>>> Environments.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Apache CloudStack Bootcamp training courses
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **NEW!** CloudStack 4.2.1
>>>>>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>>>>>>>>>>>>> training/>
>>>>>>>>>>>>>> 18th-19th February 2014, Brazil.
>>>>>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>>>>>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> This email and any attachments to it may be confidential
>>>>>>>>>>>>>> and
>>>>>> are
>>>>>>>>>>>>>> intended
>>>>>>>>>>>>> solely for the use of the individual to whom it is addressed.
>>>>>> Any
>>>>>>>>>>>>> views or opinions expressed are solely those of the author
>>>>>>>>>>>>> and
>>>>>> do
>>>>>>>>>>>>> not necessarily represent those of Shape Blue Ltd or
>>>>>>>>>>>>> related companies. If you are not the intended recipient
>>>>>>>>>>>>> of this email, you must neither take any action based upon
>>>>>>>>>>>>> its contents, nor
>>>>>> copy
>>>>>>>>>>>>> or show it to anyone. Please contact the sender if you
>>>>>>>>>>>>> believe
>>>>>> you
>>>>>>>>>>>>> have received this email in error. Shape Blue Ltd is a
>>>>>>>>>>>>> company incorporated in England & Wales. ShapeBlue
>>>>>>>>>>>>> Services India LLP
>>>>>> is a
>>>>>>>>>>>>> company incorporated in India and is operated under
>>>>>>>>>>>>> license
>>>>>> from
>>>>>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>>>>>>>>>>>>> company incorporated in Brasil and is operated under
>>>>>>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
>>>>>>>>>>> a
>>>>>>>>>>>> registered trademark.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Mike Tutkowski*
>>>>>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>>>>>>>> e: mike.tutkowski@solidfire.com
>>>>>>>>>> o: 303.746.7302
>>>>>>>>>> Advancing the way the world uses the
>>>>>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>>>>>>>> *(tm)*
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Daan
>>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkowski@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>> *(tm)*
Stratosec - Compliance as a Service
o: 415.315.9385
@johnlkinsella
RE: 4.4 Feature Freeze
Posted by Ram Ganesh <Ra...@citrix.com>.
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 efforts. We shouldn't be penalizing them with this 2 week's feature freeze schedule
Thanks,
RamG
> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@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. As I called out in earlier
> mail the feature proposal date was not called out for 4.4 and as such giving
> little extra room seems reasonable.
>
> Animesh
>
> > -----Original Message-----
> > From: Mike Tutkowski [mailto:mike.tutkowski@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
> > beginning to realize that a four-month release cycle has not been very
> > realistic for us yet.
> >
> > The main issue I encounter is our month-long RC cycle where I spend a
> > bunch of time validating the RC and (during that timeframe) less time
> > developing for the next release as I had initially planned.
> >
> > Perhaps instead of extending the cycle we could consider ways to
> > actually meet the schedule on a consistent basis. That would be fine, as
> well.
> >
> >
> > On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
> > wrote:
> >
> > > -1 on postponing the feature freeze. We are having this discussion
> > > after every release, however we agreed to do a 4 month cycle so
> > > let's stick
> > to it.
> > >
> > > If there are important features that are currently being developed
> > > but might not make this cut-off date we should discuss that
> > > separately, but as a point of principle lets stick to the release schedule as
> proposed.
> > >
> > >
> > > Cheers,
> > >
> > > Hugo
> > >
> > >
> > > On 26 feb. 2014, at 15:23, Tracy Phillips
> > > <tr...@weberize.com>
> > > wrote:
> > >
> > > > +1 to Daan.
> > > >
> > > > Tracy Phillips
> > > > Weberize, Inc.
> > > >
> > > >
> > > > On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> > > ><daan.hoogland@gmail.com
> > > >wrote:
> > > >
> > > >> -1 for postponing the feature freeze. It will amount to more
> > > >> features in the release. I'd rather shorten the cycle and do more
> > > >> releases then to pack more bugs in a single go.
> > > >>
> > > >> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
> > wrote:
> > > >>> +1
> > > >>>
> > > >>>
> > > >>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> > > >> Abhinandan.Prateek@citrix.com
> > > >>>> :
> > > >>>
> > > >>>> +1 for 4.4 feature freeze on 3/28.
> > > >>>>
> > > >>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> > > >>>> <sa...@citrix.com> wrote:
> > > >>>>
> > > >>>>>> -----Original Message-----
> > > >>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> > > >>>>>
> > > >>>>> Regards,
> > > >>>>> Sateesh
> > > >>>>>
> > > >>>>>> I also agree we should discuss 4+ month development cycles
> again.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> > > >>>>>> animesh.chaturvedi@citrix.com> wrote:
> > > >>>>>>
> > > >>>>>>> I will start a separate discussion on 4 month cycle or
> > > >>>>>>> longer, but wanted to call out one more important date.
> > > >>>>>>>
> > > >>>>>>> We have a last day for feature proposal date which is
> > > >>>>>>> typically a month before feature freeze date. If following
> > > >>>>>>> 4.3 schedule + 4
> > > >> month
> > > >>>>>>> it would have been 2/14 and we are already past that. Since
> > > >>>>>>> it was
> > > >> not
> > > >>>>>>> announced for
> > > >>>>>>> 4.4 release yet my suggestion would be to keep feature
> > > >>>>>>> proposal
> > > >> open
> > > >>>>>>> for another week and push all the dates out by 2 weeks to
> > > >>>>>>> give
> > > >> folks
> > > >>>>>>> opportunity to finish up their features for new proposals
> > > >>>>>>> that are
> > > >> yet
> > > >>>>>>> to come out.
> > > >>>>>>>
> > > >>>>>>> To be clear that would mean pushing out feature freeze to
> > > >>>>>>> 3/28 from
> > > >>>>>>> 3/14 and all the other dates likewise.
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> Thanks
> > > >>>>>>> Animesh
> > > >>>>>>>
> > > >>>>>>>> -----Original Message-----
> > > >>>>>>>> From: Animesh Chaturvedi
> > > >>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> > > >>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> > > >>>>>>>> To: dev@cloudstack.apache.org
> > > >>>>>>>> Subject: RE: 4.4 Feature Freeze
> > > >>>>>>>>
> > > >>>>>>>> With the experience of 4.2 and 4.3 I think we should
> > > >>>>>>>> discuss if
> > > >> we
> > > >>>>>>>> can realistically achieve 4 month cycle our RCs take 2
> > > >>>>>>>> months. I
> > > >> was
> > > >>>>>>>> going to open up the discussion after 4.3 is shipped though.
> > > >>>>>>>>
> > > >>>>>>>>> -----Original Message-----
> > > >>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
> > > >>>>>>>>> Trippaers
> > > >>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> > > >>>>>>>>> To: <de...@cloudstack.apache.org>
> > > >>>>>>>>> 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.
> > > >>>>>>>>>
> > > >>>>>>>>> So the proposed release schedule for 4.4 would look like
> > > >>>>>>>>> this (dates slightly modified to take efficiency and RM's
> > > >>>>>>>>> personal
> > > >> life
> > > >>>>>>>>> into
> > > >>>>>>> account ;-) ):
> > > >>>>>>>>>
> > > >>>>>>>>> Feature Freeze: March 14, 2014
> > > >>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
> > > >> 18,
> > > >>>>>> 2014
> > > >>>>>>>>> (direct access for committers)
> > > >>>>>>>>> Stability Fixes only: April 19, 2014 till
> > > >>>>>>> release (cherry picks
> > > >>>>>>>>> by RM only)
> > > >>>>>>>>> First RC: May 9, 2014
> > > >>>>>>>>> Optimistic Release Date: May 19, 2014
> > > >>>>>>>>>
> > > >>>>>>>>> Cheers,
> > > >>>>>>>>>
> > > >>>>>>>>> Hugo
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > > >>>>>>>>> <su...@citrix.com>
> > > >>>>>>>>> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> > > >>>>>>>>>> 0540<tel:+442036030540>
> > > >> |
> > > >>>>>> M:
> > > >>>>>>>>> +44<tel:+447968161581> 7788 423 969
> > > >>>>>>>>>>
> > > >>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
> > > >>>>>>>>>> WC2N
> > > >> 4HS
> > > >>>>>>>>>>
> > > >>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> > > >>>>>>>>>> Our CloudStack Infrastructure
> > > >>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> > > >>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> > > >> CloudStack
> > > >>>>>>>>> Environments.
> > > >>>>>>>>>>
> > > >>>>>>>>>> Apache CloudStack Bootcamp training courses
> > > >>>>>>>>>>
> > > >>>>>>>>>> **NEW!** CloudStack 4.2.1
> > > >>>>>>>>>> training<http://shapeblue.com/cloudstack-
> > > >>>>>>>>> training/>
> > > >>>>>>>>>> 18th-19th February 2014, Brazil.
> > > >>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> > > >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> > > >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> > > >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> > > >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > > >>>>>>>>>>
> > > >>>>>>>>>> This email and any attachments to it may be confidential
> > > >>>>>>>>>> and
> > > >> are
> > > >>>>>>>>>> intended
> > > >>>>>>>>> solely for the use of the individual to whom it is addressed.
> > > >> Any
> > > >>>>>>>>> views or opinions expressed are solely those of the author
> > > >>>>>>>>> and
> > > >> do
> > > >>>>>>>>> not necessarily represent those of Shape Blue Ltd or
> > > >>>>>>>>> related companies. If you are not the intended recipient
> > > >>>>>>>>> of this email, you must neither take any action based upon
> > > >>>>>>>>> its contents, nor
> > > >> copy
> > > >>>>>>>>> or show it to anyone. Please contact the sender if you
> > > >>>>>>>>> believe
> > > >> you
> > > >>>>>>>>> have received this email in error. Shape Blue Ltd is a
> > > >>>>>>>>> company incorporated in England & Wales. ShapeBlue
> > > >>>>>>>>> Services India LLP
> > > >> is a
> > > >>>>>>>>> company incorporated in India and is operated under
> > > >>>>>>>>> license
> > > >> from
> > > >>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > > >>>>>>>>> company incorporated in Brasil and is operated under
> > > >>>>>>>>> license from Shape Blue Ltd. ShapeBlue is
> > > >>>>>>> a
> > > >>>>>>>> registered trademark.
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> *Mike Tutkowski*
> > > >>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> > > >>>>>> e: mike.tutkowski@solidfire.com
> > > >>>>>> o: 303.746.7302
> > > >>>>>> Advancing the way the world uses the
> > > >>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
> > > >>>>>> *(tm)*
> > > >>>>
> > > >>>>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Daan
> > > >>
> > >
> > >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *(tm)*
RE: 4.4 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
Mike I share your opinion most of us have been pretty much on 4.3 until now, and pushing out the release seems reasonable. As I called out in earlier mail the feature proposal date was not called out for 4.4 and as such giving little extra room seems reasonable.
Animesh
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@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
> beginning to realize that a four-month release cycle has not been very
> realistic for us yet.
>
> The main issue I encounter is our month-long RC cycle where I spend a
> bunch of time validating the RC and (during that timeframe) less time
> developing for the next release as I had initially planned.
>
> Perhaps instead of extending the cycle we could consider ways to actually
> meet the schedule on a consistent basis. That would be fine, as well.
>
>
> On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl>
> wrote:
>
> > -1 on postponing the feature freeze. We are having this discussion
> > after every release, however we agreed to do a 4 month cycle so let's stick
> to it.
> >
> > If there are important features that are currently being developed but
> > might not make this cut-off date we should discuss that separately,
> > but as a point of principle lets stick to the release schedule as proposed.
> >
> >
> > Cheers,
> >
> > Hugo
> >
> >
> > On 26 feb. 2014, at 15:23, Tracy Phillips
> > <tr...@weberize.com>
> > wrote:
> >
> > > +1 to Daan.
> > >
> > > Tracy Phillips
> > > Weberize, Inc.
> > >
> > >
> > > On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland
> > ><daan.hoogland@gmail.com
> > >wrote:
> > >
> > >> -1 for postponing the feature freeze. It will amount to more
> > >> features in the release. I'd rather shorten the cycle and do more
> > >> releases then to pack more bugs in a single go.
> > >>
> > >> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com>
> wrote:
> > >>> +1
> > >>>
> > >>>
> > >>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> > >> Abhinandan.Prateek@citrix.com
> > >>>> :
> > >>>
> > >>>> +1 for 4.4 feature freeze on 3/28.
> > >>>>
> > >>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> > >>>> <sa...@citrix.com> wrote:
> > >>>>
> > >>>>>> -----Original Message-----
> > >>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> > >>>>>
> > >>>>> Regards,
> > >>>>> Sateesh
> > >>>>>
> > >>>>>> I also agree we should discuss 4+ month development cycles again.
> > >>>>>>
> > >>>>>>
> > >>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> > >>>>>> animesh.chaturvedi@citrix.com> wrote:
> > >>>>>>
> > >>>>>>> I will start a separate discussion on 4 month cycle or longer,
> > >>>>>>> but wanted to call out one more important date.
> > >>>>>>>
> > >>>>>>> We have a last day for feature proposal date which is
> > >>>>>>> typically a month before feature freeze date. If following 4.3
> > >>>>>>> schedule + 4
> > >> month
> > >>>>>>> it would have been 2/14 and we are already past that. Since it
> > >>>>>>> was
> > >> not
> > >>>>>>> announced for
> > >>>>>>> 4.4 release yet my suggestion would be to keep feature
> > >>>>>>> proposal
> > >> open
> > >>>>>>> for another week and push all the dates out by 2 weeks to
> > >>>>>>> give
> > >> folks
> > >>>>>>> opportunity to finish up their features for new proposals that
> > >>>>>>> are
> > >> yet
> > >>>>>>> to come out.
> > >>>>>>>
> > >>>>>>> To be clear that would mean pushing out feature freeze to 3/28
> > >>>>>>> from
> > >>>>>>> 3/14 and all the other dates likewise.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> Thanks
> > >>>>>>> Animesh
> > >>>>>>>
> > >>>>>>>> -----Original Message-----
> > >>>>>>>> From: Animesh Chaturvedi
> > >>>>>>>> [mailto:animesh.chaturvedi@citrix.com]
> > >>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> > >>>>>>>> To: dev@cloudstack.apache.org
> > >>>>>>>> Subject: RE: 4.4 Feature Freeze
> > >>>>>>>>
> > >>>>>>>> With the experience of 4.2 and 4.3 I think we should discuss
> > >>>>>>>> if
> > >> we
> > >>>>>>>> can realistically achieve 4 month cycle our RCs take 2
> > >>>>>>>> months. I
> > >> was
> > >>>>>>>> going to open up the discussion after 4.3 is shipped though.
> > >>>>>>>>
> > >>>>>>>>> -----Original Message-----
> > >>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
> > >>>>>>>>> Trippaers
> > >>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> > >>>>>>>>> To: <de...@cloudstack.apache.org>
> > >>>>>>>>> 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.
> > >>>>>>>>>
> > >>>>>>>>> So the proposed release schedule for 4.4 would look like
> > >>>>>>>>> this (dates slightly modified to take efficiency and RM's
> > >>>>>>>>> personal
> > >> life
> > >>>>>>>>> into
> > >>>>>>> account ;-) ):
> > >>>>>>>>>
> > >>>>>>>>> Feature Freeze: March 14, 2014
> > >>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
> > >> 18,
> > >>>>>> 2014
> > >>>>>>>>> (direct access for committers)
> > >>>>>>>>> Stability Fixes only: April 19, 2014 till
> > >>>>>>> release (cherry picks
> > >>>>>>>>> by RM only)
> > >>>>>>>>> First RC: May 9, 2014
> > >>>>>>>>> Optimistic Release Date: May 19, 2014
> > >>>>>>>>>
> > >>>>>>>>> Cheers,
> > >>>>>>>>>
> > >>>>>>>>> Hugo
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > >>>>>>>>> <su...@citrix.com>
> > >>>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603
> > >>>>>>>>>> 0540<tel:+442036030540>
> > >> |
> > >>>>>> M:
> > >>>>>>>>> +44<tel:+447968161581> 7788 423 969
> > >>>>>>>>>>
> > >>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London,
> > >>>>>>>>>> WC2N
> > >> 4HS
> > >>>>>>>>>>
> > >>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> > >>>>>>>>>> Our CloudStack Infrastructure
> > >>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> > >>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> > >> CloudStack
> > >>>>>>>>> Environments.
> > >>>>>>>>>>
> > >>>>>>>>>> Apache CloudStack Bootcamp training courses
> > >>>>>>>>>>
> > >>>>>>>>>> **NEW!** CloudStack 4.2.1
> > >>>>>>>>>> training<http://shapeblue.com/cloudstack-
> > >>>>>>>>> training/>
> > >>>>>>>>>> 18th-19th February 2014, Brazil.
> > >>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> > >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> > >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> > >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> > >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> > >>>>>>>>>>
> > >>>>>>>>>> This email and any attachments to it may be confidential
> > >>>>>>>>>> and
> > >> are
> > >>>>>>>>>> intended
> > >>>>>>>>> solely for the use of the individual to whom it is addressed.
> > >> Any
> > >>>>>>>>> views or opinions expressed are solely those of the author
> > >>>>>>>>> and
> > >> do
> > >>>>>>>>> not necessarily represent those of Shape Blue Ltd or related
> > >>>>>>>>> companies. If you are not the intended recipient of this
> > >>>>>>>>> email, you must neither take any action based upon its
> > >>>>>>>>> contents, nor
> > >> copy
> > >>>>>>>>> or show it to anyone. Please contact the sender if you
> > >>>>>>>>> believe
> > >> you
> > >>>>>>>>> have received this email in error. Shape Blue Ltd is a
> > >>>>>>>>> company incorporated in England & Wales. ShapeBlue Services
> > >>>>>>>>> India LLP
> > >> is a
> > >>>>>>>>> company incorporated in India and is operated under license
> > >> from
> > >>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > >>>>>>>>> company incorporated in Brasil and is operated under license
> > >>>>>>>>> from Shape Blue Ltd. ShapeBlue is
> > >>>>>>> a
> > >>>>>>>> registered trademark.
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> *Mike Tutkowski*
> > >>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> > >>>>>> e: mike.tutkowski@solidfire.com
> > >>>>>> o: 303.746.7302
> > >>>>>> Advancing the way the world uses the
> > >>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
> > >>>>>> *(tm)*
> > >>>>
> > >>>>
> > >>
> > >>
> > >>
> > >> --
> > >> Daan
> > >>
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
I think we're having this discussion after every release because we're
beginning to realize that a four-month release cycle has not been very
realistic for us yet.
The main issue I encounter is our month-long RC cycle where I spend a bunch
of time validating the RC and (during that timeframe) less time developing
for the next release as I had initially planned.
Perhaps instead of extending the cycle we could consider ways to actually
meet the schedule on a consistent basis. That would be fine, as well.
On Wed, Feb 26, 2014 at 8:04 AM, Hugo Trippaers <hu...@trippaers.nl> wrote:
> -1 on postponing the feature freeze. We are having this discussion after
> every release, however we agreed to do a 4 month cycle so let's stick to it.
>
> If there are important features that are currently being developed but
> might not make this cut-off date we should discuss that separately, but as
> a point of principle lets stick to the release schedule as proposed.
>
>
> Cheers,
>
> Hugo
>
>
> On 26 feb. 2014, at 15:23, Tracy Phillips <tr...@weberize.com>
> wrote:
>
> > +1 to Daan.
> >
> > Tracy Phillips
> > Weberize, Inc.
> >
> >
> > On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland <daan.hoogland@gmail.com
> >wrote:
> >
> >> -1 for postponing the feature freeze. It will amount to more features
> >> in the release. I'd rather shorten the cycle and do more releases then
> >> to pack more bugs in a single go.
> >>
> >> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com> wrote:
> >>> +1
> >>>
> >>>
> >>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> >> Abhinandan.Prateek@citrix.com
> >>>> :
> >>>
> >>>> +1 for 4.4 feature freeze on 3/28.
> >>>>
> >>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> >>>> <sa...@citrix.com> wrote:
> >>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> >>>>>
> >>>>> Regards,
> >>>>> Sateesh
> >>>>>
> >>>>>> I also agree we should discuss 4+ month development cycles again.
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> >>>>>> animesh.chaturvedi@citrix.com> wrote:
> >>>>>>
> >>>>>>> I will start a separate discussion on 4 month cycle or longer, but
> >>>>>>> wanted to call out one more important date.
> >>>>>>>
> >>>>>>> We have a last day for feature proposal date which is typically a
> >>>>>>> month before feature freeze date. If following 4.3 schedule + 4
> >> month
> >>>>>>> it would have been 2/14 and we are already past that. Since it was
> >> not
> >>>>>>> announced for
> >>>>>>> 4.4 release yet my suggestion would be to keep feature proposal
> >> open
> >>>>>>> for another week and push all the dates out by 2 weeks to give
> >> folks
> >>>>>>> opportunity to finish up their features for new proposals that are
> >> yet
> >>>>>>> to come out.
> >>>>>>>
> >>>>>>> To be clear that would mean pushing out feature freeze to 3/28 from
> >>>>>>> 3/14 and all the other dates likewise.
> >>>>>>>
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>> Animesh
> >>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> >>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
> >>>>>>>> To: dev@cloudstack.apache.org
> >>>>>>>> Subject: RE: 4.4 Feature Freeze
> >>>>>>>>
> >>>>>>>> With the experience of 4.2 and 4.3 I think we should discuss if
> >> we
> >>>>>>>> can realistically achieve 4 month cycle our RCs take 2 months. I
> >> was
> >>>>>>>> going to open up the discussion after 4.3 is shipped though.
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
> >>>>>>>>> Trippaers
> >>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
> >>>>>>>>> To: <de...@cloudstack.apache.org>
> >>>>>>>>> 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.
> >>>>>>>>>
> >>>>>>>>> So the proposed release schedule for 4.4 would look like this
> >>>>>>>>> (dates slightly modified to take efficiency and RM's personal
> >> life
> >>>>>>>>> into
> >>>>>>> account ;-) ):
> >>>>>>>>>
> >>>>>>>>> Feature Freeze: March 14, 2014
> >>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
> >> 18,
> >>>>>> 2014
> >>>>>>>>> (direct access for committers)
> >>>>>>>>> Stability Fixes only: April 19, 2014 till
> >>>>>>> release (cherry picks
> >>>>>>>>> by RM only)
> >>>>>>>>> First RC: May 9, 2014
> >>>>>>>>> Optimistic Release Date: May 19, 2014
> >>>>>>>>>
> >>>>>>>>> Cheers,
> >>>>>>>>>
> >>>>>>>>> Hugo
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> >>>>>>>>> <su...@citrix.com>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540>
> >> |
> >>>>>> M:
> >>>>>>>>> +44<tel:+447968161581> 7788 423 969
> >>>>>>>>>>
> >>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
> >> 4HS
> >>>>>>>>>>
> >>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
> >>>>>>>>>> Our CloudStack Infrastructure
> >>>>>>>>>> Support<http://shapeblue.com/cloudstack-
> >>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
> >> CloudStack
> >>>>>>>>> Environments.
> >>>>>>>>>>
> >>>>>>>>>> Apache CloudStack Bootcamp training courses
> >>>>>>>>>>
> >>>>>>>>>> **NEW!** CloudStack 4.2.1
> >>>>>>>>>> training<http://shapeblue.com/cloudstack-
> >>>>>>>>> training/>
> >>>>>>>>>> 18th-19th February 2014, Brazil.
> >>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
> >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
> >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
> >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
> >>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
> >>>>>>>>>>
> >>>>>>>>>> This email and any attachments to it may be confidential and
> >> are
> >>>>>>>>>> intended
> >>>>>>>>> solely for the use of the individual to whom it is addressed.
> >> Any
> >>>>>>>>> views or opinions expressed are solely those of the author and
> >> do
> >>>>>>>>> not necessarily represent those of Shape Blue Ltd or related
> >>>>>>>>> companies. If you are not the intended recipient of this email,
> >>>>>>>>> you must neither take any action based upon its contents, nor
> >> copy
> >>>>>>>>> or show it to anyone. Please contact the sender if you believe
> >> you
> >>>>>>>>> have received this email in error. Shape Blue Ltd is a company
> >>>>>>>>> incorporated in England & Wales. ShapeBlue Services India LLP
> >> is a
> >>>>>>>>> company incorporated in India and is operated under license
> >> from
> >>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company
> >>>>>>>>> incorporated in Brasil and is operated under license from Shape
> >>>>>>>>> Blue Ltd. ShapeBlue is
> >>>>>>> a
> >>>>>>>> registered trademark.
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> *Mike Tutkowski*
> >>>>>> *Senior CloudStack Developer, SolidFire Inc.*
> >>>>>> e: mike.tutkowski@solidfire.com
> >>>>>> o: 303.746.7302
> >>>>>> Advancing the way the world uses the
> >>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
> >>>>>> *(tm)*
> >>>>
> >>>>
> >>
> >>
> >>
> >> --
> >> Daan
> >>
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Hugo Trippaers <hu...@trippaers.nl>.
-1 on postponing the feature freeze. We are having this discussion after every release, however we agreed to do a 4 month cycle so let's stick to it.
If there are important features that are currently being developed but might not make this cut-off date we should discuss that separately, but as a point of principle lets stick to the release schedule as proposed.
Cheers,
Hugo
On 26 feb. 2014, at 15:23, Tracy Phillips <tr...@weberize.com> wrote:
> +1 to Daan.
>
> Tracy Phillips
> Weberize, Inc.
>
>
> On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland <da...@gmail.com>wrote:
>
>> -1 for postponing the feature freeze. It will amount to more features
>> in the release. I'd rather shorten the cycle and do more releases then
>> to pack more bugs in a single go.
>>
>> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com> wrote:
>>> +1
>>>
>>>
>>> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
>> Abhinandan.Prateek@citrix.com
>>>> :
>>>
>>>> +1 for 4.4 feature freeze on 3/28.
>>>>
>>>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>>>> <sa...@citrix.com> wrote:
>>>>
>>>>>> -----Original Message-----
>>>>>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>>>>>
>>>>> Regards,
>>>>> Sateesh
>>>>>
>>>>>> I also agree we should discuss 4+ month development cycles again.
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>>>>>> animesh.chaturvedi@citrix.com> wrote:
>>>>>>
>>>>>>> I will start a separate discussion on 4 month cycle or longer, but
>>>>>>> wanted to call out one more important date.
>>>>>>>
>>>>>>> We have a last day for feature proposal date which is typically a
>>>>>>> month before feature freeze date. If following 4.3 schedule + 4
>> month
>>>>>>> it would have been 2/14 and we are already past that. Since it was
>> not
>>>>>>> announced for
>>>>>>> 4.4 release yet my suggestion would be to keep feature proposal
>> open
>>>>>>> for another week and push all the dates out by 2 weeks to give
>> folks
>>>>>>> opportunity to finish up their features for new proposals that are
>> yet
>>>>>>> to come out.
>>>>>>>
>>>>>>> To be clear that would mean pushing out feature freeze to 3/28 from
>>>>>>> 3/14 and all the other dates likewise.
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>> Animesh
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
>>>>>>>> Sent: Tuesday, February 25, 2014 1:05 PM
>>>>>>>> To: dev@cloudstack.apache.org
>>>>>>>> Subject: RE: 4.4 Feature Freeze
>>>>>>>>
>>>>>>>> With the experience of 4.2 and 4.3 I think we should discuss if
>> we
>>>>>>>> can realistically achieve 4 month cycle our RCs take 2 months. I
>> was
>>>>>>>> going to open up the discussion after 4.3 is shipped though.
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
>>>>>>>>> Trippaers
>>>>>>>>> Sent: Tuesday, February 25, 2014 8:50 AM
>>>>>>>>> To: <de...@cloudstack.apache.org>
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>> So the proposed release schedule for 4.4 would look like this
>>>>>>>>> (dates slightly modified to take efficiency and RM's personal
>> life
>>>>>>>>> into
>>>>>>> account ;-) ):
>>>>>>>>>
>>>>>>>>> Feature Freeze: March 14, 2014
>>>>>>>>> Testing/Bug Fixes: March 15, 2014 till April
>> 18,
>>>>>> 2014
>>>>>>>>> (direct access for committers)
>>>>>>>>> Stability Fixes only: April 19, 2014 till
>>>>>>> release (cherry picks
>>>>>>>>> by RM only)
>>>>>>>>> First RC: May 9, 2014
>>>>>>>>> Optimistic Release Date: May 19, 2014
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> Hugo
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>>>>>>>>> <su...@citrix.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540>
>> |
>>>>>> M:
>>>>>>>>> +44<tel:+447968161581> 7788 423 969
>>>>>>>>>>
>>>>>>>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
>> 4HS
>>>>>>>>>>
>>>>>>>>>> Need Enterprise Grade Support for Apache CloudStack?
>>>>>>>>>> Our CloudStack Infrastructure
>>>>>>>>>> Support<http://shapeblue.com/cloudstack-
>>>>>>>>> infrastructure-support/> offers the best 24/7 SLA for
>> CloudStack
>>>>>>>>> Environments.
>>>>>>>>>>
>>>>>>>>>> Apache CloudStack Bootcamp training courses
>>>>>>>>>>
>>>>>>>>>> **NEW!** CloudStack 4.2.1
>>>>>>>>>> training<http://shapeblue.com/cloudstack-
>>>>>>>>> training/>
>>>>>>>>>> 18th-19th February 2014, Brazil.
>>>>>>>>> Classroom<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>> 17th-23rd March 2014, Region A. Instructor led, On-
>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>> 24th-28th March 2014, Region B. Instructor led, On-
>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>> 16th-20th June 2014, Region A. Instructor led, On-
>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>> 23rd-27th June 2014, Region B. Instructor led, On-
>>>>>>>>> line<http://shapeblue.com/cloudstack-training/>
>>>>>>>>>>
>>>>>>>>>> This email and any attachments to it may be confidential and
>> are
>>>>>>>>>> intended
>>>>>>>>> solely for the use of the individual to whom it is addressed.
>> Any
>>>>>>>>> views or opinions expressed are solely those of the author and
>> do
>>>>>>>>> not necessarily represent those of Shape Blue Ltd or related
>>>>>>>>> companies. If you are not the intended recipient of this email,
>>>>>>>>> you must neither take any action based upon its contents, nor
>> copy
>>>>>>>>> or show it to anyone. Please contact the sender if you believe
>> you
>>>>>>>>> have received this email in error. Shape Blue Ltd is a company
>>>>>>>>> incorporated in England & Wales. ShapeBlue Services India LLP
>> is a
>>>>>>>>> company incorporated in India and is operated under license
>> from
>>>>>>>>> Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company
>>>>>>>>> incorporated in Brasil and is operated under license from Shape
>>>>>>>>> Blue Ltd. ShapeBlue is
>>>>>>> a
>>>>>>>> registered trademark.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Mike Tutkowski*
>>>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>>>> e: mike.tutkowski@solidfire.com
>>>>>> o: 303.746.7302
>>>>>> Advancing the way the world uses the
>>>>>> cloud<http://solidfire.com/solution/overview/?video=play>
>>>>>> *(tm)*
>>>>
>>>>
>>
>>
>>
>> --
>> Daan
>>
Re: 4.4 Feature Freeze
Posted by Tracy Phillips <tr...@weberize.com>.
+1 to Daan.
Tracy Phillips
Weberize, Inc.
On Wed, Feb 26, 2014 at 7:48 AM, Daan Hoogland <da...@gmail.com>wrote:
> -1 for postponing the feature freeze. It will amount to more features
> in the release. I'd rather shorten the cycle and do more releases then
> to pack more bugs in a single go.
>
> On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com> wrote:
> > +1
> >
> >
> > 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <
> Abhinandan.Prateek@citrix.com
> >>:
> >
> >> +1 for 4.4 feature freeze on 3/28.
> >>
> >> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> >> <sa...@citrix.com> wrote:
> >>
> >> >> -----Original Message-----
> >> >> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> >> >
> >> >Regards,
> >> >Sateesh
> >> >
> >> >> I also agree we should discuss 4+ month development cycles again.
> >> >>
> >> >>
> >> >> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> >> >>animesh.chaturvedi@citrix.com> wrote:
> >> >>
> >> >> > I will start a separate discussion on 4 month cycle or longer, but
> >> >> > wanted to call out one more important date.
> >> >> >
> >> >> > We have a last day for feature proposal date which is typically a
> >> >> > month before feature freeze date. If following 4.3 schedule + 4
> month
> >> >> > it would have been 2/14 and we are already past that. Since it was
> not
> >> >> > announced for
> >> >> > 4.4 release yet my suggestion would be to keep feature proposal
> open
> >> >> > for another week and push all the dates out by 2 weeks to give
> folks
> >> >> > opportunity to finish up their features for new proposals that are
> yet
> >> >> > to come out.
> >> >> >
> >> >> > To be clear that would mean pushing out feature freeze to 3/28 from
> >> >> > 3/14 and all the other dates likewise.
> >> >> >
> >> >> >
> >> >> > Thanks
> >> >> > Animesh
> >> >> >
> >> >> > > -----Original Message-----
> >> >> > > From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> >> >> > > Sent: Tuesday, February 25, 2014 1:05 PM
> >> >> > > To: dev@cloudstack.apache.org
> >> >> > > Subject: RE: 4.4 Feature Freeze
> >> >> > >
> >> >> > > With the experience of 4.2 and 4.3 I think we should discuss if
> we
> >> >> > > can realistically achieve 4 month cycle our RCs take 2 months. I
> was
> >> >> > > going to open up the discussion after 4.3 is shipped though.
> >> >> > >
> >> >> > > > -----Original Message-----
> >> >> > > > From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
> >> >> > > > Trippaers
> >> >> > > > Sent: Tuesday, February 25, 2014 8:50 AM
> >> >> > > > To: <de...@cloudstack.apache.org>
> >> >> > > > 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.
> >> >> > > >
> >> >> > > > So the proposed release schedule for 4.4 would look like this
> >> >> > > > (dates slightly modified to take efficiency and RM's personal
> life
> >> >> > > > into
> >> >> > account ;-) ):
> >> >> > > >
> >> >> > > > Feature Freeze: March 14, 2014
> >> >> > > > Testing/Bug Fixes: March 15, 2014 till April
> 18,
> >> >>2014
> >> >> > > > (direct access for committers)
> >> >> > > > Stability Fixes only: April 19, 2014 till
> >> >> > release (cherry picks
> >> >> > > > by RM only)
> >> >> > > > First RC: May 9, 2014
> >> >> > > > Optimistic Release Date: May 19, 2014
> >> >> > > >
> >> >> > > > Cheers,
> >> >> > > >
> >> >> > > > Hugo
> >> >> > > >
> >> >> > > >
> >> >> > > > On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> >> >> > > > <su...@citrix.com>
> >> >> > > > wrote:
> >> >> > > >
> >> >> > > > > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540>
> |
> >> >>M:
> >> >> > > > +44<tel:+447968161581> 7788 423 969
> >> >> > > > >
> >> >> > > > > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
> 4HS
> >> >> > > > >
> >> >> > > > > Need Enterprise Grade Support for Apache CloudStack?
> >> >> > > > > Our CloudStack Infrastructure
> >> >> > > > > Support<http://shapeblue.com/cloudstack-
> >> >> > > > infrastructure-support/> offers the best 24/7 SLA for
> CloudStack
> >> >> > > > Environments.
> >> >> > > > >
> >> >> > > > > Apache CloudStack Bootcamp training courses
> >> >> > > > >
> >> >> > > > > **NEW!** CloudStack 4.2.1
> >> >> > > > > training<http://shapeblue.com/cloudstack-
> >> >> > > > training/>
> >> >> > > > > 18th-19th February 2014, Brazil.
> >> >> > > > Classroom<http://shapeblue.com/cloudstack-training/>
> >> >> > > > > 17th-23rd March 2014, Region A. Instructor led, On-
> >> >> > > > line<http://shapeblue.com/cloudstack-training/>
> >> >> > > > > 24th-28th March 2014, Region B. Instructor led, On-
> >> >> > > > line<http://shapeblue.com/cloudstack-training/>
> >> >> > > > > 16th-20th June 2014, Region A. Instructor led, On-
> >> >> > > > line<http://shapeblue.com/cloudstack-training/>
> >> >> > > > > 23rd-27th June 2014, Region B. Instructor led, On-
> >> >> > > > line<http://shapeblue.com/cloudstack-training/>
> >> >> > > > >
> >> >> > > > > This email and any attachments to it may be confidential and
> are
> >> >> > > > > intended
> >> >> > > > solely for the use of the individual to whom it is addressed.
> Any
> >> >> > > > views or opinions expressed are solely those of the author and
> do
> >> >> > > > not necessarily represent those of Shape Blue Ltd or related
> >> >> > > > companies. If you are not the intended recipient of this email,
> >> >> > > > you must neither take any action based upon its contents, nor
> copy
> >> >> > > > or show it to anyone. Please contact the sender if you believe
> you
> >> >> > > > have received this email in error. Shape Blue Ltd is a company
> >> >> > > > incorporated in England & Wales. ShapeBlue Services India LLP
> is a
> >> >> > > > company incorporated in India and is operated under license
> from
> >> >> > > > Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company
> >> >> > > > incorporated in Brasil and is operated under license from Shape
> >> >> > > > Blue Ltd. ShapeBlue is
> >> >> > a
> >> >> > > registered trademark.
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >> --
> >> >> *Mike Tutkowski*
> >> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> >> e: mike.tutkowski@solidfire.com
> >> >> o: 303.746.7302
> >> >> Advancing the way the world uses the
> >> >> cloud<http://solidfire.com/solution/overview/?video=play>
> >> >> *(tm)*
> >>
> >>
>
>
>
> --
> Daan
>
Re: 4.4 Feature Freeze
Posted by Daan Hoogland <da...@gmail.com>.
-1 for postponing the feature freeze. It will amount to more features
in the release. I'd rather shorten the cycle and do more releases then
to pack more bugs in a single go.
On Wed, Feb 26, 2014 at 1:13 PM, Guo Star <gh...@gmail.com> wrote:
> +1
>
>
> 2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <Abhinandan.Prateek@citrix.com
>>:
>
>> +1 for 4.4 feature freeze on 3/28.
>>
>> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
>> <sa...@citrix.com> wrote:
>>
>> >> -----Original Message-----
>> >> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>> >
>> >Regards,
>> >Sateesh
>> >
>> >> I also agree we should discuss 4+ month development cycles again.
>> >>
>> >>
>> >> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>> >>animesh.chaturvedi@citrix.com> wrote:
>> >>
>> >> > I will start a separate discussion on 4 month cycle or longer, but
>> >> > wanted to call out one more important date.
>> >> >
>> >> > We have a last day for feature proposal date which is typically a
>> >> > month before feature freeze date. If following 4.3 schedule + 4 month
>> >> > it would have been 2/14 and we are already past that. Since it was not
>> >> > announced for
>> >> > 4.4 release yet my suggestion would be to keep feature proposal open
>> >> > for another week and push all the dates out by 2 weeks to give folks
>> >> > opportunity to finish up their features for new proposals that are yet
>> >> > to come out.
>> >> >
>> >> > To be clear that would mean pushing out feature freeze to 3/28 from
>> >> > 3/14 and all the other dates likewise.
>> >> >
>> >> >
>> >> > Thanks
>> >> > Animesh
>> >> >
>> >> > > -----Original Message-----
>> >> > > From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
>> >> > > Sent: Tuesday, February 25, 2014 1:05 PM
>> >> > > To: dev@cloudstack.apache.org
>> >> > > Subject: RE: 4.4 Feature Freeze
>> >> > >
>> >> > > With the experience of 4.2 and 4.3 I think we should discuss if we
>> >> > > can realistically achieve 4 month cycle our RCs take 2 months. I was
>> >> > > going to open up the discussion after 4.3 is shipped though.
>> >> > >
>> >> > > > -----Original Message-----
>> >> > > > From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
>> >> > > > Trippaers
>> >> > > > Sent: Tuesday, February 25, 2014 8:50 AM
>> >> > > > To: <de...@cloudstack.apache.org>
>> >> > > > 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.
>> >> > > >
>> >> > > > So the proposed release schedule for 4.4 would look like this
>> >> > > > (dates slightly modified to take efficiency and RM's personal life
>> >> > > > into
>> >> > account ;-) ):
>> >> > > >
>> >> > > > Feature Freeze: March 14, 2014
>> >> > > > Testing/Bug Fixes: March 15, 2014 till April 18,
>> >>2014
>> >> > > > (direct access for committers)
>> >> > > > Stability Fixes only: April 19, 2014 till
>> >> > release (cherry picks
>> >> > > > by RM only)
>> >> > > > First RC: May 9, 2014
>> >> > > > Optimistic Release Date: May 19, 2014
>> >> > > >
>> >> > > > Cheers,
>> >> > > >
>> >> > > > Hugo
>> >> > > >
>> >> > > >
>> >> > > > On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>> >> > > > <su...@citrix.com>
>> >> > > > wrote:
>> >> > > >
>> >> > > > > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> |
>> >>M:
>> >> > > > +44<tel:+447968161581> 7788 423 969
>> >> > > > >
>> >> > > > > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
>> >> > > > >
>> >> > > > > Need Enterprise Grade Support for Apache CloudStack?
>> >> > > > > Our CloudStack Infrastructure
>> >> > > > > Support<http://shapeblue.com/cloudstack-
>> >> > > > infrastructure-support/> offers the best 24/7 SLA for CloudStack
>> >> > > > Environments.
>> >> > > > >
>> >> > > > > Apache CloudStack Bootcamp training courses
>> >> > > > >
>> >> > > > > **NEW!** CloudStack 4.2.1
>> >> > > > > training<http://shapeblue.com/cloudstack-
>> >> > > > training/>
>> >> > > > > 18th-19th February 2014, Brazil.
>> >> > > > Classroom<http://shapeblue.com/cloudstack-training/>
>> >> > > > > 17th-23rd March 2014, Region A. Instructor led, On-
>> >> > > > line<http://shapeblue.com/cloudstack-training/>
>> >> > > > > 24th-28th March 2014, Region B. Instructor led, On-
>> >> > > > line<http://shapeblue.com/cloudstack-training/>
>> >> > > > > 16th-20th June 2014, Region A. Instructor led, On-
>> >> > > > line<http://shapeblue.com/cloudstack-training/>
>> >> > > > > 23rd-27th June 2014, Region B. Instructor led, On-
>> >> > > > line<http://shapeblue.com/cloudstack-training/>
>> >> > > > >
>> >> > > > > This email and any attachments to it may be confidential and are
>> >> > > > > intended
>> >> > > > solely for the use of the individual to whom it is addressed. Any
>> >> > > > views or opinions expressed are solely those of the author and do
>> >> > > > not necessarily represent those of Shape Blue Ltd or related
>> >> > > > companies. If you are not the intended recipient of this email,
>> >> > > > you must neither take any action based upon its contents, nor copy
>> >> > > > or show it to anyone. Please contact the sender if you believe you
>> >> > > > have received this email in error. Shape Blue Ltd is a company
>> >> > > > incorporated in England & Wales. ShapeBlue Services India LLP is a
>> >> > > > company incorporated in India and is operated under license from
>> >> > > > Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company
>> >> > > > incorporated in Brasil and is operated under license from Shape
>> >> > > > Blue Ltd. ShapeBlue is
>> >> > a
>> >> > > registered trademark.
>> >> >
>> >> >
>> >>
>> >>
>> >> --
>> >> *Mike Tutkowski*
>> >> *Senior CloudStack Developer, SolidFire Inc.*
>> >> e: mike.tutkowski@solidfire.com
>> >> o: 303.746.7302
>> >> Advancing the way the world uses the
>> >> cloud<http://solidfire.com/solution/overview/?video=play>
>> >> *(tm)*
>>
>>
--
Daan
Re: 4.4 Feature Freeze
Posted by Guo Star <gh...@gmail.com>.
+1
2014-02-26 20:01 GMT+08:00 Abhinandan Prateek <Abhinandan.Prateek@citrix.com
>:
> +1 for 4.4 feature freeze on 3/28.
>
> On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
> <sa...@citrix.com> wrote:
>
> >> -----Original Message-----
> >> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
> >
> >Regards,
> >Sateesh
> >
> >> I also agree we should discuss 4+ month development cycles again.
> >>
> >>
> >> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
> >>animesh.chaturvedi@citrix.com> wrote:
> >>
> >> > I will start a separate discussion on 4 month cycle or longer, but
> >> > wanted to call out one more important date.
> >> >
> >> > We have a last day for feature proposal date which is typically a
> >> > month before feature freeze date. If following 4.3 schedule + 4 month
> >> > it would have been 2/14 and we are already past that. Since it was not
> >> > announced for
> >> > 4.4 release yet my suggestion would be to keep feature proposal open
> >> > for another week and push all the dates out by 2 weeks to give folks
> >> > opportunity to finish up their features for new proposals that are yet
> >> > to come out.
> >> >
> >> > To be clear that would mean pushing out feature freeze to 3/28 from
> >> > 3/14 and all the other dates likewise.
> >> >
> >> >
> >> > Thanks
> >> > Animesh
> >> >
> >> > > -----Original Message-----
> >> > > From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> >> > > Sent: Tuesday, February 25, 2014 1:05 PM
> >> > > To: dev@cloudstack.apache.org
> >> > > Subject: RE: 4.4 Feature Freeze
> >> > >
> >> > > With the experience of 4.2 and 4.3 I think we should discuss if we
> >> > > can realistically achieve 4 month cycle our RCs take 2 months. I was
> >> > > going to open up the discussion after 4.3 is shipped though.
> >> > >
> >> > > > -----Original Message-----
> >> > > > From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
> >> > > > Trippaers
> >> > > > Sent: Tuesday, February 25, 2014 8:50 AM
> >> > > > To: <de...@cloudstack.apache.org>
> >> > > > 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.
> >> > > >
> >> > > > So the proposed release schedule for 4.4 would look like this
> >> > > > (dates slightly modified to take efficiency and RM's personal life
> >> > > > into
> >> > account ;-) ):
> >> > > >
> >> > > > Feature Freeze: March 14, 2014
> >> > > > Testing/Bug Fixes: March 15, 2014 till April 18,
> >>2014
> >> > > > (direct access for committers)
> >> > > > Stability Fixes only: April 19, 2014 till
> >> > release (cherry picks
> >> > > > by RM only)
> >> > > > First RC: May 9, 2014
> >> > > > Optimistic Release Date: May 19, 2014
> >> > > >
> >> > > > Cheers,
> >> > > >
> >> > > > Hugo
> >> > > >
> >> > > >
> >> > > > On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> >> > > > <su...@citrix.com>
> >> > > > wrote:
> >> > > >
> >> > > > > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> |
> >>M:
> >> > > > +44<tel:+447968161581> 7788 423 969
> >> > > > >
> >> > > > > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
> >> > > > >
> >> > > > > Need Enterprise Grade Support for Apache CloudStack?
> >> > > > > Our CloudStack Infrastructure
> >> > > > > Support<http://shapeblue.com/cloudstack-
> >> > > > infrastructure-support/> offers the best 24/7 SLA for CloudStack
> >> > > > Environments.
> >> > > > >
> >> > > > > Apache CloudStack Bootcamp training courses
> >> > > > >
> >> > > > > **NEW!** CloudStack 4.2.1
> >> > > > > training<http://shapeblue.com/cloudstack-
> >> > > > training/>
> >> > > > > 18th-19th February 2014, Brazil.
> >> > > > Classroom<http://shapeblue.com/cloudstack-training/>
> >> > > > > 17th-23rd March 2014, Region A. Instructor led, On-
> >> > > > line<http://shapeblue.com/cloudstack-training/>
> >> > > > > 24th-28th March 2014, Region B. Instructor led, On-
> >> > > > line<http://shapeblue.com/cloudstack-training/>
> >> > > > > 16th-20th June 2014, Region A. Instructor led, On-
> >> > > > line<http://shapeblue.com/cloudstack-training/>
> >> > > > > 23rd-27th June 2014, Region B. Instructor led, On-
> >> > > > line<http://shapeblue.com/cloudstack-training/>
> >> > > > >
> >> > > > > This email and any attachments to it may be confidential and are
> >> > > > > intended
> >> > > > solely for the use of the individual to whom it is addressed. Any
> >> > > > views or opinions expressed are solely those of the author and do
> >> > > > not necessarily represent those of Shape Blue Ltd or related
> >> > > > companies. If you are not the intended recipient of this email,
> >> > > > you must neither take any action based upon its contents, nor copy
> >> > > > or show it to anyone. Please contact the sender if you believe you
> >> > > > have received this email in error. Shape Blue Ltd is a company
> >> > > > incorporated in England & Wales. ShapeBlue Services India LLP is a
> >> > > > company incorporated in India and is operated under license from
> >> > > > Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company
> >> > > > incorporated in Brasil and is operated under license from Shape
> >> > > > Blue Ltd. ShapeBlue is
> >> > a
> >> > > registered trademark.
> >> >
> >> >
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkowski@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >> cloud<http://solidfire.com/solution/overview/?video=play>
> >> *(tm)*
>
>
Re: 4.4 Feature Freeze
Posted by Abhinandan Prateek <Ab...@citrix.com>.
+1 for 4.4 feature freeze on 3/28.
On 26/02/14 10:01 am, "Sateesh Chodapuneedi"
<sa...@citrix.com> wrote:
>> -----Original Message-----
>> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
>
>Regards,
>Sateesh
>
>> I also agree we should discuss 4+ month development cycles again.
>>
>>
>> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
>>animesh.chaturvedi@citrix.com> wrote:
>>
>> > I will start a separate discussion on 4 month cycle or longer, but
>> > wanted to call out one more important date.
>> >
>> > We have a last day for feature proposal date which is typically a
>> > month before feature freeze date. If following 4.3 schedule + 4 month
>> > it would have been 2/14 and we are already past that. Since it was not
>> > announced for
>> > 4.4 release yet my suggestion would be to keep feature proposal open
>> > for another week and push all the dates out by 2 weeks to give folks
>> > opportunity to finish up their features for new proposals that are yet
>> > to come out.
>> >
>> > To be clear that would mean pushing out feature freeze to 3/28 from
>> > 3/14 and all the other dates likewise.
>> >
>> >
>> > Thanks
>> > Animesh
>> >
>> > > -----Original Message-----
>> > > From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
>> > > Sent: Tuesday, February 25, 2014 1:05 PM
>> > > To: dev@cloudstack.apache.org
>> > > Subject: RE: 4.4 Feature Freeze
>> > >
>> > > With the experience of 4.2 and 4.3 I think we should discuss if we
>> > > can realistically achieve 4 month cycle our RCs take 2 months. I was
>> > > going to open up the discussion after 4.3 is shipped though.
>> > >
>> > > > -----Original Message-----
>> > > > From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
>> > > > Trippaers
>> > > > Sent: Tuesday, February 25, 2014 8:50 AM
>> > > > To: <de...@cloudstack.apache.org>
>> > > > 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.
>> > > >
>> > > > So the proposed release schedule for 4.4 would look like this
>> > > > (dates slightly modified to take efficiency and RM's personal life
>> > > > into
>> > account ;-) ):
>> > > >
>> > > > Feature Freeze: March 14, 2014
>> > > > Testing/Bug Fixes: March 15, 2014 till April 18,
>>2014
>> > > > (direct access for committers)
>> > > > Stability Fixes only: April 19, 2014 till
>> > release (cherry picks
>> > > > by RM only)
>> > > > First RC: May 9, 2014
>> > > > Optimistic Release Date: May 19, 2014
>> > > >
>> > > > Cheers,
>> > > >
>> > > > Hugo
>> > > >
>> > > >
>> > > > On 25 feb. 2014, at 16:35, Sudha Ponnaganti
>> > > > <su...@citrix.com>
>> > > > wrote:
>> > > >
>> > > > > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> |
>>M:
>> > > > +44<tel:+447968161581> 7788 423 969
>> > > > >
>> > > > > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
>> > > > >
>> > > > > Need Enterprise Grade Support for Apache CloudStack?
>> > > > > Our CloudStack Infrastructure
>> > > > > Support<http://shapeblue.com/cloudstack-
>> > > > infrastructure-support/> offers the best 24/7 SLA for CloudStack
>> > > > Environments.
>> > > > >
>> > > > > Apache CloudStack Bootcamp training courses
>> > > > >
>> > > > > **NEW!** CloudStack 4.2.1
>> > > > > training<http://shapeblue.com/cloudstack-
>> > > > training/>
>> > > > > 18th-19th February 2014, Brazil.
>> > > > Classroom<http://shapeblue.com/cloudstack-training/>
>> > > > > 17th-23rd March 2014, Region A. Instructor led, On-
>> > > > line<http://shapeblue.com/cloudstack-training/>
>> > > > > 24th-28th March 2014, Region B. Instructor led, On-
>> > > > line<http://shapeblue.com/cloudstack-training/>
>> > > > > 16th-20th June 2014, Region A. Instructor led, On-
>> > > > line<http://shapeblue.com/cloudstack-training/>
>> > > > > 23rd-27th June 2014, Region B. Instructor led, On-
>> > > > line<http://shapeblue.com/cloudstack-training/>
>> > > > >
>> > > > > This email and any attachments to it may be confidential and are
>> > > > > intended
>> > > > solely for the use of the individual to whom it is addressed. Any
>> > > > views or opinions expressed are solely those of the author and do
>> > > > not necessarily represent those of Shape Blue Ltd or related
>> > > > companies. If you are not the intended recipient of this email,
>> > > > you must neither take any action based upon its contents, nor copy
>> > > > or show it to anyone. Please contact the sender if you believe you
>> > > > have received this email in error. Shape Blue Ltd is a company
>> > > > incorporated in England & Wales. ShapeBlue Services India LLP is a
>> > > > company incorporated in India and is operated under license from
>> > > > Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company
>> > > > incorporated in Brasil and is operated under license from Shape
>> > > > Blue Ltd. ShapeBlue is
>> > a
>> > > registered trademark.
>> >
>> >
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud<http://solidfire.com/solution/overview/?video=play>
>> *(tm)*
RE: 4.4 Feature Freeze
Posted by Sateesh Chodapuneedi <sa...@citrix.com>.
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@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 move 4.4 feature freeze date to 3/28.
Regards,
Sateesh
> I also agree we should discuss 4+ month development cycles again.
>
>
> On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi < animesh.chaturvedi@citrix.com> wrote:
>
> > I will start a separate discussion on 4 month cycle or longer, but
> > wanted to call out one more important date.
> >
> > We have a last day for feature proposal date which is typically a
> > month before feature freeze date. If following 4.3 schedule + 4 month
> > it would have been 2/14 and we are already past that. Since it was not
> > announced for
> > 4.4 release yet my suggestion would be to keep feature proposal open
> > for another week and push all the dates out by 2 weeks to give folks
> > opportunity to finish up their features for new proposals that are yet
> > to come out.
> >
> > To be clear that would mean pushing out feature freeze to 3/28 from
> > 3/14 and all the other dates likewise.
> >
> >
> > Thanks
> > Animesh
> >
> > > -----Original Message-----
> > > From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> > > Sent: Tuesday, February 25, 2014 1:05 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: RE: 4.4 Feature Freeze
> > >
> > > With the experience of 4.2 and 4.3 I think we should discuss if we
> > > can realistically achieve 4 month cycle our RCs take 2 months. I was
> > > going to open up the discussion after 4.3 is shipped though.
> > >
> > > > -----Original Message-----
> > > > From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo
> > > > Trippaers
> > > > Sent: Tuesday, February 25, 2014 8:50 AM
> > > > To: <de...@cloudstack.apache.org>
> > > > 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.
> > > >
> > > > So the proposed release schedule for 4.4 would look like this
> > > > (dates slightly modified to take efficiency and RM's personal life
> > > > into
> > account ;-) ):
> > > >
> > > > Feature Freeze: March 14, 2014
> > > > Testing/Bug Fixes: March 15, 2014 till April 18, 2014
> > > > (direct access for committers)
> > > > Stability Fixes only: April 19, 2014 till
> > release (cherry picks
> > > > by RM only)
> > > > First RC: May 9, 2014
> > > > Optimistic Release Date: May 19, 2014
> > > >
> > > > Cheers,
> > > >
> > > > Hugo
> > > >
> > > >
> > > > On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > > > <su...@citrix.com>
> > > > wrote:
> > > >
> > > > > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M:
> > > > +44<tel:+447968161581> 7788 423 969
> > > > >
> > > > > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
> > > > >
> > > > > Need Enterprise Grade Support for Apache CloudStack?
> > > > > Our CloudStack Infrastructure
> > > > > Support<http://shapeblue.com/cloudstack-
> > > > infrastructure-support/> offers the best 24/7 SLA for CloudStack
> > > > Environments.
> > > > >
> > > > > Apache CloudStack Bootcamp training courses
> > > > >
> > > > > **NEW!** CloudStack 4.2.1
> > > > > training<http://shapeblue.com/cloudstack-
> > > > training/>
> > > > > 18th-19th February 2014, Brazil.
> > > > Classroom<http://shapeblue.com/cloudstack-training/>
> > > > > 17th-23rd March 2014, Region A. Instructor led, On-
> > > > line<http://shapeblue.com/cloudstack-training/>
> > > > > 24th-28th March 2014, Region B. Instructor led, On-
> > > > line<http://shapeblue.com/cloudstack-training/>
> > > > > 16th-20th June 2014, Region A. Instructor led, On-
> > > > line<http://shapeblue.com/cloudstack-training/>
> > > > > 23rd-27th June 2014, Region B. Instructor led, On-
> > > > line<http://shapeblue.com/cloudstack-training/>
> > > > >
> > > > > This email and any attachments to it may be confidential and are
> > > > > intended
> > > > solely for the use of the individual to whom it is addressed. Any
> > > > views or opinions expressed are solely those of the author and do
> > > > not necessarily represent those of Shape Blue Ltd or related
> > > > companies. If you are not the intended recipient of this email,
> > > > you must neither take any action based upon its contents, nor copy
> > > > or show it to anyone. Please contact the sender if you believe you
> > > > have received this email in error. Shape Blue Ltd is a company
> > > > incorporated in England & Wales. ShapeBlue Services India LLP is a
> > > > company incorporated in India and is operated under license from
> > > > Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company
> > > > incorporated in Brasil and is operated under license from Shape
> > > > Blue Ltd. ShapeBlue is
> > a
> > > registered trademark.
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
I think this is a good idea, Animesh (to push out feature freeze to 3/28).
I also agree we should discuss 4+ month development cycles again.
On Tue, Feb 25, 2014 at 3:43 PM, Animesh Chaturvedi <
animesh.chaturvedi@citrix.com> wrote:
> I will start a separate discussion on 4 month cycle or longer, but wanted
> to call out one more important date.
>
> We have a last day for feature proposal date which is typically a month
> before feature freeze date. If following 4.3 schedule + 4 month it would
> have been 2/14 and we are already past that. Since it was not announced for
> 4.4 release yet my suggestion would be to keep feature proposal open for
> another week and push all the dates out by 2 weeks to give folks
> opportunity to finish up their features for new proposals that are yet to
> come out.
>
> To be clear that would mean pushing out feature freeze to 3/28 from 3/14
> and all the other dates likewise.
>
>
> Thanks
> Animesh
>
> > -----Original Message-----
> > From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> > Sent: Tuesday, February 25, 2014 1:05 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: 4.4 Feature Freeze
> >
> > With the experience of 4.2 and 4.3 I think we should discuss if we can
> > realistically achieve 4 month cycle our RCs take 2 months. I was going to
> > open up the discussion after 4.3 is shipped though.
> >
> > > -----Original Message-----
> > > From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo Trippaers
> > > Sent: Tuesday, February 25, 2014 8:50 AM
> > > To: <de...@cloudstack.apache.org>
> > > 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.
> > >
> > > So the proposed release schedule for 4.4 would look like this (dates
> > > slightly modified to take efficiency and RM's personal life into
> account ;-) ):
> > >
> > > Feature Freeze: March 14, 2014
> > > Testing/Bug Fixes: March 15, 2014 till April 18, 2014
> > > (direct access for committers)
> > > Stability Fixes only: April 19, 2014 till
> release (cherry picks
> > > by RM only)
> > > First RC: May 9, 2014
> > > Optimistic Release Date: May 19, 2014
> > >
> > > Cheers,
> > >
> > > Hugo
> > >
> > >
> > > On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > > <su...@citrix.com>
> > > wrote:
> > >
> > > > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M:
> > > +44<tel:+447968161581> 7788 423 969
> > > >
> > > > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
> > > >
> > > > Need Enterprise Grade Support for Apache CloudStack?
> > > > Our CloudStack Infrastructure
> > > > Support<http://shapeblue.com/cloudstack-
> > > infrastructure-support/> offers the best 24/7 SLA for CloudStack
> > > Environments.
> > > >
> > > > Apache CloudStack Bootcamp training courses
> > > >
> > > > **NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-
> > > training/>
> > > > 18th-19th February 2014, Brazil.
> > > Classroom<http://shapeblue.com/cloudstack-training/>
> > > > 17th-23rd March 2014, Region A. Instructor led, On-
> > > line<http://shapeblue.com/cloudstack-training/>
> > > > 24th-28th March 2014, Region B. Instructor led, On-
> > > line<http://shapeblue.com/cloudstack-training/>
> > > > 16th-20th June 2014, Region A. Instructor led, On-
> > > line<http://shapeblue.com/cloudstack-training/>
> > > > 23rd-27th June 2014, Region B. Instructor led, On-
> > > line<http://shapeblue.com/cloudstack-training/>
> > > >
> > > > This email and any attachments to it may be confidential and are
> > > > intended
> > > solely for the use of the individual to whom it is addressed. Any
> > > views or opinions expressed are solely those of the author and do not
> > > necessarily represent those of Shape Blue Ltd or related companies. If
> > > you are not the intended recipient of this email, you must neither
> > > take any action based upon its contents, nor copy or show it to
> > > anyone. Please contact the sender if you believe you have received
> > > this email in error. Shape Blue Ltd is a company incorporated in
> > > England & Wales. ShapeBlue Services India LLP is a company
> > > incorporated in India and is operated under license from Shape Blue
> > > Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> > > Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is
> a
> > registered trademark.
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
RE: 4.4 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
I will start a separate discussion on 4 month cycle or longer, but wanted to call out one more important date.
We have a last day for feature proposal date which is typically a month before feature freeze date. If following 4.3 schedule + 4 month it would have been 2/14 and we are already past that. Since it was not announced for 4.4 release yet my suggestion would be to keep feature proposal open for another week and push all the dates out by 2 weeks to give folks opportunity to finish up their features for new proposals that are yet to come out.
To be clear that would mean pushing out feature freeze to 3/28 from 3/14 and all the other dates likewise.
Thanks
Animesh
> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> Sent: Tuesday, February 25, 2014 1:05 PM
> To: dev@cloudstack.apache.org
> Subject: RE: 4.4 Feature Freeze
>
> With the experience of 4.2 and 4.3 I think we should discuss if we can
> realistically achieve 4 month cycle our RCs take 2 months. I was going to
> open up the discussion after 4.3 is shipped though.
>
> > -----Original Message-----
> > From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo Trippaers
> > Sent: Tuesday, February 25, 2014 8:50 AM
> > To: <de...@cloudstack.apache.org>
> > 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.
> >
> > So the proposed release schedule for 4.4 would look like this (dates
> > slightly modified to take efficiency and RM's personal life into account ;-) ):
> >
> > Feature Freeze: March 14, 2014
> > Testing/Bug Fixes: March 15, 2014 till April 18, 2014
> > (direct access for committers)
> > Stability Fixes only: April 19, 2014 till release (cherry picks
> > by RM only)
> > First RC: May 9, 2014
> > Optimistic Release Date: May 19, 2014
> >
> > Cheers,
> >
> > Hugo
> >
> >
> > On 25 feb. 2014, at 16:35, Sudha Ponnaganti
> > <su...@citrix.com>
> > wrote:
> >
> > > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M:
> > +44<tel:+447968161581> 7788 423 969
> > >
> > > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
> > >
> > > Need Enterprise Grade Support for Apache CloudStack?
> > > Our CloudStack Infrastructure
> > > Support<http://shapeblue.com/cloudstack-
> > infrastructure-support/> offers the best 24/7 SLA for CloudStack
> > Environments.
> > >
> > > Apache CloudStack Bootcamp training courses
> > >
> > > **NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-
> > training/>
> > > 18th-19th February 2014, Brazil.
> > Classroom<http://shapeblue.com/cloudstack-training/>
> > > 17th-23rd March 2014, Region A. Instructor led, On-
> > line<http://shapeblue.com/cloudstack-training/>
> > > 24th-28th March 2014, Region B. Instructor led, On-
> > line<http://shapeblue.com/cloudstack-training/>
> > > 16th-20th June 2014, Region A. Instructor led, On-
> > line<http://shapeblue.com/cloudstack-training/>
> > > 23rd-27th June 2014, Region B. Instructor led, On-
> > line<http://shapeblue.com/cloudstack-training/>
> > >
> > > This email and any attachments to it may be confidential and are
> > > intended
> > solely for the use of the individual to whom it is addressed. Any
> > views or opinions expressed are solely those of the author and do not
> > necessarily represent those of Shape Blue Ltd or related companies. If
> > you are not the intended recipient of this email, you must neither
> > take any action based upon its contents, nor copy or show it to
> > anyone. Please contact the sender if you believe you have received
> > this email in error. Shape Blue Ltd is a company incorporated in
> > England & Wales. ShapeBlue Services India LLP is a company
> > incorporated in India and is operated under license from Shape Blue
> > Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> > Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a
> registered trademark.
RE: 4.4 Feature Freeze
Posted by Animesh Chaturvedi <an...@citrix.com>.
With the experience of 4.2 and 4.3 I think we should discuss if we can realistically achieve 4 month cycle our RCs take 2 months. I was going to open up the discussion after 4.3 is shipped though.
> -----Original Message-----
> From: Trippie [mailto:trippie@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Tuesday, February 25, 2014 8:50 AM
> To: <de...@cloudstack.apache.org>
> 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.
>
> So the proposed release schedule for 4.4 would look like this (dates slightly
> modified to take efficiency and RM's personal life into account ;-) ):
>
> Feature Freeze: March 14, 2014
> Testing/Bug Fixes: March 15, 2014 till April 18, 2014
> (direct access for committers)
> Stability Fixes only: April 19, 2014 till release (cherry picks
> by RM only)
> First RC: May 9, 2014
> Optimistic Release Date: May 19, 2014
>
> Cheers,
>
> Hugo
>
>
> On 25 feb. 2014, at 16:35, Sudha Ponnaganti <su...@citrix.com>
> wrote:
>
> > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M:
> +44<tel:+447968161581> 7788 423 969
> >
> > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
> >
> > Need Enterprise Grade Support for Apache CloudStack?
> > Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-
> infrastructure-support/> offers the best 24/7 SLA for CloudStack
> Environments.
> >
> > Apache CloudStack Bootcamp training courses
> >
> > **NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-
> training/>
> > 18th-19th February 2014, Brazil.
> Classroom<http://shapeblue.com/cloudstack-training/>
> > 17th-23rd March 2014, Region A. Instructor led, On-
> line<http://shapeblue.com/cloudstack-training/>
> > 24th-28th March 2014, Region B. Instructor led, On-
> line<http://shapeblue.com/cloudstack-training/>
> > 16th-20th June 2014, Region A. Instructor led, On-
> line<http://shapeblue.com/cloudstack-training/>
> > 23rd-27th June 2014, Region B. Instructor led, On-
> line<http://shapeblue.com/cloudstack-training/>
> >
> > This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape
> Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a
> registered trademark.
Re: 4.4 Feature Freeze
Posted by Mike Tutkowski <mi...@solidfire.com>.
That would be the way to go - yes.
On Tue, Feb 25, 2014 at 1:06 PM, Will Stevens <ws...@cloudops.com> wrote:
> If we plan to add a feature to 4.4, should the patch be based off the
> current master (which is currently setup for 4.4)?
>
> Thanks,
>
> Will
>
>
> On Tue, Feb 25, 2014 at 11:50 AM, Hugo Trippaers <hu...@trippaers.nl>
> wrote:
>
> > 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.
> >
> > So the proposed release schedule for 4.4 would look like this (dates
> > slightly modified to take efficiency and RM's personal life into account
> > ;-) ):
> >
> > Feature Freeze: March 14, 2014
> > Testing/Bug Fixes: March 15, 2014 till April 18,
> 2014
> > (direct access for committers)
> > Stability Fixes only: April 19, 2014 till release
> > (cherry picks by RM only)
> > First RC: May 9, 2014
> > Optimistic Release Date: May 19, 2014
> >
> > Cheers,
> >
> > Hugo
> >
> >
> > On 25 feb. 2014, at 16:35, Sudha Ponnaganti <sudha.ponnaganti@citrix.com
> >
> > wrote:
> >
> > > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M:
> > +44<tel:+447968161581> 7788 423 969
> > >
> > > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
> > >
> > > Need Enterprise Grade Support for Apache CloudStack?
> > > Our CloudStack Infrastructure Support<
> > http://shapeblue.com/cloudstack-infrastructure-support/> offers the best
> > 24/7 SLA for CloudStack Environments.
> > >
> > > Apache CloudStack Bootcamp training courses
> > >
> > > **NEW!** CloudStack 4.2.1 training<
> > http://shapeblue.com/cloudstack-training/>
> > > 18th-19th February 2014, Brazil. Classroom<
> > http://shapeblue.com/cloudstack-training/>
> > > 17th-23rd March 2014, Region A. Instructor led, On-line<
> > http://shapeblue.com/cloudstack-training/>
> > > 24th-28th March 2014, Region B. Instructor led, On-line<
> > http://shapeblue.com/cloudstack-training/>
> > > 16th-20th June 2014, Region A. Instructor led, On-line<
> > http://shapeblue.com/cloudstack-training/>
> > > 23rd-27th June 2014, Region B. Instructor led, On-line<
> > http://shapeblue.com/cloudstack-training/>
> > >
> > > This email and any attachments to it may be confidential and are
> > intended solely for the use of the individual to whom it is addressed.
> Any
> > views or opinions expressed are solely those of the author and do not
> > necessarily represent those of Shape Blue Ltd or related companies. If
> you
> > are not the intended recipient of this email, you must neither take any
> > action based upon its contents, nor copy or show it to anyone. Please
> > contact the sender if you believe you have received this email in error.
> > Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
> > Services India LLP is a company incorporated in India and is operated
> under
> > license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > company incorporated in Brasil and is operated under license from Shape
> > Blue Ltd. ShapeBlue is a registered trademark.
> >
> >
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*
Re: 4.4 Feature Freeze
Posted by Will Stevens <ws...@cloudops.com>.
If we plan to add a feature to 4.4, should the patch be based off the
current master (which is currently setup for 4.4)?
Thanks,
Will
On Tue, Feb 25, 2014 at 11:50 AM, Hugo Trippaers <hu...@trippaers.nl> wrote:
> 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.
>
> So the proposed release schedule for 4.4 would look like this (dates
> slightly modified to take efficiency and RM's personal life into account
> ;-) ):
>
> Feature Freeze: March 14, 2014
> Testing/Bug Fixes: March 15, 2014 till April 18, 2014
> (direct access for committers)
> Stability Fixes only: April 19, 2014 till release
> (cherry picks by RM only)
> First RC: May 9, 2014
> Optimistic Release Date: May 19, 2014
>
> Cheers,
>
> Hugo
>
>
> On 25 feb. 2014, at 16:35, Sudha Ponnaganti <su...@citrix.com>
> wrote:
>
> > 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M:
> +44<tel:+447968161581> 7788 423 969
> >
> > ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
> >
> > Need Enterprise Grade Support for Apache CloudStack?
> > Our CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/> offers the best
> 24/7 SLA for CloudStack Environments.
> >
> > Apache CloudStack Bootcamp training courses
> >
> > **NEW!** CloudStack 4.2.1 training<
> http://shapeblue.com/cloudstack-training/>
> > 18th-19th February 2014, Brazil. Classroom<
> http://shapeblue.com/cloudstack-training/>
> > 17th-23rd March 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> > 24th-28th March 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> > 16th-20th June 2014, Region A. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> > 23rd-27th June 2014, Region B. Instructor led, On-line<
> http://shapeblue.com/cloudstack-training/>
> >
> > This email and any attachments to it may be confidential and are
> intended solely for the use of the individual to whom it is addressed. Any
> views or opinions expressed are solely those of the author and do not
> necessarily represent those of Shape Blue Ltd or related companies. If you
> are not the intended recipient of this email, you must neither take any
> action based upon its contents, nor copy or show it to anyone. Please
> contact the sender if you believe you have received this email in error.
> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
> Services India LLP is a company incorporated in India and is operated under
> license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> company incorporated in Brasil and is operated under license from Shape
> Blue Ltd. ShapeBlue is a registered trademark.
>
>
Re: 4.4 Feature Freeze
Posted by David Nalley <da...@gnsa.us>.
Even better :)
On Tue, Feb 25, 2014 at 3:30 PM, Daan Hoogland <da...@gmail.com> wrote:
> I think Hugo stepped up (incriminating me in the process). I will talk
> to him about sharing the burdon for both the releases.
>
> On Tue, Feb 25, 2014 at 6:02 PM, David Nalley <da...@gnsa.us> wrote:
>> Though I'll point out no one has stepped up to RM 4.4 (or 4.3.1). If
>> all else fails and no one else steps up, I'll take 4.4, though I'd
>> prefer someone else do so.
>>
>> --David
>>
>> On Tue, Feb 25, 2014 at 11:50 AM, Hugo Trippaers <hu...@trippaers.nl> wrote:
>>> 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.
>>>
>>> So the proposed release schedule for 4.4 would look like this (dates slightly modified to take efficiency and RM's personal life into account ;-) ):
>>>
>>> Feature Freeze: March 14, 2014
>>> Testing/Bug Fixes: March 15, 2014 till April 18, 2014 (direct access for committers)
>>> Stability Fixes only: April 19, 2014 till release (cherry picks by RM only)
>>> First RC: May 9, 2014
>>> Optimistic Release Date: May 19, 2014
>>>
>>> Cheers,
>>>
>>> Hugo
>>>
>>>
>>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti <su...@citrix.com> wrote:
>>>
>>>> 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M: +44<tel:+447968161581> 7788 423 969
>>>>
>>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
>>>>
>>>> Need Enterprise Grade Support for Apache CloudStack?
>>>> Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments.
>>>>
>>>> Apache CloudStack Bootcamp training courses
>>>>
>>>> **NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/>
>>>> 18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/>
>>>> 17th-23rd March 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>>>> 24th-28th March 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>>>> 16th-20th June 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>>>> 23rd-27th June 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>>>>
>>>> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>>
>
>
>
> --
> Daan
Re: 4.4 Feature Freeze
Posted by Daan Hoogland <da...@gmail.com>.
I think Hugo stepped up (incriminating me in the process). I will talk
to him about sharing the burdon for both the releases.
On Tue, Feb 25, 2014 at 6:02 PM, David Nalley <da...@gnsa.us> wrote:
> Though I'll point out no one has stepped up to RM 4.4 (or 4.3.1). If
> all else fails and no one else steps up, I'll take 4.4, though I'd
> prefer someone else do so.
>
> --David
>
> On Tue, Feb 25, 2014 at 11:50 AM, Hugo Trippaers <hu...@trippaers.nl> wrote:
>> 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.
>>
>> So the proposed release schedule for 4.4 would look like this (dates slightly modified to take efficiency and RM's personal life into account ;-) ):
>>
>> Feature Freeze: March 14, 2014
>> Testing/Bug Fixes: March 15, 2014 till April 18, 2014 (direct access for committers)
>> Stability Fixes only: April 19, 2014 till release (cherry picks by RM only)
>> First RC: May 9, 2014
>> Optimistic Release Date: May 19, 2014
>>
>> Cheers,
>>
>> Hugo
>>
>>
>> On 25 feb. 2014, at 16:35, Sudha Ponnaganti <su...@citrix.com> wrote:
>>
>>> 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M: +44<tel:+447968161581> 7788 423 969
>>>
>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
>>>
>>> Need Enterprise Grade Support for Apache CloudStack?
>>> Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments.
>>>
>>> Apache CloudStack Bootcamp training courses
>>>
>>> **NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/>
>>> 18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/>
>>> 17th-23rd March 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>>> 24th-28th March 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>>> 16th-20th June 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>>> 23rd-27th June 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>>>
>>> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>
--
Daan
Re: 4.4 Feature Freeze
Posted by David Nalley <da...@gnsa.us>.
Though I'll point out no one has stepped up to RM 4.4 (or 4.3.1). If
all else fails and no one else steps up, I'll take 4.4, though I'd
prefer someone else do so.
--David
On Tue, Feb 25, 2014 at 11:50 AM, Hugo Trippaers <hu...@trippaers.nl> wrote:
> 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.
>
> So the proposed release schedule for 4.4 would look like this (dates slightly modified to take efficiency and RM's personal life into account ;-) ):
>
> Feature Freeze: March 14, 2014
> Testing/Bug Fixes: March 15, 2014 till April 18, 2014 (direct access for committers)
> Stability Fixes only: April 19, 2014 till release (cherry picks by RM only)
> First RC: May 9, 2014
> Optimistic Release Date: May 19, 2014
>
> Cheers,
>
> Hugo
>
>
> On 25 feb. 2014, at 16:35, Sudha Ponnaganti <su...@citrix.com> wrote:
>
>> 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M: +44<tel:+447968161581> 7788 423 969
>>
>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
>>
>> Need Enterprise Grade Support for Apache CloudStack?
>> Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments.
>>
>> Apache CloudStack Bootcamp training courses
>>
>> **NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/>
>> 18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/>
>> 17th-23rd March 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>> 24th-28th March 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>> 16th-20th June 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>> 23rd-27th June 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>
Re: 4.4 Feature Freeze
Posted by Hugo Trippaers <hu...@trippaers.nl>.
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.
So the proposed release schedule for 4.4 would look like this (dates slightly modified to take efficiency and RM’s personal life into account ;-) ):
Feature Freeze: March 14, 2014
Testing/Bug Fixes: March 15, 2014 till April 18, 2014 (direct access for committers)
Stability Fixes only: April 19, 2014 till release (cherry picks by RM only)
First RC: May 9, 2014
Optimistic Release Date: May 19, 2014
Cheers,
Hugo
On 25 feb. 2014, at 16:35, Sudha Ponnaganti <su...@citrix.com> wrote:
> 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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M: +44<tel:+447968161581> 7788 423 969
>
> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
>
> Need Enterprise Grade Support for Apache CloudStack?
> Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments.
>
> Apache CloudStack Bootcamp training courses
>
> **NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/>
> 18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/>
> 17th-23rd March 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
> 24th-28th March 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
> 16th-20th June 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
> 23rd-27th June 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
RE: 4.4 Feature Freeze
Posted by Sudha Ponnaganti <su...@citrix.com>.
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.hitchins@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 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 523 587 | S: +44 20 3603 0540<tel:+442036030540> | M: +44<tel:+447968161581> 7788 423 969
ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments.
Apache CloudStack Bootcamp training courses
**NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/>
18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/>
17th-23rd March 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
24th-28th March 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
16th-20th June 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
23rd-27th June 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.