[debcargo-conf.git] / RELEASE.rst

Release
=======

For this team's purposes, the job is not done until the package gets into
Debian Testing. This is a rigorous QA process the details of which can be read
about elsewhere. 

Install graphviz and pypy3, then run::

  dev/rust-excuses.mk refresh all

which will generate a nice pretty graph of packages trying to enter Debian
Testing, along with their dependencies, and sometimes a colour representing the
reason why it's being held back. (The colours could be more sophisticated,
please help with improving the script. White does not always mean there is no
problem; the excuses page is the authoritative source on the matter.)

Generally, you should look at the bottom-most packages in this diagram, and
deal with their issues first.

You can also visit the permanent rust transition tracker here:

  https://release.debian.org/transitions/html/rust.html

This page also gives you an overview about architectures being broken for a package.
Ideally, all rust crates on this site should migrate to testing eventually.
 More details for each package can be found at:

  https://qa.debian.org/excuses.php?package=rust-$crate

or by clicking the relevant "Excuse" link on this team's `QA page`_.

.. _QA page: https://qa.debian.org/developer.php?login=pkg-rust-maintainers@lists.alioth.debian.org

It should be fairly self-explanatory on how to deal with each of the issues
mentioned on that page. Ask in #debian-rust or #debian-release or #debian-devel
if you get stuck, whichever channel seems most suitable.

Once you have dealt with all of the excuses, wait a day or so. If the excuses
page then says "Will attempt migration (Any information below is purely
informational)" and it remains in this state for more than 2 days, it means
that we have failed "Migration phase 2", whose specific failure reasons are not
mentioned in the excuses for `technical reasons`_.

.. _technical reasons: https://release.debian.org/doc/britney/short-intro-to-migrations.html#migration-phase-2-installability-regression-testing

However the reason is basically that there are other crates already in Debian
Testing that depend on the old version of the $crate you were looking at, i.e.
the one in Debian Testing not Debian Unstable. To view a summary of this, run::

  dev/list-rdeps.sh $crate

It will also give you some follow-up instructions to fix the problem.


Source-only re-upload
=====================

Two aspects of Debian infrastructure policy, run by two different teams,
interact badly when it comes to the Debian Rust Team:

1. Uploads with new binary packages have to be done as binary (not source-only)
   uploads, into the FTP team's NEW queue.
2. Uploads that are valid candidates for Debian Testing have to be source-only
   uploads, to be considered by the Release team's migration script.

For your convenience, ``./release.sh`` can do these quickly. After a
binary-upload is accepted from the NEW queue, and you merge the relevant
pending branch, do a source-only re-upload by simply running::

  RERELEASE=1 ./release.sh <rust-crate-name> [<old-version>]


Remove an obsolete package
==========================

::

  $ reportbug ftp.debian.org
  [..]
  What sort of request is this?
  [..]
   6 ROM       Package removal - Request Of Maintainer.
  [..]
  Choose the request type: 6
  [..]
  Is the removal to be done in a suite other than "unstable"? Don't select anything for "unstable"
  [..]
  Choose the suite: # input nothing here, i.e. "unstable"
  Please enter the reason for removal: obsolete package, prevents others from migrating to testing
  Is this removal request for specific architectures? [y|N|?]? n
  [..]
  # An editor will spawn, probably nano. add
  #   X-Debbugs-Cc: pkg-rust-maintainers@alioth-lists.debian.net
  # to the header, and then add the following text to the body:

  Hi, please remove this package on all architectures. It is an old rust library
  that is preventing newer ones from migrating to testing. Nothing else in the
  archive depends on it these days.

  # then save and exit, and proceed with submitting the report.
Commit	Line	Data
c798dd3a XL	1	Release
	2	=======
	3
	4	For this team's purposes, the job is not done until the package gets into
	5	Debian Testing. This is a rigorous QA process the details of which can be read
579c0f9b MG	6	about elsewhere.
	7
	8	Install graphviz and pypy3, then run::
