Oslo Release Versioning

Registered by Mark McLoughlin on 2012-11-12

Before we can release Oslo's first library package, we must agree on a versioning scheme.

The core services projects follow one versioning scheme and the client libraries follow another scheme, but this is our first time releasing a library which supports the core services.

Should Oslo library packages be part of the co-ordinated release schedule along with the core services? Or should they follow their own (ad-hoc?) release schedule?

Which versions get released to PyPi? Should we have a stable branch of these libraries with stable releases?

Needs a mailing list discussion to work through all the angles.

Blueprint information

Status:
Complete
Approver:
Mark McLoughlin
Priority:
Essential
Drafter:
Mark McLoughlin
Direction:
Approved
Assignee:
Mark McLoughlin
Definition:
Drafting
Series goal:
Accepted for grizzly
Implementation:
Implemented
Milestone target:
milestone icon 2013.1
Started by
Mark McLoughlin on 2012-12-04
Completed by
Thierry Carrez on 2013-01-08

Related branches

Sprints

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.