From: Jones, Peter A <peter.a.jones@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Lustre 2.4 Release
Date: Thu, 20 Jun 2013 12:29:21 +0000 [thread overview]
Message-ID: <CDE84282.2B648%peter.a.jones@intel.com> (raw)
In-Reply-To: <CALuPYL0Vf8JOOhOq9RRx_ErP+5qN5_FmgmC6w409DNKqnqSSRw@mail.gmail.com>
Hi Indivar
You are not the first to get confused by the semantics in the terminology.
A maintenance release stream is a series of maintenance releases that follows a given feature release.
So, 2.4.0 is a feature release, 2.4.x is set to become our next maintenance release stream, and 2.4.1 (due out in Q3) will be the first maintenance release in that stream.
The visual on the roadmap showing the link between the feature releases and the maintenance releases aims to illustrate this.
Does this make sense? Do you have any suggestions how we could clarify this?
Peter
On 6/20/13 5:21 AM, "Indivar Nair" <indivar.nair at techterra.in<mailto:indivar.nair@techterra.in>> wrote:
Hi ...,
Lustre 2.4 was supposed to be released as a "Maintenance Release' -
https://wiki.hpdd.intel.com/display/PUB/Community+Lustre+Roadmap
so how come it has been released as a 'Feature Release'?
https://wiki.hpdd.intel.com/display/PUB/Lustre+Releases
Will it be moved to 'Maintenance Release' later?
Regards,
Indivar Nair
next prev parent reply other threads:[~2013-06-20 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 12:21 [Lustre-devel] Lustre 2.4 Release Indivar Nair
2013-06-20 12:29 ` Jones, Peter A [this message]
2013-06-21 17:10 ` Indivar Nair
2013-06-21 20:20 ` Jones, Peter A
2013-06-20 16:24 ` Dilger, Andreas
2013-06-20 17:38 ` Indivar Nair
2013-06-20 21:15 ` White, Cliff
2013-06-20 21:19 ` Jones, Peter A
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CDE84282.2B648%peter.a.jones@intel.com \
--to=peter.a.jones@intel.com \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.