Releases other than by the package maintainer
There are a couple of circumstances when a new version of a package
needs to be released by someone other than the usual maintainer:
* Architecture-specific patches which need to be integrated.
* Maintainer is away or can't do it for some other reason.
* Urgent security and other fixes.
I propose that we should mandate:
(a) a broad description of when you should and when you shouldn't do
this, and how not to tread on the usual maintainer's toes.
(b) that the non-usual-maintainer releases should use a particular
revision format: eg, hello-1.3-8 would become hello-1.3-8.1.
Ian.
Reply to: