3:30 a.m.
I'm not particularly concerned, and yes, no one is obliged to do anything.
People get concerned that bugfixes might not come out if a line is no
longer the maintenance release. I think this is very understandable.
It's even directly addressed right there on the release page at intel:
"The HPDD team at Intel invests a huge amount of time and resources into
ensuring that every release is of high quality. However, we recognize
that many Lustre users would rather run a release that is well-proven in
production, and will be supported over a longer time, even if it means
foregoing some of the newer features. To meet the needs of these
customers, Intel designates a certain release to be its long-term
maintenance release stream and produces regular bugfix-only updates for
this release stream. These releases are what the majority of Intel's
customers choose to run in production. You can find out more detailed
information in the Lustre 2.4 ChangeLog."
The early dropping of the maintenance release is fine, but do we need to
pretend it has no impact on anything?
Scott
On 10/17/2013 11:12 AM, Jones, Peter A wrote:
Please note that nobody is obliged to keep track with the latest
maintenance release. If your present release is working for you why move?
On 10/17/13 7:25 AM, "Scott Nolin" <scott.nolin(a)ssec.wisc.edu> wrote:
> Just be aware that 2.4 was the planned maintenance release series - but
> that is now being dropped and maintenance release switched to 2.5 when
> that comes out.
>
> If I understand correctly this was a change decided on based on a desire
> for HSM features available in 2.5.
>
> I believe 2.5 is also not as backwards compatible with as many versions
> as 2.4. I get the feeling that 2.4 will be viable for a while yet even
> after 2.5 is released, but that's just a guess.
>
> Lustre releases in my opinion are kind of in a strange state right now.
>
> Scott
>
> On 10/16/2013 6:33 PM, Bob Ball wrote:
>> We are at 2.1.6. So, this means our next step up should be to 2.4.1, is
>> that correct? Yes, I would have preferred to have heard such an
>> announcement via this list. I would assume the upgrade path/procedure
>> is well documented?
>>
>> bob
>>
>> On 10/16/2013 6:23 PM, Jones, Peter A wrote:
>>> Hi Ed
>>>
>>> Yes the major version of the maintenance release stream changed. The
>>> roadmap aims to show that and we have presented about this change both
>>> before and advance at community events like LUG, LAD etc. I suppose
>>> that I
>>> could/should have stated that information with the release announcement
>>> for 2.4.1. Would that kind of notice be sufficient do you think?
>>>
>>> Peter
>>>
>>> On 10/16/13 2:44 PM, "Edward Walter" <ewalter(a)cs.cmu.edu>
wrote:
>>>
>>>> Hello,
>>>>
>>>> The link for the current maintenance release points here:
>>>>
>>>> http://downloads.whamcloud.com/public/lustre/latest-maintenance-release
>>>> /
>>>>
>>>> This tree seems to contain Lustre version 2.4.1 (as of 2013/09/12).
>>>> Did
>>>> the major version for the maintenance stream change? I didn't see
any
>>>> anouncement to that effect. The Lustre Software Roadmap
>>>> (https://wiki.hpdd.intel.com/display/PUB/Community+Lustre+Roadmap)
>>>> seems
>>>> to imply that this will happen at some point.
>>>>
>>>> Thanks much.
>>>>
>>>> -Ed Walter
>>>> Carnegie Mellon University
>>>> _______________________________________________
>>>> HPDD-discuss mailing list
>>>> HPDD-discuss(a)lists.01.org
>>>> https://lists.01.org/mailman/listinfo/hpdd-discuss
>>> _______________________________________________
>>> HPDD-discuss mailing list
>>> HPDD-discuss(a)lists.01.org
>>> https://lists.01.org/mailman/listinfo/hpdd-discuss
>>>
>>
>> _______________________________________________
>> HPDD-discuss mailing list
>> HPDD-discuss(a)lists.01.org
>> https://lists.01.org/mailman/listinfo/hpdd-discuss
>
>