On Tue, Dec 28, 2010 at 02:26:19PM +0100, Arnout Engelen wrote:
I wanted to remind you that stretchplayer is, as far as I can see, ready for upload.

As I didn't want to nag, but didn't want this package to be forgotten about either, I talked to Reinhard on IRC about a way to keep track. Using usertags to tag the (ITP) bugs seems like a reasonable approach. A report of tags can be obtained by:


I'd say this tag could also be used on other bugs for which a fix is available in our git.

If this seems like a good idea to you, too, I'll document this at the wiki.

Hmm. If the intend is to maintain an overview of a relatively large pile of pending tasks then using usertags seem sensible to me.

But if the intend is to ping DDs then posting to our mailinglist is better IMO.

Related to this it might be interesting to compare with how the Perl team does it:

When a package is in progress, the distribution field in changelog is set to UNRELEASED, and when the (main) maintainer(s) feel the package is ready for release the field is changed to unstable (or experimental or whatever is appropriate).

This (ab)use of the release field is supported by tools like debchange, and is also used in the tool PET which AFAIK informs on IRC about pending packages. PET was written for Subversion and currently does not support git - the Perl team is interested in that improvement, so if anyone here use IRC and see the benefit of that improvement, there is an open challenge for you.

To me it seems that if we go for a more formal way to hint packages being ready for release, then it makes sense to use (parts of) same approach the Perl team use. Perhaps it then makes sense - instead of improving PET or in addition to that - to write a git hook which auto-applies usertags?

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to