c798dd3a XL	9
	10	dev/rust-excuses.mk refresh all
	11
	12	which will generate a nice pretty graph of packages trying to enter Debian
	13	Testing, along with their dependencies, and sometimes a colour representing the
	14	reason why it's being held back. (The colours could be more sophisticated,
	15	please help with improving the script. White does not always mean there is no
	16	problem; the excuses page is the authoritative source on the matter.)
	17
	18	Generally, you should look at the bottom-most packages in this diagram, and
7bb3957d MG	19	deal with their issues first.
	20
	21	You can also visit the permanent rust transition tracker here:
	22
	23	https://release.debian.org/transitions/html/rust.html
	24
	25	This page also gives you an overview about architectures being broken for a package.
	26	Ideally, all rust crates on this site should migrate to testing eventually.
	27	More details for each package can be found at:
c798dd3a XL	28
	29	https://qa.debian.org/excuses.php?package=rust-$crate
	30
	31	or by clicking the relevant "Excuse" link on this team's `QA page`_.
	32
	33	.. _QA page: https://qa.debian.org/developer.php?login=pkg-rust-maintainers@lists.alioth.debian.org
	34
	35	It should be fairly self-explanatory on how to deal with each of the issues
	36	mentioned on that page. Ask in #debian-rust or #debian-release or #debian-devel
	37	if you get stuck, whichever channel seems most suitable.
	38
	39	Once you have dealt with all of the excuses, wait a day or so. If the excuses
	40	page then says "Will attempt migration (Any information below is purely
	41	informational)" and it remains in this state for more than 2 days, it means
	42	that we have failed "Migration phase 2", whose specific failure reasons are not
	43	mentioned in the excuses for `technical reasons`_.
	44
	45	.. _technical reasons: https://release.debian.org/doc/britney/short-intro-to-migrations.html#migration-phase-2-installability-regression-testing
	46
	47	However the reason is basically that there are other crates already in Debian
	48	Testing that depend on the old version of the $crate you were looking at, i.e.
	49	the one in Debian Testing not Debian Unstable. To view a summary of this, run::
	50
	51	dev/list-rdeps.sh $crate
	52
	53	It will also give you some follow-up instructions to fix the problem.
d7d45996	54
baae6f7c XL	55
	56	Source-only re-upload
	57	=====================
	58
	59	Two aspects of Debian infrastructure policy, run by two different teams,
	60	interact badly when it comes to the Debian Rust Team:
	61
	62	1. Uploads with new binary packages have to be done as binary (not source-only)
	63	uploads, into the FTP team's NEW queue.
	64	2. Uploads that are valid candidates for Debian Testing have to be source-only
	65	uploads, to be considered by the Release team's migration script.
	66
	67	For your convenience, ``./release.sh`` can do these quickly. After a
	68	binary-upload is accepted from the NEW queue, and you merge the relevant
	69	pending branch, do a source-only re-upload by simply running::
	70
	71	RERELEASE=1 ./release.sh <rust-crate-name> [<old-version>]
	72
	73
d7d45996 XL	74	Remove an obsolete package
	75	==========================
	76
	77	::
	78
	79	$ reportbug ftp.debian.org
	80	[..]
	81	What sort of request is this?
	82	[..]
	83	6 ROM Package removal - Request Of Maintainer.
	84	[..]
	85	Choose the request type: 6
	86	[..]
	87	Is the removal to be done in a suite other than "unstable"? Don't select anything for "unstable"
	88	[..]
	89	Choose the suite: # input nothing here, i.e. "unstable"
	90	Please enter the reason for removal: obsolete package, prevents others from migrating to testing
	91	Is this removal request for specific architectures? [y\|N\|?]? n
	92	[..]
	93	# An editor will spawn, probably nano. add
	94	# X-Debbugs-Cc: pkg-rust-maintainers@alioth-lists.debian.net
	95	# to the header, and then add the following text to the body:
	96
	97	Hi, please remove this package on all architectures. It is an old rust library
	98	that is preventing newer ones from migrating to testing. Nothing else in the
	99	archive depends on it these days.
	100
	101	# then save and exit, and proceed with submitting the report.