Setting the release target on debian/changelog

Felipe Sateler fsateler at debian.org
Wed May 27 13:14:24 UTC 2015


On 27 May 2015 at 06:41, IOhannes m zmölnig (Debian/GNU)
<umlaeute at debian.org> wrote:
> finally: don't set the release-target in debian/changelog to anything
> but UNRELEASED until the package is to be uploaded.
> the exact point when the package is ready is currently to be
> determined by your sponsors rather than yourself, so just leave it at
> UNRELEASED.

In the wiki we document [1] that we should set the target when the
package is deemed ready for upload. This is not the first time I think
this is in conflict with current practice.

1. I understand our current wiki document to imply that I should set
the target to unstable even if I am being sponsored. This has the
benefit of allowing sponsors to use automated tools such as PET[2] to
see which packages are ready for upload.
2. I understand your comment (and previous comments on the list) to
imply that only the person actually uploading should set the target.
This loses the above automation possibility but allows the sponsor to
modify the changelog more easily with dch (as having a target would
make dch create a new entry).

I am fine with either, and I don't think we ever leveraged PET that
much, so maybe we do not lose much by going with 2. Which one do we
currently use? I have not sponsored that much lately, but what I did
is follow number 2.

But in either case, we should clarify our documentation.

[1] https://wiki.debian.org/DebianMultimedia/DevelopPackaging section 3.2
[2] http://pet.debian.net/pkg-multimedia/pet.cgi


-- 

Saludos,
Felipe Sateler



More information about the pkg-multimedia-maintainers mailing list