Release Roadmap - Revision history

Neteler: Releases are managed at https://github.com/OSGeo/grass/releases

2022-05-13T15:18:51Z

Releases are managed at https://github.com/OSGeo/grass/releases

← Older revision		Revision as of 15:18, 13 May 2022
Line 144:		Line 144:
	* Open to major enhancements which '''''do''''' break backward compatibility with 7.x.		* Open to major enhancements which '''''do''''' break backward compatibility with 7.x.
	* See https://trac.osgeo.org/grass/wiki/Grass8Planning		* See https://trac.osgeo.org/grass/wiki/Grass8Planning
			* Releases are managed at https://github.com/OSGeo/grass/releases

	[[Category:Development]]		[[Category:Development]]
	[[Category:Release Roadmap]]		[[Category:Release Roadmap]]

Neteler: link to https://trac.osgeo.org/grass/wiki/Grass8Planning

2016-05-16T10:11:47Z

link to https://trac.osgeo.org/grass/wiki/Grass8Planning

← Older revision		Revision as of 10:11, 16 May 2016
Line 143:		Line 143:

	* Open to major enhancements which '''''do''''' break backward compatibility with 7.x.		* Open to major enhancements which '''''do''''' break backward compatibility with 7.x.
			* See https://trac.osgeo.org/grass/wiki/Grass8Planning
	..~~. and so on.~~


	[[Category:Development]]		[[Category:Development]]
	[[Category:Release Roadmap]]		[[Category:Release Roadmap]]

Neteler: discourage the use of GRASS 6.5.x in favour of 7

2016-01-23T20:17:14Z

discourage the use of GRASS 6.5.x in favour of 7

← Older revision		Revision as of 20:17, 23 January 2016
Line 120:		Line 120:
	=== GRASS 6.5.x and beyond ===		=== GRASS 6.5.x and beyond ===

	Since GRASS 7 development has started the 6.x line works towards stability. Major new development should now happen in GRASS 7 SVN (<tt>trunk</tt>). What is now the ''6.5'' branch (<tt>develbranch_6</tt>) should be kept in sync with the 6.4 bug fixes, but is also available as a testing ground for bug fixes before backport to the stable branch and important backports from GRASS 7.		Since GRASS 7 development has started the 6.x line works towards stability. Major new development should now happen in GRASS 7 SVN (<tt>trunk</tt>). <strike>What is now the ''6.5'' branch (<tt>develbranch_6</tt>) should be kept in sync with the 6.4 bug fixes, but is also available as a testing ground for bug fixes before backport to the stable branch and important backports from GRASS 7.

	It is unknown at this time if there will be a 6.5 or 6.6 release, it mostly depends on how long a final GRASS 7.0 release takes and what important development comes along which is too radical for the 6.4 stable branch but too important to wait for a final 7.0 release. Thus, it is not planned at this time, but may be possible as an interim measure.		It is unknown at this time if there will be a 6.5 or 6.6 release, it mostly depends on how long a final GRASS 7.0 release takes and what important development comes along which is too radical for the 6.4 stable branch but too important to wait for a final 7.0 release. Thus, it is not planned at this time, but may be possible as an interim measure.</strike>

	* Open to bug fixes and non-structural enhancements which '''''do not''''' break backwards compatibility with 6.x		* <strike>Open to bug fixes and non-structural enhancements which '''''do not''''' break backwards compatibility with 6.x</strike> - please use GRASS GIS 7

	* Available only in source code form by way of a direct SVN checkout.		* Available only in source code form by way of a direct SVN checkout.
Line 130:		Line 130:
	* It is strongly encouraged that new development happens in the GRASS 7 branch.		* It is strongly encouraged that new development happens in the GRASS 7 branch.

	* Mainly geared at extreme power-users (aka casual developers) who need the stability of GRASS 6 for production use tasks, but can't live without some of the newer gadgets. Users are expected to report and help fix any bugs they discover.		* <strike>Mainly geared at extreme power-users (aka casual developers) who need the stability of GRASS 6 for production use tasks, but can't live without some of the newer gadgets. Users are expected to report and help fix any bugs they discover.</strike>

	=== GRASS 7.x ===		=== GRASS 7.x ===

Neteler: /* GRASS 7.x */

2015-02-20T21:03:42Z

GRASS 7.x

← Older revision		Revision as of 21:03, 20 February 2015
Line 138:		Line 138:
	* Planning is continued in the Trac integrated development wiki: http://trac.osgeo.org/grass/wiki/Grass7Planning		* Planning is continued in the Trac integrated development wiki: http://trac.osgeo.org/grass/wiki/Grass7Planning

	* ~~Available only in source code form at this time.~~		* Released
	* Users are expected to report and help fix any bugs they discover.
	* Mainly geared at developers and extreme power-users.

			=== GRASS 8.x ===

			* Open to major enhancements which '''''do''''' break backward compatibility with 7.x.

			... and so on.


	[[Category:Development]]		[[Category:Development]]
	[[Category:Release Roadmap]]		[[Category:Release Roadmap]]

Neteler: /* GRASS 6.4.x */

2012-02-19T16:36:09Z

GRASS 6.4.x

← Older revision		Revision as of 16:36, 19 February 2012
Line 114:		Line 114:
	* 6.4 is the first stable version of GRASS to build natively for MS Windows.		* 6.4 is the first stable version of GRASS to build natively for MS Windows.

	* See the [[GRASS 6~~.4 Feature Plan]~~] for discussion and details.		* See the [http://trac.osgeo.org/grass/wiki/Grass6Planning GRASS 6 planning] for discussion and details.

	* See the [http://trac.osgeo.org/grass/wiki/WikiStart#Releases trac development wiki for (pre)release history].		* See the [http://trac.osgeo.org/grass/wiki/WikiStart#Releases trac development wiki for (pre)release history].

Neteler: /* GRASS 6.4.x */

2010-09-03T20:46:49Z

GRASS 6.4.x

← Older revision		Revision as of 20:46, 3 September 2010
Line 110:		Line 110:
	* It is now closed to most feature enhancements (''frozen Dec 2008'').		* It is now closed to most feature enhancements (''frozen Dec 2008'').

	* 6.4 ~~will include~~ the new wxPython GUI but otherwise be very similar to 6.3.x.		* 6.4.0 includes the new wxPython GUI but otherwise be very similar to 6.3.x.
	~~: ''For 6.4.0 it is debatable as to which should be the default GUI. (i.e. should the Tcl/Tk GUI remain the default on MS Windows until 6.4.1?)''~~

	* 6.4 is the first stable version of GRASS to build natively for MS Windows.		* 6.4 is the first stable version of GRASS to build natively for MS Windows.

⚠️HamishBowman: /* GRASS 7.x */ weekly snapshot also available now

2009-02-25T07:28:02Z

GRASS 7.x: weekly snapshot also available now

← Older revision		Revision as of 07:28, 25 February 2009
Line 139:		Line 139:
	* Planning is continued in the Trac integrated development wiki: http://trac.osgeo.org/grass/wiki/Grass7Planning		* Planning is continued in the Trac integrated development wiki: http://trac.osgeo.org/grass/wiki/Grass7Planning

	* Available only in source code form ~~by way of a direct SVN checkout~~ at this time.		* Available only in source code form at this time.
	* Users are expected to report and help fix any bugs they discover.		* Users are expected to report and help fix any bugs they discover.
	* Mainly geared at developers and extreme power-users.		* Mainly geared at developers and extreme power-users.

⚠️HamishBowman: /* GRASS 7.x */ gramar

2009-02-25T07:25:05Z

GRASS 7.x: gramar

← Older revision		Revision as of 07:25, 25 February 2009
Line 135:		Line 135:
	=== GRASS 7.x ===		=== GRASS 7.x ===

	* Open to major enhancements which '''''~~does~~''''' break backward compatibility with 6.x.		* Open to major enhancements which '''''do''''' break backward compatibility with 6.x.
	* See the [[GRASS 7 ideas collection]]		* See the [[GRASS 7 ideas collection]]
	* Planning is continued in the Trac integrated development wiki: http://trac.osgeo.org/grass/wiki/Grass7Planning		* Planning is continued in the Trac integrated development wiki: http://trac.osgeo.org/grass/wiki/Grass7Planning

⚠️HamishBowman: /* GRASS 6.5.x and beyond */ typo

2009-02-25T07:23:49Z

GRASS 6.5.x and beyond: typo

← Older revision		Revision as of 07:23, 25 February 2009
Line 129:		Line 129:
	* Available only in source code form by way of a direct SVN checkout.		* Available only in source code form by way of a direct SVN checkout.

	* Is is strongly encouraged that new development happens in the GRASS 7 branch.		* It is strongly encouraged that new development happens in the GRASS 7 branch.

	* Mainly geared at extreme power-users (aka casual developers) who need the stability of GRASS 6 for production use tasks, but can't live without some of the newer gadgets. Users are expected to report and help fix any bugs they discover.		* Mainly geared at extreme power-users (aka casual developers) who need the stability of GRASS 6 for production use tasks, but can't live without some of the newer gadgets. Users are expected to report and help fix any bugs they discover.

⚠️HamishBowman: /* GRASS 6.5.x and beyond */ minor wording

2009-02-25T07:23:14Z

GRASS 6.5.x and beyond: minor wording

← Older revision		Revision as of 07:23, 25 February 2009
Line 125:		Line 125:
	It is unknown at this time if there will be a 6.5 or 6.6 release, it mostly depends on how long a final GRASS 7.0 release takes and what important development comes along which is too radical for the 6.4 stable branch but too important to wait for a final 7.0 release. Thus, it is not planned at this time, but may be possible as an interim measure.		It is unknown at this time if there will be a 6.5 or 6.6 release, it mostly depends on how long a final GRASS 7.0 release takes and what important development comes along which is too radical for the 6.4 stable branch but too important to wait for a final 7.0 release. Thus, it is not planned at this time, but may be possible as an interim measure.

	* Open to bug fixes and ~~minor~~ enhancements which '''''do not''''' break backwards compatibility with 6.x		* Open to bug fixes and non-structural enhancements which '''''do not''''' break backwards compatibility with 6.x

	* Available only in source code form by way of a direct SVN checkout.		* Available only in source code form by way of a direct SVN checkout.