Oslo Release Versioning
Registered by
Mark McLoughlin
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:
-
2013.1
- Started by
- Mark McLoughlin
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
