Maintain several release channels

Registered by Sergey "Shnatsel" Davidoff

For increased availability of elementary software and ease of testing, we can implement several release channels.

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
Sergey "Shnatsel" Davidoff
Direction:
Approved
Assignee:
Sergey "Shnatsel" Davidoff
Definition:
Approved
Series goal:
Accepted for 0.2-luna
Implementation:
Implemented
Milestone target:
None
Started by
Sergey "Shnatsel" Davidoff
Completed by
Sergey "Shnatsel" Davidoff

Related branches

Sprints

Whiteboard

Sounds good. What if there are a few ppas, by category? Example: elementary-stable, elementary-testing... by default, only the stable repo is marked but a user would be able to easily go in and mark the testing ppa.

One could even go further and have: elementary-stable, elementary-testing, postler-trunk, midori-trunk, etc... This way one can also set updates on a per app basis or just set the whole thing. Huh. Maybe a plug for switchboard would be nice for handling software sources... Oh my. I wish I had time, got a mockup in mind.
--ottorobba

ottorobba: please propose your changes in the full specification (there's a link to it beneath the summary). --shnatsel

shnatsel: my apologies. Added it to the full specification. :)

Stable, Testing, and per-app PPAs seems like a lot of PPAs, but I can't think of a better setup. I'm fine with whatever. --codygarver

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.