|
Size: 3010
Comment: Initial roadmap conversion from GitHub
|
Size: 4235
Comment: link to beta announcement blog post
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| Line 5: | Line 4: |
| Line 8: | Line 6: |
| == 1. Maintainer MVP milestone == |
== 1. Maintainer Minimum Viable Product milestone -- COMPLETE == |
| Line 12: | Line 9: |
| 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. | 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]]. |
| Line 14: | Line 11: |
| == 2. End User MVP == | We completed this milestone on '''Feb. 20th, 2018'''. |
| Line 16: | Line 13: |
| == 2. End User MVP -- COMPLETE == | |
| Line 18: | Line 16: |
| 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]]. May include redirecting a portion of ''pip'' install traffic to Warehouse. | 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]]. |
| Line 20: | Line 18: |
| == 3: Publicize beta == | We completed this milestone on '''Feb. 23rd, 2018'''. |
| Line 22: | Line 20: |
| == 3: Publicize beta -- COMPLETE == | |
| Line 24: | Line 23: |
| Blog, email, etc. to invite Python community to test Warehouse. Redirect an increasing portion of ''pip install'' traffic to Warehouse. | 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. |
| Line 26: | Line 25: |
| == 4: Launch: redirect pypi.python.org to pypi.org == | We [[https://pyfound.blogspot.com/2018/03/warehouse-all-new-pypi-is-now-in-beta.html|completed this milestone]] on '''March 26th, 2018'''. |
| Line 28: | Line 27: |
| == 4: Launch: redirect pypi.python.org to pypi.org -- COMPLETE == | |
| Line 30: | Line 30: |
| Replace the legacy code base powering PyPI with Warehouse, e.g., redirect web browser 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 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 diffrent 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'', so launching is really just flipping the switch to make people go to the new site by default. We're going to have to keep the legacy code base running somewhere 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 some mechanism to continue to do that. | 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]]. |
| Line 32: | Line 32: |
| == 5: Shut Down Legacy PyPI == | 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. |
| Line 34: | Line 34: |
| 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 completed this milestone on Monday, '''16 April 2018'''. == 5: Shut Down Legacy PyPI -- in progress == |
|
| Line 36: | Line 41: |
| 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. | Prerequisites to shut down [[http://legacy.pypi.org/|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 [[https://mail.python.org/mm3/mailman3/lists/pypi-announce.python.org/|the pypi-announce mailing list]]. We plan to do this on Monday, '''30 April 2018'''. |
| Line 39: | Line 48: |
| Line 45: | Line 53: |
Warehouse roadmap
As we develop Warehouse, here are the milestones along the way. To talk about them with us, please contact us.
1. Maintainer Minimum Viable Product milestone -- COMPLETE
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
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
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
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
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 plan to do this on Monday, 30 April 2018.
6. Post Legacy Shutdown
Issues that become unblocked once legacy is dead (RIP).
Cool but not urgent
Wishlist; not part of the critical path for shutting down legacy PyPI.