audacity 1.3.8-1 ready for upload

Reinhard Tartler siretart at
Tue Jul 21 14:29:52 UTC 2009

Free Ekanayaka <freee at> writes:

> Hi,
> |--==> On Sun, 19 Jul 2009 00:37:23 +0200, Benjamin Drung <benjamin.drung at> said:
>   BD> Am Freitag, den 17.07.2009, 20:01 +0200 schrieb Reinhard Tartler:
>   >>Benjamin Drung <benjamin.drung at> writes:
>   >>
>   >>> audacity 1.3.8-1 is now ready for upload. I am no DD, so can someone
>   >>> sponsor the upload?
>   >>
>   >>2 minor issues:
>   >>
>   >>- debian/changelog states UNRELEASED. please set this to 'unstable'. In
>   >>this case it is clear, but in general you can document here to what
>   >>suite this upload is intended for
>   BD> Now the target is set to unstable.
> I actually think that leaving UNRELEASED until the actual upload
> happens is right, as it makes it clear that the work is still in
> progress.

Well, as reviewer/uploader I don't have much problems to recognise if a
branch is not ready for upload, usually there is an sponsor request on
the mailing list or something. In this case it was much less clear if
this upload should go to experimental or unstable.

I could imagine if we have some mechanism or framework that regularily
scan over our package to see what changelogs are marked what way to
indicate what package need uploading, then this protocol would indeed
make sense. Such a thing already exists for svn, it is called PET
(package entropy tracker) and is located at Last time I looked it didn't support git,
only svn though.

Reinhard Tartler, KeyID 945348A4

More information about the pkg-multimedia-maintainers mailing list