Link Farm to Release Related Info (FAQ deleted)
Read http://www.debian.org/devel/testing first.
See also the responsabilities of ftp masters (e.g. http://lists.debian.org/debian-project/2005/02/msg00184.html ).
"Release Candidate" means
Search through the archives of debian-relase which are officialy archived on the web at http://lists.debian.org/debian-release (perhaps searchable using http://www.google.ca/search?hl=en&q=%22debian-release%22+site%3Alists.debian.org&btnG=Google+Search&meta= )
Q: My package hasn't been uploaded for one or more architectures, can this be ignored?
Check the buildd logs ( http://buildd.debian.org ) for failures and queue status (see http://www.debian.org/devel/buildd/ ). See also http://www.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html#s-porting . If a rebuild is required ask the appropriate group via their e-mail address (read the developers reference for the adresses link). It's better to have a buildd build a package to make sure that one can be used to do any future security builds. If an architecture is too backed up the release team may decide to temporarily ignore it. Generally, if your package has binaries for an architecture in unstable or testing, then these binaries need to be built again for any new versions, or removed (see removing binary packages). http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=258437 or http://www.debian.org/devel/testing under "My package is stalled because it's out of date on some architecture. What do I do?" may also be useful.
(todo: fix this q up to be a step by step and perhaps host on another page)
See ReleaseProposals for proposed/proposing changes to the release process.
Release documentation is handled by debian-doc? A copy of the release notes is under development at http://cvs.debian.org/ddp/manuals.sgml/release-notes/en/release-notes.en.sgml?cvsroot=debian-doc
Real i386 info: http://higgs.djpig.de/upgrade-i386/
Other resources? debian-installer (d-i) info?