Installing unstable applications
This article describes how to select unstable applications while minimizing risks.
Contents |
Extras-testing vs Extras-devel
First step when minimizing risks is to disable Extras-devel -repository. Packages that are in Extras-devel, are there because the developer thinks it is not yet ready for Extras-testing. Further info can be found from Extras -article.
QA Queue
QA Queue from Extras-testing can be found at http://maemo.org/packages/repository/qa/fremantle_extras-testing/
First column is the name of the package, second is version number, and third is karma.
Karma
QA Queue karma shouldn't be mixed to personal Karma. An application needs 10 karma in order to get moved from Extras-testing to Extras. Application gains one karma, when one tester has followed instructions from Help testing software and given a thumbs up -vote for it.
So, one thumbs up means one karma and that means one guy is certain that the application is stable, doesn't fill root partition (optified) etc.
So more karma for the package, the safer it should be to install and use.
Comments
When you click a name of package, it will open a page where you can either comment the package or read comments. That can be very useful data for the decision.
Bugzilla
The address of bugtracker can be seen in same page where the comments are. Or atleast it should be there. You can use the Bugzilla search to find out if the package is already in bugzilla. Just see if the packages name can be found at product -box. If it is found, please note column "Sev", aka Severity. If you can find red items in the list, you should be atleast warned.
Staying safe
- Install only applications with top karma rates
- See all the comments left to QA Queue (can be found when clicking package name) for possible threats
- When in doubt, stop and wait for package to enter Extras.
and of course an article General precautions can be useful too.