Skip to content

Milestones

List view

  • Beta blockers

    Issues blocking a beta feature https://pypi.org/help/#beta-badge from graduating to production. https://github.com/pypa/warehouse/issues/5661#issuecomment-515802931

    No due date
    •5/5 issues closed
    100% complete0 open5 closed

  • OTF accessibility work

    Accessibility (a11y) work funded by Open Technology Fund https://pyfound.blogspot.com/2019/03/commencing-security-accessibility-and.html .

    Due by September 30, 2019
    •83/83 issues closed
    100% complete0 open83 closed

  • OTF Security work

    2-factor auth & audit log work funded by Open Technology Fund https://pyfound.blogspot.com/2019/03/commencing-security-accessibility-and.html .

    Due by August 31, 2019
    •35/35 issues closed
    100% complete0 open35 closed

  • 3: Publicize beta

    Prepare to blog, email, etc. promotional push to invite Python community to test Warehouse. Redirect an increasing portion of `pip install` traffic to Warehouse. This thus requires an infrastructure changeover. See https://wiki.python.org/psf/WarehouseRoadmap .

    Due by March 26, 2018
    •18/18 issues closed
    100% complete0 open18 closed

  • 2: End User MVP

    Necessary features for Python users (other than package maintainers) to try, test, and report bugs against Warehouse. Including infrastructure improvements tracked in https://github.com/python/pypi-infra . May include redirecting a portion of `pip install` traffic to Warehouse.

    No due date
    •13/13 issues closed
    100% complete0 open13 closed

  • 1: Maintainer MVP

    Necessary features for package maintainers to try, test, and report bugs against Warehouse. We estimate this'll be ready by the end of February 2018. See https://wiki.python.org/psf/WarehouseRoadmap .

    Due by February 28, 2018
    •40/40 issues closed
    100% complete0 open40 closed

  • 5: Shut Down Legacy PyPI

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

    Due by April 30, 2018
    •30/30 issues closed
    100% complete0 open30 closed

  • 4: Launch: redirect pypi.python.org to pypi.org

    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. *Not necessarily at feature parity* with [the old PyPI system](https://github.com/pypa/pypi-legacy). 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 usable *right now*. Launching is really just flipping the switch to make people go to the new site by default. Legacy codebase will remain up temporarily at http://legacy.pypi.org/; see #1294. [See the whole roadmap.](https://wiki.python.org/psf/WarehouseRoadmap)

    Due by April 16, 2018
    •193/193 issues closed
    100% complete0 open193 closed