#235: Stable Version Set Specification Mechanism for Use with Buildout

Contents

1. Definitions
2. Motivation
3. Assumptions
4. Proposal
5. Implementation
6. Deliverables
7. Risks
8. Progress log
9. Participants

Proposed by

Steve McMahon

Proposal type

Architecture

State

being-discussed

Definitions

 

Motivation

Even major recipes can be broken at any given moment. plone.recipe.zope2zeoserver-0.14, for example, has a syntax error.

However, solving this by including detailed version pinnings in a buildout is not a practical solution for mainstream buildout use. Mainstream integrators need to be able to do incremental updates by changing at most one line of their buildout.cfg.

 

Assumptions

 

Proposal

In #plone-frameworks 2008-08-25, wiggy and fschulze discussed managing this with a "versions=url" scheme using well-known URLs for stable set specification.

Florian said that some buildout work is underway to allow buildout to cache version information obtained from a URL, so that it would still run correctly offline.

 

Implementation

 

Deliverables

This will impact

buildout (we need the versions improvement for caching);

release process (the stable set will need to be specified with every release);

installers (which will need to use and popularize the mechanism)

Risks

Further confusing the release process;

Confusion created by changing the mechanism for specifying a version change in buildout;

It's got to be solid offline.

Progress log

 

Participants

Wichert

Florian

Steve M