Release Terminology - Revision history

Adilger: fix formatting

2026-01-09T19:40:18Z

fix formatting

← Older revision		Revision as of 12:40, 9 January 2026
Line 2:		Line 2:

	Versions have Major.Minor.Release.Patch numbers:		Versions have Major.Minor.Release.Patch numbers:
	- The Major version indicates significant functional change and possibly protocol incompatibility from previous major versions.		* The Major version indicates significant functional change and possibly protocol incompatibility from previous major versions.
	- The Minor version indicates important new features, but maintains compatibility back to at least the previous LTS release.		* The Minor version indicates important new features, but maintains compatibility back to at least the previous LTS release.
	- The Release version indicates bug fixes and minor new functionality or enhancements that have been tested .		* The Release version indicates bug fixes and minor new functionality or enhancements that have been tested .
	-- Release versions .0 through .49 indicate stable maintenance releases.		** Release versions .0 through .49 indicate stable maintenance releases.
	-- Release versions .50 through .99 indicate development releases that may contain major new functionality and possibly (temporary) protocol incompatibilities, and are not recommended for general production usage.		** Release versions .50 through .99 indicate development releases that may contain major new functionality and possibly (temporary) protocol incompatibilities, and are not recommended for general production usage.
	- The Patch version indicates individual fixes and enhancements.		* The Patch version indicates individual fixes and enhancements.

	Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. 2.15.8 is the current LTS release. See: http://lustre.org/roadmap/ for details.		Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. 2.15.8 is the current LTS release. See: http://lustre.org/roadmap/ for details.

	[[Category: Releases]]		[[Category: Releases]]

Adilger: Describe versioning better.

2026-01-09T19:39:27Z

Describe versioning better.

← Older revision		Revision as of 12:39, 9 January 2026
Line 1:		Line 1:
	Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. 2.15.8 is the current LTS release. See: http://lustre.org/roadmap/.		Lustre releases are numbered with semantic versions, such as 2.17.0 or 2.17.52.

			Versions have Major.Minor.Release.Patch numbers:
			- The Major version indicates significant functional change and possibly protocol incompatibility from previous major versions.
			- The Minor version indicates important new features, but maintains compatibility back to at least the previous LTS release.
			- The Release version indicates bug fixes and minor new functionality or enhancements that have been tested .
			-- Release versions .0 through .49 indicate stable maintenance releases.
			-- Release versions .50 through .99 indicate development releases that may contain major new functionality and possibly (temporary) protocol incompatibilities, and are not recommended for general production usage.
			- The Patch version indicates individual fixes and enhancements.

			Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. 2.15.8 is the current LTS release. See: http://lustre.org/roadmap/ for details.

	[[Category: Releases]]		[[Category: Releases]]

Adilger: update of old LTS release numbers

2026-01-09T19:29:59Z

update of old LTS release numbers

← Older revision		Revision as of 12:29, 9 January 2026
Line 1:		Line 1:
	Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. 2.10.6 is the current LTS release~~. However, 2.12.x is the next LTS stream. A final 2.10.7 is planned around the time of 2.12.1~~. See: http://lustre.org/roadmap/.		Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. 2.15.8 is the current LTS release. See: http://lustre.org/roadmap/.

	[[Category: Releases]]		[[Category: Releases]]

Spitzcor at 21:51, 12 February 2019

2019-02-12T21:51:29Z

← Older revision		Revision as of 14:51, 12 February 2019
Line 1:		Line 1:
	Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. 2.10.6 is the current LTS release. However, 2.12.x is the next LTS stream. A final 2.10.7 is planned around the time ~~that~~ 2.12.1. See: http://lustre.org/roadmap/.		Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. 2.10.6 is the current LTS release. However, 2.12.x is the next LTS stream. A final 2.10.7 is planned around the time of 2.12.1. See: http://lustre.org/roadmap/.

	[[Category: Releases]]		[[Category: Releases]]

Spitzcor at 21:51, 12 February 2019

2019-02-12T21:51:10Z

