[pkg-nagios-changes] [Git][nagios-team/centreon-plugins][debian/master] Update changelog for 0.0~20210520-1 release
Sebastiaan Couwenberg
sebastic at xs4all.nl
Mon Sep 13 19:54:07 BST 2021
On 9/13/21 8:40 PM, Baptiste Beauplat wrote:
> On 2021/09/13 08:34 PM, Sebastiaan Couwenberg wrote:
>> On 9/13/21 8:18 PM, Baptiste Beauplat (@lyknode) wrote:
>>> -centreon-plugins (0.0~20210520-1) UNRELEASED; urgency=medium
>>> +centreon-plugins (0.0~20210520-1) unstable; urgency=medium
>>
>> While it's too late now, you should target experimental for uploads that
>> have to pass through the NEW queue so you control when it get into
>> unstable since you'll have to upload it again anyway because it wasn't
>> built on a buildd.
>
> It that a team policy?
This team doesn't have a policy.
> Since both can be done, my personal preference is
> to go through unstable twice bumping the debian revision (it's cheap
> after all and hopefully at some point dak will discard the binary). I
> consider experimental reserved for experimental versions.
I chose to upload to experimental because unstable is meant for packages
that are intended for testing migration, because NEW packages cannot
migrate to testing they get uploaded to experimental first.
It's also a good practice in case that new package triggers a transition.
When you are unable to do the second upload due to VAC or some such it
prevents the need for the Release Team to file RC bugs for packages that
fail to migrate.
Since this team has no policy, you can do pretty much whatever you want.
I'm just sharing my best practices. If we're not trying to help
eachother what use is there for team maintenance?
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
More information about the pkg-nagios-changes
mailing list