Personal Packages Archives
Individual developers will be able to "branch" any package being managed in Launchpad. They will be able to work on that package, publishing their commits as source code. Whenever they are ready to publish a new binary release, they will ask Launchpad to build the package, at which point the binary packages will be published in that person's Personal Package Archive.
Blueprint information
- Status:
- Complete
- Approver:
- Mark Shuttleworth
- Priority:
- Essential
- Drafter:
- Mark Shuttleworth
- Direction:
- Needs approval
- Assignee:
- Celso Providelo
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Celso Providelo
- Completed by
- Joey Stanford
Whiteboard
The initial implementation was started in london sprint but never tested or finished.
cprov 20/Jun/2006: decreasing priority.
sabdfl 30/Jun/2006: this is my top Soyuz priority, it is essential, and needs to be implemented before the end of August. Also, this can be implemented without any HCT support as straight source package upload, build and publishing.
cprov 11/Aug/2006: target to Soyuz-1.0
MishaS 11/Nov/2006: what is the target date for Soyuz-1.0?
This was dropped from Soyuz 1.0 proper (or Soyuz 1.0 is misaligned with Launchpad 1.0, which will be confusing), but we have good progress on the blocker specs and it will most likely be Soyuz 1.1.
2007-05-23: jjs- retargeting to 1.1.6. We're almost there.
2007-07-19: Rinchen - setting to implement so I can close out 1.1.6.
2007-07-19: MishaS: any pointers to the documentation? the spec seems to be internal...
Work Items
Dependency tree
* Blueprints in grey have been implemented.