← Older revision		Revision as of 14:51, 12 February 2019
Line 1:		Line 1:
	Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. ~~At the time of writing the Lustre~~ 2.10.~~x release~~ is the current LTS release.		Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. 2.10.6 is the current LTS release. However, 2.12.x is the next LTS stream. A final 2.10.7 is planned around the time that 2.12.1. See: http://lustre.org/roadmap/.

	[[Category: Releases]]		[[Category: Releases]]

KenRawlings: KenRawlings moved page Retired Release Terminology to Release Terminology

2017-09-05T16:28:22Z

KenRawlings moved page Retired Release Terminology to Release Terminology

← Older revision	Revision as of 09:28, 5 September 2017
(No difference)

Pjones: Replaced content with "Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not ma..."

2017-09-05T12:46:01Z

Replaced content with "Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not ma..."

← Older revision		Revision as of 05:46, 5 September 2017
Line 1:		Line 1:
	~~We used to us the terms "Maintenance Release" and "Feature Release" to differentiate the kinds of~~ Lustre releases, but those terms are now retired. There are many reasons behind the name changes, but the change with the broadest impact is likely the current end of public Maintenance Releases. Before we explain that further, we need to establish some background information.		Occasional Lustre releases will be designated as LTS (Long Term Stability) releases and have a series of maintenance releases that will include only small fixes and not major new functionality. At the time of writing the Lustre 2.10.x release is the current LTS release.

	Lustre has a main continuous branch of development that is named ''master''. Whenever it is time to create a new release from the master branch we increment the second number in Lustre's version and reset the third number to zero. For instance, 2.4.0, 2.5.0, and 2.6.0 are releases created along the master branch. These releases used to go by the name "Feature Releases". Feature Releases in the past were of somewhat lower stability than one might hope, in part because they contained large destabilizing new headline features.

	Many organizations wish to have regular bug-fix releases that do not contain new destabilizing features. Therefore it was common to create side branches of the lustre code that allowed changes that focused mainly on stabilization. Not every Feature Release spawned a stabilization branch, instead they began every few releases. For instance 1.8.0, 2.1.0, and 2.5.0 all spawned stabilization branches while 2.0.0, 2.2.0, and 2.3.0 did not. The releases that were created along these side branches were called "Maintenance Releases". Maintenance releases incremented the third number in the Lustre version, for instance 2.5.1, 2.5.2, and 2.5.3.

	~~In the past, OpenSFS would publish a slide that looked like this:~~

	~~[[File:Retired_roadmap_example.png\|x300px]]~~

	The master branch is the main point of collaboration for the Lustre development community. All are welcome to contribute to the development of the master branch. Intel maintains a leadership position in the master branch by contributing the majority of the changes to the branch. It is important to note that Intel's work (~~and Whamcloud before they were purchased by Intel~~) on the master branch is funded in large part by a [http://wiki.opensfs.org/Community_Tree_Development_Contract contract from OpenSFS], so a significant portion of those Intel authored changes on the master branch are made at the behest of OpenSFS. The releases ~~along the master branch can therefore rightly be claimed to be "community releases".~~

	~~In contrast, the public Maintenance Releases were all funded~~ and ~~largely developed by~~ a ~~single organization,~~ of ~~late Intel. In hind sight, it was probably misleading to present information about Maintenance~~ and ~~Feature releases on the same slide, as it did~~ not ~~make clear this distinction~~. ~~Feature releases were developed and funded by the community (although perhaps not in equal proportions amongst~~ the ~~organizations), but Maintenance Releases were almost entirely developed and funded by a single organization, Intel, for its support customers.~~

	~~Intel for some~~ time was very open with their stabilization branches and resulting Maintenance Releases, choosing to publish them in publicly accessible locations. But alas, they plan to publish that work publicly no more.

	''Intel no longer intends to push their stabilization branches and Maintenance Releases to public locations''. While this may be distressing to some, it bears keeping in mind that this is common practice amongst other Lustre vendors. Cray keeps their Lustre product branch private. Seagate keeps at least one of their Lustre product branches private. Both Cray and Seagate upstream changes as they see fit to the Lustre master branch.

	~~''Intel has expressed their commitment to up-streaming Intel Lustre changes to Lustre's master branch.'' We can expect them to remain active members~~ of the ~~Lustre development community for the foreseeable future.~~

	~~It is worth repeating: ''There will no longer be publicly published changes to the Intel's b2_5 branch''. Likewise, there are ''no planned future Maintenance Releases''.~~ Lustre 2.5.~~3 was the last public Maintenance Release. There will not be a public Lustre 2.5.4.~~

	~~With this change (and others) in mind, there Lustre community~~ is ~~retiring~~ the ~~terms "Maintenance Release" and "Feature Release". Instead, the future releases that we make along the master branch will simply be known as "Major releases".~~
	~~If the community decides to have minor stabilization releases in the future we will likely call them "Minor releases".~~

	~~Fortunately, the community development of Lustre's master branch remains open and vibrant. We remain committed to making Major Releases along the master branch roughly every six months~~.

	[[Category: Releases]]		[[Category: Releases]]

