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

Re: NEW processing during freezes (Was: R 3.0.0 and required rebuilds of all reverse Depends: of R)

On 02.04.2013 22:48, Thomas Goirand wrote:
On 04/02/2013 12:16 AM, Luca Falavigna wrote:
In a perfect world there wouldn't be any need for a NEW queue at all.
But we have to face with the reality.
We try to do our best to improve things where we can. From the FTP
Team side, we always try to be quick and helpful with our fellow
developers, and are happy to hear about suggestions how to improve
I got a bunch of suggestions...

Suggestion #1: if a package stays more than a month in the NEW
queue, then it gets automatically approved, and may be
reviewed later on. My reasoning is that more than a month,
it can become really problematic and blocks development.

No. Go back to start and learn why there is a NEW queue.

Suggestion #2: get rid of the new binary queue (not new source
package, that's different). There's no reason why the licensing
of a package changes just because the maintainer decides to add
a new binary, so it makes no sense. This would save a lot of
time for the FTP team.

No. Go back to start and learn why there is a NEW queue.

Suggestion #3: have a system where any other DD can review
a package in the NEW queue, not only the FTP masters or the
FTP assistants.

That would include publishing the contents of the NEW queue,
at least to all Debian Developers - so we might violate
licenses already.

Suggestion #4: recognized that the FTP team needs to work faster,
and get more people in the FTP team.

When did you read the last announce mail from the FTP team?
They always look for people to join. But it is a lot of
work, so rarely people like to join. Or they don't get into
the team because they fail to understand what they have to
take care of.
So when did you offer yourself to join the FTP team?

Suggestion #5: make it so that a bunch of packages can be
reviewed together, as they might depend on each other, and we
would like to avoid cases where some packages are accepted, but
can't be installed because their dependencies are in NEW.

And that breaks exactly what? Such a package will never migrate
to testing. No harm done. Also you might want to avoid to depend
on packages not yet in Debian as they might never end up in
Debian at all.

Suggestion #6: get rid of the NEW queue completely. I'm not
the only one that thinks it should be like that, and that the
licensing review process could happen after packages are
accepted. Maybe though, I'll be the only one saying it out
loud (but I'm getting used to it...).

No. Go back to start and learn why there is a NEW queue.

 Bernd Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Reply to: