Open Stack

I think three releases is important to keep in support of each DefCore release.  Even though the community no longer supports the third release back, the vendor community has a need to continue to support their customers beyond the length that the OpenStack developer community does.  Especially considering that many vendors look to provide one release per year, or may be multiple months behind in releasing the latest release, it is important to allow the vendors some extra room to satisfy their more conservative customers.  Three releases is 18 months.  That's nothing in Financial Company time or some other industries.  We have to be flexible with enduser support if we are to continue to grow the ecosystem I*and* keep forking to a minimum.

Perhaps in the future, when upgrades are easier and pre release test coverage and quality reports are more available, we can move to two release support, but not while we are still battling to get quality higher and upgrade smoother.

--Rocky

-----Original Message-----
From: Rob Hirschfeld [mailto:rob at zehicle.com] 
Sent: Friday, May 08, 2015 07:35
To: Mark Voelker
Cc: defcore-committee at lists.openstack.org
Subject: Re: [OpenStack-DefCore] May Board Report Draft

Mark,

Thanks.  I put comments in the patch supporting 3 releases as long as 
one is the latest release.  When we get to a regular S+3 cadence, that 
will be very natural.

I don't feel compelled to have a policy about it at this point - we may 
find that 2 are sufficient in the future.

Rob

On 05/08/2015 07:31 AM, Mark Voelker wrote:
> Before 2015.05 goes up for Board approval, we need to finalize the releases covered by the guideline [1].  The 2015.04 spec covered Havana, Icehouse, and Juno [2], so I've posted a patch [3] to drop Havana and add Kilo.  However there's been some discussion in another review [4] about whether we should cover two releases or three going forward.  I don't have particularly strong feelings either way, so I would welcome discussion on the new patch [3] so we can get to consensus.
>
> [1] https://github.com/openstack/defcore/blob/master/2015.next.json#L7
> [2] https://github.com/openstack/defcore/commit/dc9dce4bcbe165967bef8394b6d5b3cdd1535df5
> [3] https://review.openstack.org/#/c/181372/
> [4] https://review.openstack.org/#/c/181137/
>
> At Your Service,
>
> Mark T. Voelker
> OpenStack Architect
>
> On May 7, 2015, at 5:35 PM, Rob Hirschfeld <rob at zehicle.com> wrote:
>
>> DefCore,
>>
>> You are invited to review our draft report for the 2015 May Board meeting.
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_12kUWSWt55Ju-2DokgfEbPt9AH-2D8UzaQoO-5F2KzSOHl5Sg0_edit-3Fusp-3Dsharing&d=AwICAg&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=Q8IhPU-EIzbG5YDx5LYO7zEJpGZykn7RwFg-UTPWvDc&m=znDq0m4Bb3X4F17krVc50lf9Ayh55uxGmLjS7vJbkfE&s=bs936MKSr-Aeu_O42vFGkonlbwgeXwZmVvtqIObP1-g&e=
>>
>> DefCore Board Report
>> Meeting May 17, 2015
>> Rob Hirschfeld & Egle Sigler Co-Chairs
>>
>> 20 minutes
>>
>> Process 2015A Discussion [5 mins. WARNING MINIMAL TIME]
>> 2015.04/03 Update [5 mins WARNING MINIMAL TIME]
>> 2015.05 Guideline Approval [5 mins]
>> Next Cycle Objectives [5 mins]
>>
>> -- 
>>   
>> Rob
>> ____________________________
>> Rob Hirschfeld, 512-773-7522
>>
>> I am in CENTRAL (-6) time
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__robhirschfeld.com&d=AwICAg&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=Q8IhPU-EIzbG5YDx5LYO7zEJpGZykn7RwFg-UTPWvDc&m=znDq0m4Bb3X4F17krVc50lf9Ayh55uxGmLjS7vJbkfE&s=HGlVKWefqiHujd7zm1QlzYeUsVUFOYoVgf3WEGc18aQ&e= twitter: @zehicle, github: cloudedge & ravolt
>>
>>
>> _______________________________________________
>> Defcore-committee mailing list
>> Defcore-committee at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee

-- 
   

Rob
____________________________
Rob Hirschfeld, 512-773-7522

I am in CENTRAL (-6) time
http://robhirschfeld.com
twitter: @zehicle, github: cloudedge & ravolt


_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee