`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
> 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.
On Fri, Feb 03, 2023 at 07:55:08AM +, min sun wrote:
>
> Hi mentors!
>
> I packaged new version of libcommons-validator [1] and uploaded again to
> debian mentors[2], please refer to Upload #2 .
Hi!
I will review and sponsor the upload soon. Thank you for your
contribution to Debian!
Postscript:
If you already edit `debian/changelog` (`UNRELEASED` -> `unstable`), the
trailing spaces in this file equally can be removed in the same session, too.
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
Hi mentors!
I packaged new version of libcommons-validator [1] and uploaded again to
debian mentors[2], please refer to Upload #2 .
The below line from debian/maven.properties was omitted to ensure all the tests
get passed.
maven.test.failure.ignore=true
In fact all the test cases should
6 matches
Mail list logo