KenRawlings: adding categories

2016-03-04T19:30:00Z

adding categories

← Older revision		Revision as of 12:30, 4 March 2016
Line 25:		Line 25:

	Fortunately, the community development of Lustre's master branch remains open and vibrant. We remain committed to making Major Releases along the master branch roughly every six months.		Fortunately, the community development of Lustre's master branch remains open and vibrant. We remain committed to making Major Releases along the master branch roughly every six months.

			[[Category: Releases]]

ChrisMorrone at 17:36, 20 May 2015

2015-05-20T17:36:57Z

← Older revision		Revision as of 10:36, 20 May 2015
Line 1:		Line 1:
	~~'''A.K.A. What happened to Maintenance Releases?'''~~

	~~'''A.K.A. When is Lustre 2.5.4 coming out?'''~~

	We used to us the terms "Maintenance Release" and "Feature Release" to differentiate the kinds of Lustre releases, but those terms are now retired. There are many reasons behind the name changes, but the change with the broadest impact is likely the current end of public Maintenance Releases. Before we explain that further, we need to establish some background information.		We used to us the terms "Maintenance Release" and "Feature Release" to differentiate the kinds of Lustre releases, but those terms are now retired. There are many reasons behind the name changes, but the change with the broadest impact is likely the current end of public Maintenance Releases. Before we explain that further, we need to establish some background information.

ChrisMorrone at 18:37, 23 April 2015

2015-04-23T18:37:01Z

← Older revision		Revision as of 11:37, 23 April 2015
Line 11:		Line 11:
	In the past, OpenSFS would publish a slide that looked like this:		In the past, OpenSFS would publish a slide that looked like this:

	~~(FIXME~~: ~~Image coming once wiki uploads enabled)~~		[[File:Retired_roadmap_example.png\|x300px]]

	The master branch is the main point of collaboration for the Lustre development community. All are welcome to contribute to the development of the master branch. Intel maintains a leadership position in the master branch by contributing the majority of the changes to the branch. It is important to note that Intel's work (and Whamcloud before they were purchased by Intel) on the master branch is funded in large part by a [http://wiki.opensfs.org/Community_Tree_Development_Contract contract from OpenSFS], so a significant portion of those Intel authored changes on the master branch are made at the behest of OpenSFS. The releases along the master branch can therefore rightly be claimed to be "community releases".		The master branch is the main point of collaboration for the Lustre development community. All are welcome to contribute to the development of the master branch. Intel maintains a leadership position in the master branch by contributing the majority of the changes to the branch. It is important to note that Intel's work (and Whamcloud before they were purchased by Intel) on the master branch is funded in large part by a [http://wiki.opensfs.org/Community_Tree_Development_Contract contract from OpenSFS], so a significant portion of those Intel authored changes on the master branch are made at the behest of OpenSFS. The releases along the master branch can therefore rightly be claimed to be "community releases".