Warehouse roadmap

Current

See https://warehouse.readthedocs.io/roadmap/ .

Complete & archived

We completed these milestones between December 2017 and April 2018. See PackagingWG for details.

1. Maintainer Minimum Viable Product milestone -- COMPLETE

On GitHub.

The point of this first milestone is to give package maintainers a solid chance to try out Warehouse and report critical bugs early. This milestone is for necessary features so we can ask package maintainers to try, test, and report bugs against Warehouse.

We completed this milestone on Feb. 20th, 2018.

2. End User MVP -- COMPLETE

On GitHub.

Necessary features for Python users (other than package maintainers) to try, test, and report bugs against Warehouse. Including infrastructure improvements tracked in the PyPI infrastructure repository.

We completed this milestone on Feb. 23rd, 2018.

3: Publicize beta -- COMPLETE

On GitHub.

Prepare to blog, email, etc. to invite Python community to test Warehouse. Redirect an increasing portion of pip install traffic to Warehouse, as we did during a load test in mid-March. This thus requires an infrastructure changeover.

We completed this milestone on March 26th, 2018.

4: Launch: redirect pypi.python.org to pypi.org -- COMPLETE

On GitHub.

Replace the legacy code base powering PyPI with Warehouse, e.g., redirect web browser and API requests for pypi.python.org to pypi.org. Warehouse (as instantiated at PyPI.org) at this milestone is good enough to be the main entryway to Python packages. We have announced this on the pypi-announce mailing list.

This is not necessarily at feature parity with the old PyPI system. We already auto deploy the master branch to both pypi.org and test.pypi.org, and pypi.org and pypi.python.org share data stores (so they're really just two different views over the same data) (and test.pypi.org and testpypi.python.org also share data store), so this is all live and able to be used right now. Thus, launching is really just flipping the switch to make people go to the new site by default.

We are temporarily keeping the legacy code base running at legacy.pypi.org for people to be able to access it until we maintain feature parity, so that people depending on something that hasn't yet been implemented have a mechanism to continue to do that.

We completed this milestone on Monday, 16 April 2018.

5: Shut Down Legacy PyPI -- in progress

Issues in this milestone, on GitHub.

Prerequisites to shut down legacy PyPI. In general, we're aiming to do this once we reach feature parity, but some existing features may be acceptable to complete later. The URL pypi.python.org will continue to redirect to Warehouse.

We will announce this on the pypi-announce mailing list.

We did this on Monday, 30 April 2018.

WarehouseRoadmap (last edited 2018-05-02 19:01:37 by SumanaHarihareswara)

Unable to view page? See the FrontPage for instructions.