[openstack-dev] When will we stop adding new Python modules to requirements

Thomas Goirand zigo at debian.org
Sun Sep 15 15:34:06 UTC 2013


Hi,

Short version: the global-requirements.txt should be frozen asap because
otherwise, packages wont be ready.

Longer version:

I'm getting worried that, even after Havana b3 is released, we are still
getting some new Python modules added to the requirements repository.

In Debian, every new package has to go through a review process, called
the NEW queue. FTP masters review both the freeness of a package, the
exactitude of debian/copyright, and the general packaging quality.
Unfortunately, this review process can take a lot of time. At best, it
is processed within a week (which is what happened for more than a year
before November 2012), but in the worse case, it could take up to a
month or 2 (this was the case up to the end of last summer, thanks to
new manpower in the FTP team).

So I need to point it out: adding new Python modules at the end of a
release adds more risk that I will be missing some Python modules within
the Debian archive when Havana will be released.

I wouldn't have to write this mail if this was only a single module or
something. Though that's not the case, we have 4 packages added this
last week:
- falcon
- diskimage-builder
- tripleo-image-elements
- sphinxcontrib-programoutput

I do understand that they might be absolutely needed, though it would be
nice if additions to the global-requirements.txt file stopped at some
point. And as far as I am concerned, the sooner the better, so that
there's enough time to get the packages packaged, checked and tested,
uploaded, approved by the FTP masters, and ready in time in Sid.

Cheers,

Thomas



More information about the OpenStack-dev mailing list