DogfoodingLucille
|
Size: 766
Comment:
|
← Revision 11 as of 2008-08-06 16:13:53 ⇥
Size: 2253
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from DogfoodingLucille | |
| Line 7: | Line 8: |
| * Created: [[Date(2005-04-25T23:49:02Z)]] by DanielSilverstone * Priority: NeedsPriority * People: NeedsLead, NeedsSecond * Contributors: DanielSilverstone |
* Created: <<Date(2005-04-25T23:49:02Z)>> by DanielSilverstone * Priority: HighPriority * People: DanielSilverstoneLead, LamontJonesSecond * Contributors: DanielSilverstone, DanielDebonzi, LamontJones, SteveAlexander |
| Line 12: | Line 13: |
| * Status: BrainDump, BreezyGoal, UduBof, DistroSpecification, NewSpec | * Status: BreezyGoal, UduBof, ApprovedSpec |
| Line 14: | Line 15: |
| * Malone Bug: * Packages: * Depends: |
|
| Line 18: | Line 16: |
| [[FullSearch(DogfoodingLucille)]] * UduSessions: 1, 4, 8, etc |
<<FullSearch(DogfoodingLucille)>> * UduSessions: 1 |
| Line 23: | Line 21: |
| This specification discusses the process and implications of dogfooding the Canonical archive publisher for Launchpad, which is informally known as Lucille. The term 'dogfood', in this instance, refers to the process of using the archive publisher on an internal Canonical machine for the purpose of determining whether or not the publisher is ready to enter production. Dogfooding is done with non-live but still accurate data (often imported, periodically from either production or other sources). The term 'dogfooding' also implies that we will be using the results of the archive publisher in order to "eat our own dogfood". |
|
| Line 25: | Line 25: |
| == Scope and Use Cases == | In order to be sure that the archive publisher is working properly we need to give it a long term test. The only way we can be certain is to force ourselves to rely on it working properly. Dogfooding lets us do this without forcing the rest of the world to cope when we haven't got it quite right yet. |
| Line 29: | Line 29: |
| === Data Preservation and Migration === === Packages Affected === === User Interface Requirements === |
* Use Gina to import warty, warty-updates, warty-security, hoary, hoary-updates, hoary-security and breezy into dogfood. We may use Gina to import grumpy, but this will be decided later. * Use the Canonical Archive Publisher to then publish the Ubuntu distribution in order to test the publisher. * Do this regularly (every day, hour, 30m, whatever). * After breezy's feature freeze, three months before the breezy release, encourage launchpadders to upgrade from hoary to breezy, and to use the dogfood generated archive instead of archive.ubuntu.com in their apt sources. |
| Line 37: | Line 36: |
| === UDU BOF Agenda === | * The Canonical archive publisher needs to be mostly finished before the dogfooding can begin. |
| Line 39: | Line 38: |
| === UDU Pre-Work === | ---- CategoryUdu CategorySpec |
DogfoodingLucille
Status
Created: 2005-04-25 by DanielSilverstone
Priority: HighPriority
People: DanielSilverstoneLead, LamontJonesSecond
Contributors: DanielSilverstone, DanielDebonzi, LamontJones, SteveAlexander
- Interested:
Status: BreezyGoal, UduBof, ApprovedSpec
- Branch:
- Dependents:
UduSessions: 1
Introduction
This specification discusses the process and implications of dogfooding the Canonical archive publisher for Launchpad, which is informally known as Lucille. The term 'dogfood', in this instance, refers to the process of using the archive publisher on an internal Canonical machine for the purpose of determining whether or not the publisher is ready to enter production. Dogfooding is done with non-live but still accurate data (often imported, periodically from either production or other sources). The term 'dogfooding' also implies that we will be using the results of the archive publisher in order to "eat our own dogfood".
Rationale
In order to be sure that the archive publisher is working properly we need to give it a long term test. The only way we can be certain is to force ourselves to rely on it working properly. Dogfooding lets us do this without forcing the rest of the world to cope when we haven't got it quite right yet.
Implementation Plan
- Use Gina to import warty, warty-updates, warty-security, hoary, hoary-updates, hoary-security and breezy into dogfood. We may use Gina to import grumpy, but this will be decided later.
- Use the Canonical Archive Publisher to then publish the Ubuntu distribution in order to test the publisher.
- Do this regularly (every day, hour, 30m, whatever).
- After breezy's feature freeze, three months before the breezy release, encourage launchpadders to upgrade from hoary to breezy, and to use the dogfood generated archive instead of archive.ubuntu.com in their apt sources.
Outstanding Issues
- The Canonical archive publisher needs to be mostly finished before the dogfooding can begin.
UbuntuDownUnder/BOFs/DogfoodingLucille (last edited 2008-08-06 16:13:53 by localhost)