Hi,
as HE pointed out, if we indeed enter debian-perl@lists.debian.org in
the Maintainer field for our packages, and we have a lot of packages,
then debian-perl might get a little too flooded by all kinds of
package-related mails. The gnome team has
pkg-gnome-maintainers@lists.alitoh.debian.org, we could do the same
thing. Any comments?
In my previous mail, I said the uploader should put himself into the
changelog. This is actually not needed, he should rather use
dpkg-buildpakge -k<his keyid> to build the package, and the person in
the changelog should be listed in "Uploaders:" (otherwise it would be a
NMU).
We also have to think about how we treat the debian revisions. When HE
changed the package a bit, he added a new entry to debian/changelog,
thus bumping the debian revision to -2 and tagged it
debian_version_0_71-2. I'd rather add lines to the current
debian/changelog entry, retag the sources (cvs tag -F
debian_version_0_71-1), and only bump the debian revision if we have
released a version.
This mail is a request for comments, so comment! :-)
nomeata
--
Joachim "nomeata" Breitner
e-Mail: mail@joachim-breitner.de | Homepage: http://www.joachim-breitner.de
JID: joachimbreitner@amessage.de | GPG-Keyid: 4743206C | ICQ#: 74513189
Geekcode: GCS/IT/S d-- s++:- a--- C++ UL+++ P+++ !E W+++ N-- !W O? M?>+ V?
PS++ PE PGP++ t? 5? X- R+ tv- b++ DI+ D+ G e+>* h! z?
Bitte senden Sie mir keine Word- oder PowerPoint-Anhänge.
Siehe http://www.fsf.org/philosophy/no-word-attachments.de.html
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil