`UNRELEASED` is used because it will cause a failure if you accidentally try
to upload it, which prevents accidental releases before they are intended. At
the point of release, you should change it to be `unstable` or `experimental`
or a backports repository.
On Saturday, February 4, 2023 8:18:19 AM MST min sun wrote:
> > Hello Min Sun,
> >
> > is there a particular reason why you opt for / stick to distribution
> > `UNRELEASED` for a package already monitored by the tracker?[1] It is the
> > entry e.g., `dch -i` puts into file `/debian/changelog` when you start to
> > work on a new version (increment) of a package. After all other other
> > work on your side is done, an eventual change to the string `unstable`
> > (then lower case only) is one of the keys necessary to let results of
> > your work enter branch `unstable`, and later `testing`, etc.
>
> Thanks for your clarification, Tony,
>
> I did not mean to specify it as `UNRELEASE`, the ‘uscan and uupdate” tools
> insert this keyword to debian/changelog.
>
> I am not clear about the internal mechanism from `UNRELEASED` to `testing`
> and later stage.
>
> I need learn more about Debian policy along with your guideline.
>
> All the best.
--
Soren Stoutner
so...@stoutner.com
signature.asc
Description: This is a digitally signed message part.