Empowering Flavors
This session is about providing tooling which would allow the flavors to have total control over their release schedule and image creation.
Blueprint information
- Status:
- Not started
- Approver:
- Pete Graner
- Priority:
- High
- Drafter:
- Pete Graner
- Direction:
- Needs approval
- Assignee:
- Adam Conrad
- Definition:
- New
- Series goal:
- Accepted for raring
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
I think this spec would be better named foundations-
[stgraber]: Flavor/Flavour is the preferred term to refer to an approved flavour of Ubuntu (edubuntu, kubuntu, lubuntu, mythbuntu, ubuntu studio and xubuntu).
"Derivative" refers to an unofficial out-of-the-archive Ubuntu-based distro.
[ScottK]: What we are talking about is not about derivatives.
[vorlon]: correct. Namespace issues notwithstanding, these are flavors, not derivatives.
* Does the RT need to track release tracking bugs or can this be left up to individual teams?
* Who liaises with flavours?
* Is someone in charge of the common section & coordination of the release notes?
* Can freezes be done on an opt-in basis by flavors as desired?
