[cdwg] Maintenance releaase status of 2.5/2.4

[Christopher J. Morrone]

Cory,

The new official URL for the community roadmap is this:

   http://lustre.opensfs.org/community-lustre-roadmap/

And, yes, we will absolutely update that roadmap to show 2.5 as the next 
maintenance branch instead of 2.4.  Maybe we'll keep a stubby branch for 
2.4 in the picture that shows 2.4.1 and 2.4.2.

Unless I completely misunderstood, nothing Peter has said contradicts 
that plan.  He is on board with us advertising 2.5 as the longer term 
"scheduled maintenance".

Peter is just making clear Intel's business plan, which is nice of him 
to share, and again, does not conflict with the community plan.  They 
are going to support 2.5 for their customers, and they will _also_ 
support 2.4 for their customers that choose to keep paying for it.

Great!  LLNL is an Intel customer, and we plan to take them up on that. 
  We are on the path to install 2.4 everywhere soon, and it is not clear 
to me how quickly we can change our plans to move to 2.5.  But we are 
working on adapting our plans to align with the community and go to 2.5 
at the earliest reasonable date.

If you are not an Intel customer, then their support of 2.4 for their 
customers doesn't particularly apply to you.  No worries.

The important thing is that Intel is agreeing with the plan to advertise 
regularly scheduled maintenance releases for the 2.5 branch along with 
the community.

Chris


On 06/27/2013 02:14 PM, Cory Spitz wrote:
> Ok, I haven't heard of any objections either.
>
> However, I'm more than a bit concerned that the CDWG may recommend that
> b2_5 become a maintenance branch, but that we aren't prepared to turn out
> releases from said branch.
>
> Peter J. said, "maintenance releases and support is at the discretion of
> the support providers" when talking about _other_ branches.  I'm not sure
> that he was implying that Intel would substitute 2.4.x for 2.5.x on the
> roadmap
> (https://wiki.hpdd.intel.com/display/PUB/Community+Lustre+Roadmap).  Since
> Intel was putting out maintenance releases for the previous maintenance
> branch, b2_1, I think that they need to be on-board with the suggestion to
> move to b2_5.  Otherwise, the CDWG is going to have to find a way to turn
> out 2.5.x releases.
>
> Thanks,
> -Cory
>
>
>
> On 6/27/13 3:33 PM, "Christopher J. Morrone" <morrone2 at llnl.gov> wrote:
>
>> Cory,
>>
>> We will have one final discussion on the July 3rd CDWG call.  Given that
>> there have been no dissenting opinions on the mailing lists, I suspect
>> that the discussion will be short and announcements will be circulated
>> shortly after.
>>
>> So my powers of prognostication could be on the fritz, but I think it is
>> fairly safe to say "when" at this point.
>>
>> Chris
>>
>> On 06/27/2013 11:25 AM, Cory Spitz wrote:
>>> Chris,
>>>
>>> What do you mean "when we officially announceŠ"  I didn't realize that
>>> we
>>> had already decided.  Do you mean to say, "*if* we officially
>>> announceŠ"?
>>>
>>> Thanks,
>>> -Cory
>>>
>>> On 6/27/13 1:13 PM, "Christopher J. Morrone" <morrone2 at llnl.gov> wrote:
>>>
>>>> Bryan,
>>>>
>>>> We certainly have consensus among the small number of organizations
>>>> that
>>>> bothered to reply.  This will be on the Agenda for next Wednesday's
>>>> call.
>>>>
>>>> When we officially announce that 2.5 will be a long term maintenance
>>>> release, the we will explain that the maintenance period for 2.4 has
>>>> been shortened dramatically.  No longer should folks expect that 2.4 is
>>>> a branch that will be supported for years.  Instead its maintenance
>>>> window might be only as long as it takes to get 2.5.0 released.  But we
>>>> haven't discussed the exact date to advertise as the cut off.
>>>>
>>>> Chris
>>>>
>>>> On 06/27/2013 08:01 AM, Bryan Cote wrote:
>>>>> Hello,
>>>>>
>>>>> Did we get consensus on whether 2.5 will be a maintenance release, and
>>>>> if so, what is the impact on 2.4?
>>>>>
>>>>> ==Bryan
>>>>>
>>>>>
>>>>>
>>>>> *______________________________________________________________________
>>>>> __
>>>>> ______*
>>>>>
>>>>> *Bryan R. Cote **|**Sr. Product Manager *
>>>>>
>>>>> *M 603.557.3568**|**P 617.722.0090 Ext. 302 **|**F 617.722.6060*
>>>>>
>>>>> *100 North Washington Street **|**Boston, MA 02114*
>>>>>
>>>>> **
>>>>>
>>>>> cid:image002.jpg at 01CDFB24.4A1E3320**
>>>>>
>>>>> *www.terascala.com <http://www.terascala.com/> *
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cdwg mailing list
>>>>> cdwg at lists.opensfs.org
>>>>> http://lists.opensfs.org/listinfo.cgi/cdwg-opensfs.org
>>>>>
>>>>
>>>> _______________________________________________
>>>> cdwg mailing list
>>>> cdwg at lists.opensfs.org
>>>> http://lists.opensfs.org/listinfo.cgi/cdwg-opensfs.org
>>>
>>> .
>>>
>
> .
>