[DRE-maint] Tags / repository state

[Paul van Tilburg]

Hello all,

Our team is getting big, the number of packages is increasing but a lot
of us are by far not as active anymore as we once were.  ;)
That is a pity, sure, but besides the point I really want to make:

Due to the above reasons it is important that the repository is clean,
up-to-date and we have useful overviews such as Debian QA developer
page, dpts and PET.  However, I want to ask you (again) to really take
care and TAG YOUR UPLOADS.  Also make sure that if there are NMUs or
maintenance of "our" packages outside our repository for some reason
that the CHANGES ARE COMMITTED to our repository.

Pardon me caps, but I feel like I'm living in a student home/dowm
where I have to clean up after everyone.

A second thing; we've discussed about this before:  I have stopped
creating and commiting dummy "new" changelogs after tagging.
I'm suggesting we all stop doing this. (Some people were doing this
for a long time already and it's confusing two have two standards.)

So, after updating a package, running lintian, debi, local tests, 
debsign and dput run:
 $ svn-buildpackage --svn-only-tag --svn-noautodch

Later, when starting work on a new (upstream/debian) revision, do:
 $ dch -D UNRELEASED -i/-v <version> 
and use dch -r and debcommit when you want to upload to unstable.
This prevents some of us that work on all packages to upload something
that was not ready (hence UNRELEASED).  We should be able to assume that
packages marked unstable, one version lower than what's in the archive
is ready for upload.

Kind regards,
Paul

P.S. I'll update the website too about this soon.  If someone could do
  this sooner than me, great!

-- 
PhD Student @ Eindhoven                     | email: paulvt at debian.org
University of Technology, The Netherlands   | JID: paul at luon.net
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181