Debian - Revision history

RogueScholar: Add relevant links to Development builds page, fixing dead end page status

2021-09-13T00:39:47Z

Add relevant links to Development builds page, fixing dead end page status

← Older revision		Revision as of 00:39, 13 September 2021
Line 6:		Line 6:

	=== Uploads to Development Suites ===		=== Uploads to Development Suites ===

	The guide for uploading any package (such as XBMC) to Debian is the [http://www.debian.org/doc/manuals/maint-guide/ Debian New Maintainer's Guide]. There is also some tips on best packaging practics, found in Chapter 6 of the Debian Developer's Reference (see http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html).		The guide for uploading any package (such as XBMC) to Debian is the [http://www.debian.org/doc/manuals/maint-guide/ Debian New Maintainer's Guide]. There is also some tips on best packaging practics, found in Chapter 6 of the Debian Developer's Reference (see http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html).

Line 15:		Line 14:
	'''NOTE''' that if any release critical bugs are found in the version of Kodi that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.		'''NOTE''' that if any release critical bugs are found in the version of Kodi that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.

	For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.		For other packages such as [[Development builds#Nightly builds\|git snapshots]], [[Development builds#Beta and Release Candidate Builds\|beta releases and release candidates]], the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.

	Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.		Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.

MYnDstrEAm: installation

2021-07-25T11:20:55Z

installation

← Older revision		Revision as of 11:20, 25 July 2021
Line 1:		Line 1:
			== Installation ==
			To install a new version of Kodi on Debian 10 (buster) stable you need to install it from backports like so: <code>sudo apt install -t buster-backports kodi</code>

			== Uploading Kodi ==
	Here are a some notes related to uploading Kodi to Debian and having it synced to Ubuntu.		Here are a some notes related to uploading Kodi to Debian and having it synced to Ubuntu.

	== Uploads to Development Suites ==		=== Uploads to Development Suites ===

	The guide for uploading any package (such as XBMC) to Debian is the [http://www.debian.org/doc/manuals/maint-guide/ Debian New Maintainer's Guide]. There is also some tips on best packaging practics, found in Chapter 6 of the Debian Developer's Reference (see http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html).		The guide for uploading any package (such as XBMC) to Debian is the [http://www.debian.org/doc/manuals/maint-guide/ Debian New Maintainer's Guide]. There is also some tips on best packaging practics, found in Chapter 6 of the Debian Developer's Reference (see http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html).
Line 17:		Line 21:
	There are times where bugs need to be fixed for versions of Kodi packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.		There are times where bugs need to be fixed for versions of Kodi packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.

	== Uploads to Release Suites ==		=== Uploads to Release Suites ===

	Packages can be uploaded to the "stable" suite in Debian, although these kind of uploads can only be for fixing security related bugs. The Debian Developer's Reference has a section describing [http://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security how to handle security related bugs]. For Ubuntu, the page describing security related uploads to Ubuntu is found at https://wiki.ubuntu.com/SecurityTeam/SponsorsQueue.		Packages can be uploaded to the "stable" suite in Debian, although these kind of uploads can only be for fixing security related bugs. The Debian Developer's Reference has a section describing [http://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security how to handle security related bugs]. For Ubuntu, the page describing security related uploads to Ubuntu is found at https://wiki.ubuntu.com/SecurityTeam/SponsorsQueue.

Sw2000: /* Links: refer to kodi packages */

2020-01-03T21:14:13Z

Links: refer to kodi packages

← Older revision		Revision as of 21:14, 3 January 2020
Line 25:		Line 25:
	== Links ==		== Links ==

	* ~~http~~://~~packages.qa~~.debian.org/x/~~xbmc.html~~		* https://tracker.debian.org/pkg/kodi
	* https://launchpad.net/ubuntu/+source/~~xbmc~~		* https://launchpad.net/ubuntu/+source/kodi

	[[Category:Linux]]		[[Category:Linux]]

NedBot: Bot: Automated text replacement (- XBMC + Kodi )

2015-05-04T08:29:17Z

Bot: Automated text replacement (- XBMC + Kodi )

← Older revision		Revision as of 08:29, 4 May 2015
Line 1:		Line 1:
	Here are a some notes related to uploading ~~XBMC~~ to Debian and having it synced to Ubuntu.		Here are a some notes related to uploading Kodi to Debian and having it synced to Ubuntu.

	== Uploads to Development Suites ==		== Uploads to Development Suites ==
Line 7:		Line 7:
	Any package that is in Debian can be synced to Ubuntu. That process is described at https://wiki.ubuntu.com/SyncRequestProcess.		Any package that is in Debian can be synced to Ubuntu. That process is described at https://wiki.ubuntu.com/SyncRequestProcess.

	All packages are normally uploaded to either the "unstable" suite, or the "experimental" suite of Debian. Generally, whenever a new release of ~~XBMC~~ is done, the suite to upload these new ~~XBMC~~ packages is the "unstable" suite. Packages uploaded to unstable enter a period where they stay in unstable to get tested. Once this time where it's in unstable ends, the packages are migrated to the "testing" suite where it will be shipped in the next release of Debian. So long as no [http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#rc-bugs release critical bugs] exist for the ~~XBMC~~ package in the [http://www.debian.org/Bugs/ Debian Bug Tracking System], the packages will be migrated to testing. If release critical bugs do exist, a new upload should be made that fixes these bugs.		All packages are normally uploaded to either the "unstable" suite, or the "experimental" suite of Debian. Generally, whenever a new release of Kodi is done, the suite to upload these new Kodi packages is the "unstable" suite. Packages uploaded to unstable enter a period where they stay in unstable to get tested. Once this time where it's in unstable ends, the packages are migrated to the "testing" suite where it will be shipped in the next release of Debian. So long as no [http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#rc-bugs release critical bugs] exist for the Kodi package in the [http://www.debian.org/Bugs/ Debian Bug Tracking System], the packages will be migrated to testing. If release critical bugs do exist, a new upload should be made that fixes these bugs.

	'''NOTE''' that if any release critical bugs are found in the version of ~~XBMC~~ that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.		'''NOTE''' that if any release critical bugs are found in the version of Kodi that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.

	For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.		For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.
Line 15:		Line 15:
	Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.		Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.

	There are times where bugs need to be fixed for versions of ~~XBMC~~ packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.		There are times where bugs need to be fixed for versions of Kodi packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.

	== Uploads to Release Suites ==		== Uploads to Release Suites ==

NedBot: Robot: Substituting template: Name

2014-06-05T20:28:02Z

Robot: Substituting template: Name

← Older revision		Revision as of 20:28, 5 June 2014
Line 1:		Line 1:
	Here are a some notes related to uploading ~~{{name}}~~ to Debian and having it synced to Ubuntu.		Here are a some notes related to uploading XBMC to Debian and having it synced to Ubuntu.

	== Uploads to Development Suites ==		== Uploads to Development Suites ==
Line 7:		Line 7:
	Any package that is in Debian can be synced to Ubuntu. That process is described at https://wiki.ubuntu.com/SyncRequestProcess.		Any package that is in Debian can be synced to Ubuntu. That process is described at https://wiki.ubuntu.com/SyncRequestProcess.

	All packages are normally uploaded to either the "unstable" suite, or the "experimental" suite of Debian. Generally, whenever a new release of ~~{{name}}~~ is done, the suite to upload these new ~~{{name}}~~ packages is the "unstable" suite. Packages uploaded to unstable enter a period where they stay in unstable to get tested. Once this time where it's in unstable ends, the packages are migrated to the "testing" suite where it will be shipped in the next release of Debian. So long as no [http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#rc-bugs release critical bugs] exist for the ~~{{name}}~~ package in the [http://www.debian.org/Bugs/ Debian Bug Tracking System], the packages will be migrated to testing. If release critical bugs do exist, a new upload should be made that fixes these bugs.		All packages are normally uploaded to either the "unstable" suite, or the "experimental" suite of Debian. Generally, whenever a new release of XBMC is done, the suite to upload these new XBMC packages is the "unstable" suite. Packages uploaded to unstable enter a period where they stay in unstable to get tested. Once this time where it's in unstable ends, the packages are migrated to the "testing" suite where it will be shipped in the next release of Debian. So long as no [http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#rc-bugs release critical bugs] exist for the XBMC package in the [http://www.debian.org/Bugs/ Debian Bug Tracking System], the packages will be migrated to testing. If release critical bugs do exist, a new upload should be made that fixes these bugs.

	'''NOTE''' that if any release critical bugs are found in the version of ~~{{name}}~~ that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.		'''NOTE''' that if any release critical bugs are found in the version of XBMC that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.

	For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.		For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.
Line 15:		Line 15:
	Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.		Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.

	There are times where bugs need to be fixed for versions of ~~{{name}}~~ packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.		There are times where bugs need to be fixed for versions of XBMC packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.

	== Uploads to Release Suites ==		== Uploads to Release Suites ==

NedBot: Bot: Automated text replacement (- XBMC + {{name}} )

2014-06-05T01:01:59Z

Bot: Automated text replacement (- XBMC + {{name}} )

← Older revision		Revision as of 01:01, 5 June 2014
Line 1:		Line 1:
	Here are a some notes related to uploading ~~XBMC~~ to Debian and having it synced to Ubuntu.		Here are a some notes related to uploading {{name}} to Debian and having it synced to Ubuntu.

	== Uploads to Development Suites ==		== Uploads to Development Suites ==
Line 7:		Line 7:
	Any package that is in Debian can be synced to Ubuntu. That process is described at https://wiki.ubuntu.com/SyncRequestProcess.		Any package that is in Debian can be synced to Ubuntu. That process is described at https://wiki.ubuntu.com/SyncRequestProcess.

	All packages are normally uploaded to either the "unstable" suite, or the "experimental" suite of Debian. Generally, whenever a new release of ~~XBMC~~ is done, the suite to upload these new ~~XBMC~~ packages is the "unstable" suite. Packages uploaded to unstable enter a period where they stay in unstable to get tested. Once this time where it's in unstable ends, the packages are migrated to the "testing" suite where it will be shipped in the next release of Debian. So long as no [http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#rc-bugs release critical bugs] exist for the ~~XBMC~~ package in the [http://www.debian.org/Bugs/ Debian Bug Tracking System], the packages will be migrated to testing. If release critical bugs do exist, a new upload should be made that fixes these bugs.		All packages are normally uploaded to either the "unstable" suite, or the "experimental" suite of Debian. Generally, whenever a new release of {{name}} is done, the suite to upload these new {{name}} packages is the "unstable" suite. Packages uploaded to unstable enter a period where they stay in unstable to get tested. Once this time where it's in unstable ends, the packages are migrated to the "testing" suite where it will be shipped in the next release of Debian. So long as no [http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#rc-bugs release critical bugs] exist for the {{name}} package in the [http://www.debian.org/Bugs/ Debian Bug Tracking System], the packages will be migrated to testing. If release critical bugs do exist, a new upload should be made that fixes these bugs.

	'''NOTE''' that if any release critical bugs are found in the version of ~~XBMC~~ that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.		'''NOTE''' that if any release critical bugs are found in the version of {{name}} that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.

	For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.		For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.
Line 15:		Line 15:
	Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.		Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.

	There are times where bugs need to be fixed for versions of ~~XBMC~~ packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.		There are times where bugs need to be fixed for versions of {{name}} packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.

	== Uploads to Release Suites ==		== Uploads to Release Suites ==

Ned Scott at 04:47, 21 October 2012

2012-10-21T04:47:33Z

← Older revision		Revision as of 04:47, 21 October 2012
Line 27:		Line 27:
	* http://packages.qa.debian.org/x/xbmc.html		* http://packages.qa.debian.org/x/xbmc.html
	* https://launchpad.net/ubuntu/+source/xbmc		* https://launchpad.net/ubuntu/+source/xbmc

			[[Category:Linux]]

>Amejia: Add some notable links

2012-04-08T05:06:00Z

Add some notable links

← Older revision		Revision as of 05:06, 8 April 2012
Line 22:		Line 22:

	For other cases where an upload to stable is desired, the package should instead be uploaded to [http://backports-master.debian.org/ Debian Backports]. The page describing how an upload to backports is found at http://backports-master.debian.org/Contribute/. For Ubuntu backports, the page describing uploads to backports for Ubuntu is found at https://wiki.ubuntu.com/UbuntuBackports.		For other cases where an upload to stable is desired, the package should instead be uploaded to [http://backports-master.debian.org/ Debian Backports]. The page describing how an upload to backports is found at http://backports-master.debian.org/Contribute/. For Ubuntu backports, the page describing uploads to backports for Ubuntu is found at https://wiki.ubuntu.com/UbuntuBackports.

			== Links ==

			* http://packages.qa.debian.org/x/xbmc.html
			* https://launchpad.net/ubuntu/+source/xbmc

>Amejia: Make clear how to fix bugs in packages found in testing

2012-04-08T05:00:37Z

Make clear how to fix bugs in packages found in testing

← Older revision		Revision as of 05:00, 8 April 2012
Line 15:		Line 15:
	Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.		Sync of packages from Debian to Ubuntu are automatically done at the beginning of any Ubuntu release cycle. At some point during the release cycle, the automatic sync is stopped, so a request has to be made to sync any new package from Debian to Ubuntu.

	~~Packages~~ are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.		There are times where bugs need to be fixed for versions of XBMC packages that have migrated to testing. However, packages are never uploaded directly to the "testing" suite in Debian. Attempts to upload to testing are automatically rejected. Instead, packages need to be uploaded to unstable and the [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency Urgency] field in the debian/changelog file needs to be set appropriately to get the new packages into "testing" quicker.

	== Uploads to Release Suites ==		== Uploads to Release Suites ==

>Amejia: Removal from testing can happen at any time of a Debian release cycle

2012-04-08T04:53:30Z

Removal from testing can happen at any time of a Debian release cycle

← Older revision		Revision as of 04:53, 8 April 2012
Line 9:		Line 9:
	All packages are normally uploaded to either the "unstable" suite, or the "experimental" suite of Debian. Generally, whenever a new release of XBMC is done, the suite to upload these new XBMC packages is the "unstable" suite. Packages uploaded to unstable enter a period where they stay in unstable to get tested. Once this time where it's in unstable ends, the packages are migrated to the "testing" suite where it will be shipped in the next release of Debian. So long as no [http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#rc-bugs release critical bugs] exist for the XBMC package in the [http://www.debian.org/Bugs/ Debian Bug Tracking System], the packages will be migrated to testing. If release critical bugs do exist, a new upload should be made that fixes these bugs.		All packages are normally uploaded to either the "unstable" suite, or the "experimental" suite of Debian. Generally, whenever a new release of XBMC is done, the suite to upload these new XBMC packages is the "unstable" suite. Packages uploaded to unstable enter a period where they stay in unstable to get tested. Once this time where it's in unstable ends, the packages are migrated to the "testing" suite where it will be shipped in the next release of Debian. So long as no [http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#rc-bugs release critical bugs] exist for the XBMC package in the [http://www.debian.org/Bugs/ Debian Bug Tracking System], the packages will be migrated to testing. If release critical bugs do exist, a new upload should be made that fixes these bugs.

	'''NOTE''' that ~~at the end of Debian's release cycle,~~ if ~~XBMC has~~ any release critical bugs ~~that~~ are found in the version of XBMC in testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.		'''NOTE''' that if any release critical bugs are found in the version of XBMC that has been migrated to testing, it runs the risk of getting removed from testing altogether. Thus, any release critical bugs should be handled promptly.

	For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.		For other packages such as git snapshots, beta releases, and release candidates, the packages should be uploaded to the "experimental" suite. Packages in the "experimental" suite do not get migrated to any other suite (i.e. they are not migrated to unstable or testing). This suite is typically used for packages which are snapshots, beta releases, and release candidates.