Re: NEW queue and src-only uploads [Re: Bits from the Release Team: ride like the wind, Bullseye!]

Hello, On Tue 09 Jul 2019 at 08:45AM -04, Roberto C. Sánchez wrote: > Why is it, then, that binary-NEW still applies if there have been no > source files added/removed? (A SONAME bump possibly being necessitated > by some change that does not involve adding/removing/renaming source > files.)

Re: NEW queue and src-only uploads [Re: Bits from the Release Team: ride like the wind, Bullseye!]

On Tue, Jul 09, 2019 at 01:33:49PM +0100, Sean Whitton wrote: > Hello, > > On Mon 08 Jul 2019 at 02:02PM +02, Michael Biebl wrote: > > > I would go even further and drop the (manual) NEW queue for binary-NEW > > packages. > > Is there a good reason why new binary packages need manual processing

Re: NEW queue and src-only uploads [Re: Bits from the Release Team: ride like the wind, Bullseye!]

Hello, On Mon 08 Jul 2019 at 02:02PM +02, Michael Biebl wrote: > I would go even further and drop the (manual) NEW queue for binary-NEW > packages. > Is there a good reason why new binary packages need manual processing by > the FTP team? Couldn't this be fully automated? The three things the

NEW queue and src-only uploads [Re: Bits from the Release Team: ride like the wind, Bullseye!]

Am 07.07.19 um 15:43 schrieb Ben Hutchings: > On Sun, 2019-07-07 at 02:47 +0100, Jonathan Wiltshire wrote: > [...] >> No binary maintainer uploads for bullseye >> = >> >> The release of buster also means the bullseye release cycle is about to >> begin. >>