How to make raku-* module packages migrate faster [was: Re: raku-hash-merge]

[Timo Paulssen]

AFAICT we can only reduce the time by adding autopkgtests to our package 
as well as the reverse dependencies, but there is also the possibility 
of an "unblock request" to the release team, which I assume is for when 
we make an upload after the hard freeze and the package would not be 
able to migrate to testing at all unless we get an exception made.

This was just discussed on #debian-maintainers recently, and last time I 
asked about the 10 days, which was on the 5th of may, IRC user wRAR told 
me "there is no way to get it migrate faster than 10 days".

I would of course be happy to hear of a way to get faster migrations anyway.

I wonder if it makes sense to have the tests from the modules both for 
when we build the packages, and for autopkgtest, but AIUI autopkgtest is 
more about "integration testing" with the whole system, whereas the 
tests in the module are usually a lot more like "unit tests".

https://wiki.debian.org/ContinuousIntegration/AutopkgtestBestPractices 
has this to say:

>
>   Recommendations
>
>   * Use upstream test-suite if they have as-installed test
>

But I think "as-installed" is not what the tests we have in the modules 
actually refers to, and I'm not entirely sure we can come up with tests 
for all our modules, at least not very quickly :)

HTH
   - Timo


On 5/11/25 19:18, Dominique Dumont wrote:
> On Friday, 9 May 2025 11:51:22 Central European Summer Time Santiago Vila
> wrote:
>> It might be worth
>> to contact Release Managers so that the time required for that is reduced
>> a little bit from the default 10 days.
> Do you know how to do this ?
>
> All the best
>
>
>
>
> _______________________________________________
> Pkg-rakudo-devel mailing list
> Pkg-rakudo-devel at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rakudo-devel