#format wiki #language en = Warehouse roadmap = == Current == See https://warehouse.readthedocs.io/roadmap/ . == Complete & archived == We completed these milestones between December 2017 and May 2018. See PackagingWG for details. === 1. Maintainer Minimum Viable Product milestone -- COMPLETE === [[https://github.com/pypa/warehouse/milestone/8|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 [[WarehousePackageMaintainerTesting|ask package maintainers to try, test, and report bugs against Warehouse]]. We completed this milestone on '''Feb. 20th, 2018'''. === 2. End User MVP -- COMPLETE === [[https://github.com/pypa/warehouse/milestone/9|On GitHub.]] 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|the PyPI infrastructure repository]]. We completed this milestone on '''Feb. 23rd, 2018'''. === 3: Publicize beta -- COMPLETE === [[https://github.com/pypa/warehouse/milestone/10|On GitHub.]] Prepare to [[https://pyfound.blogspot.com/2018/03/warehouse-all-new-pypi-is-now-in-beta.html|blog]], email, etc. to [[PackagingWG/PyPIBetaAnnouncement|invite Python community to test Warehouse]]. Redirect an increasing portion of ''pip install'' traffic to Warehouse, [[https://status.python.org/incidents/0gmdf90kkt8n|as we did during a load test in mid-March]]. This thus requires an infrastructure changeover. We [[https://pyfound.blogspot.com/2018/03/warehouse-all-new-pypi-is-now-in-beta.html|completed this milestone]] on '''March 26th, 2018'''. === 4: Launch: redirect pypi.python.org to pypi.org -- COMPLETE === [[https://github.com/pypa/warehouse/milestone/1|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 [[https://mail.python.org/mm3/archives/list/pypi-announce@python.org/thread/JCNO7SWQTKY54MKOZQ22PV3TUJGRM3GR/|have announced this]] on [[https://mail.python.org/mm3/mailman3/lists/pypi-announce.python.org/|the pypi-announce mailing list]]. This is ''not necessarily at feature parity'' with [[https://github.com/pypa/pypi-legacy|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 [[http://legacy.pypi.org/|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 [[https://blog.python.org/2018/04/new-pypi-launched-legacy-pypi-shutting.html|completed]] this milestone on Monday, '''16 April 2018'''. === 5: Shut Down Legacy PyPI -- COMPLETE === [[https://github.com/pypa/warehouse/milestone/7|Issues in this milestone, on GitHub.]] Prerequisites to shut down [[http://legacy.pypi.org/|legacy PyPI]]. In general, we aimied to do this once we reach feature parity, but some existing features were acceptable to complete later. The URL pypi.python.org will continue to redirect to Warehouse. We announced this on [[https://mail.python.org/mm3/mailman3/lists/pypi-announce.python.org/|the pypi-announce mailing list]]. We did this on Monday, '''30 April 2018'''.