Re: Bug#801253: O: wicd -- wired and wireless network manager
Hi,
toogley wrote:
> what exactly needs to be changed in the package to be uploaded in
> unstable?
In general or in case of wicd as of now? In general there can be many
reasons. A common one is though the one which currently applies to wicd:
I want to wait with the next upload until the current package in
unstable as propagated to testing.
https://packages.qa.debian.org/w/wicd.html currently says:
* Too young, only 8 of 10 days old
* Not considered
urgency=low = 10 days (old default value)
urgency=medium = 5 days (currently recommended as default value)
urgency=high = 2 days
I've chosen urgency=low on purpose for wicd because I think 1.7.3
should get more exposion to users in unstable than most other uploads.
And the uploads 1.7.3-1 and 1.7.3-2 have shown that this probably was
a good idea. ;-)
There though may be other reasons why a package is held back from
migrating to testing, e.g. if a package it depends on or build-depends
on, hasn't migrated to testing yet. But those usually would be shown
on https://packages.qa.debian.org/w/wicd.html as well as
https://tracker.debian.org/pkg/wicd and the source they're refering to
(https://qa.debian.org/excuses.php?package=wicd).
> Or what is the reason for waiting some time before changing from
> "UNRELEASED" to "unstable" inside the debian changelog file?
Putting "UNRELEASED" in there is solely a convention, but some tools
recognize it as "stuff currently in VCS is not yet meant/ready for
uploading", e.g.
https://udd.debian.org/dmd.cgi?email1=abe%40debian.org#todo shows "New
version: ready for upload" if there's "unstable" in there, but the
package not yet uploaded.
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Reply to: