Release infrastructure that supports eggification
Registered by
Christian Theune
After the eggification, we want to create releases that leverage the eggs. This has a couple of interesting problems: switch from zpkg to buildout, allow to ship a tarball with all eggs that will be picked up by buildout, provide a recipe that creates classical instances that are built with eggs and provide scripts to migrate existing Zope 3 instances to support the new release.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- Accepted for 3.4
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Jim and Christian have been working on this at the PyCon sprint. We've started creating Zope3.buildout that will resemble the base for the Zope 3.4 release.
(?)
