[Pkg-rust-maintainers] Getting rid of the NEW step for binaries ?

[Sylvestre Ledru]

Hello Ftp masters,

As you probably noticed ;)  a bunch of us have been working on getting 
more rust based software into the archive.
Because of the nature of Rust dependencies, we are generating new binary 
packages very often. Probably more
than most of the teams before.

Even if you have a good track record on accepting such new packages in 
reasonable time, the rust packaging team
feels demotivated by this step. It is preventing us to move faster and 
causes some important frictions in our processes
(and as the Rust ecosystem had a huge success lately and is still pretty 
young, a lot of changes are happening, requiring
more agility).

In parallel, the frustration increased recently because of binary upload 
for new packages + source upload to allow transition.
This creates a lot of manual steps for a process which could be more 
automated.

Moreover, the creation (or deletion) of new packages is automatically 
managed by debcargo (our tooling).

As I don't recall a new binary being rejected in rust by ftpmaster, I 
would like to propose that we get rid of the NEW
step for new binaries. At least for packages starting with rust-*. Is 
that something you could consider?

Thanks for reading that far and many thanks for your hard work!

Cheers,
Sylvestre

PS: I feel the same for the llvm-toolchain packages. even if you fast 
tracked NEW for me, I am always reluctant
to create new packages from the same source because I know it might 
block me for a few days.