UbuntuBleedingEdge
|
Size: 571
Comment:
|
Size: 3265
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| This is a umbrella team for projects who wish to provide bleeding-edge, use-at-your-own-risk packages for upstream testing in a common PPA repo. | [[BR]] ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| Ubuntu too stable for you? Want to have the latest updated versions of desktop apps at your fingertips? Want to help troubleshoot application bugs before they enter Ubuntu? Well, then welcome to the Bleeding Edge! This umbrella team is for projects wishing to provide developmental, use-at-your-own-risk snapshots of packages for upstream testing. |
| Line 10: | Line 15: |
| [[BR]] [[BR]] [[BR]] = Using the Bleeding Edge Repo = ||<tablestyle="width:100%; text-align:center"> /!\ This repo is completely '''USE AT YOUR OWN RISK'''. Every attempt will be taken to ensure that packages don't break a stable system but no guarantee is given. /!\ || == Adding the repo == TBD == Reverting back to the official Ubuntu distro version of a package == = Adding a new project = TBD == Requirements == * Apps must not require any major changes to system libs. * Apps must not break a stable system. == Uploading a new package == TBD = Frequently Asked Questions = * Q: How do you decide what applications to include? * A: Our project is driven by involvement, so an application can be included when a member of that project joins the team and takes the role of maintaining it. * Q: I've found a bug in a package I got through UbuntuBleedingEdge. How do I report it? * A: Please report the issue directly to upstream. UbuntuBleedingEdge does not provide troubleshooting assistance or bug management. * Q: How do I request to have an application I use be added? * A: It is important to contact the upstream project that maintains the application, and to find someone to take on the duty of setting up and keeping an eye on things. Maybe YOU could become that someone! But for success it's critical that the upstream project feel they "own" this process, since users of it will be reporting bugs about it to them, and we want to ensure they feel they have the control to be able to update packages in the BleedingEdge when they feel it's needed. * Q: What happens if a maintainer of a package becomes inactive or too busy with other matters? === *A: If a given package has not been updated in a long while, or if its VCS snapshot has broken, or if there are other such issues that go unsolved for more than a few months, we will drop the package for inclusion in UbuntuBleedingEdge. Of course, it can be re-enabled whenever someone picks up the reins on it again. = TODO = * Flesh out this page * Flesh out the FAQ to about a dozen questions or so, as appropriate * Announce to ubuntu development discussion list * Advertise/blog/etc. to recruit involvement of upstreams that might be interested |
ContentsBRTableOfContents |
Ubuntu too stable for you? Want to have the latest updated versions of desktop apps at your fingertips? Want to help troubleshoot application bugs before they enter Ubuntu? Well, then welcome to the Bleeding Edge!
This umbrella team is for projects wishing to provide developmental, use-at-your-own-risk snapshots of packages for upstream testing.
The aim is to get users of arguably the most popular desktop distro to test applications *before* the stable release hits the official repos.
The team will be closed but will be comprised of package maintainers for a particular app.
All packages must comply to Ubuntu package rules and specifications.
Packages under this umbrella team must link to upstream bug-trackers and make upstream aware of their efforts. BR BR BR
Using the Bleeding Edge Repo
|
![Warning /!\](/moin_static198/light/img/icon_eek.png "Warning /!\"){kind=icon}
This repo is completely USE AT YOUR OWN RISK. Every attempt will be taken to ensure that packages don't break a stable system but no guarantee is given.
Adding the repo
TBD
Reverting back to the official Ubuntu distro version of a package
Adding a new project
TBD
Requirements
- Apps must not require any major changes to system libs.
- Apps must not break a stable system.
Uploading a new package
TBD
Frequently Asked Questions
- Q: How do you decide what applications to include?
- A: Our project is driven by involvement, so an application can be included when a member of that project joins the team and takes the role of maintaining it.
Q: I've found a bug in a package I got through UbuntuBleedingEdge. How do I report it?
A: Please report the issue directly to upstream. UbuntuBleedingEdge does not provide troubleshooting assistance or bug management.
- Q: How do I request to have an application I use be added?
A: It is important to contact the upstream project that maintains the application, and to find someone to take on the duty of setting up and keeping an eye on things. Maybe YOU could become that someone! But for success it's critical that the upstream project feel they "own" this process, since users of it will be reporting bugs about it to them, and we want to ensure they feel they have the control to be able to update packages in the BleedingEdge when they feel it's needed.
- Q: What happens if a maintainer of a package becomes inactive or too busy with other matters? ===
A: If a given package has not been updated in a long while, or if its VCS snapshot has broken, or if there are other such issues that go unsolved for more than a few months, we will drop the package for inclusion in UbuntuBleedingEdge. Of course, it can be re-enabled whenever someone picks up the reins on it again.
TODO
- Flesh out this page
- Flesh out the FAQ to about a dozen questions or so, as appropriate
- Announce to ubuntu development discussion list
- Advertise/blog/etc. to recruit involvement of upstreams that might be interested
UbuntuBleedingEdge (last edited 2008-08-06 16:59:41 by localhost)