[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1029186: reply: RFS: libcommons-validator-java/1:1.7-1 [Team] -- ease and speed development and maintenance of validation rules



 

> 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.


Reply to: