Niels, that sounds like a sage proposal to the initial uploading, what however happens when a package has gone through all this and been uploaded and "active" for a while with no real problems.
If after a period of time reports start to come in of problems, would it be wise to put in place mechanisms to temporarily demote an application back to -testing to prevent further problems for users? It happens with online applications quite often (and through no fault of the developer might I add), a required service changes their layout or data format so the app becomes unusable but the developer cannot rectify the solution immediately. gary On Tue, May 12, 2009 at 3:15 PM, Niels Breet <[email protected]> wrote: > > Just for thought since I uploaded my app to the fremantle autobuilder > > last night: > > > > The Tabletbridge application connects to Roku Soundbridge devices. > > It's pretty useless if you don't have a Soundbridge on your network. > > I'm sure there are similar applications that are not self contained. > > Of the testing group that you have available, how many will have > > Soundbridges on their network? Will my application not be allowed in > > extras because of this? > > > > One idea I'm currently working on with Jeremiah is to have 'karma' voting > for the package. This would mean that the package gets promoted > automatically either after X amount of positive votes or after X days > without negative votes. Whenever there are negative votes, the debmaster > and/or some community QA people should check the package out manually. > > Every package would go through automated QA tests first, so no package > will get promoted without at least some basic tests. > > The negative votes would serve as a warning flag for the QA people to take > a look. If no negative votes have been received then the package should > just go through. > > > I grant you can do some basic tests that the application will start > > and install but you won't be able to detect a crash or battery drain as a > > majority of the code is not executed until a connection is made. > > > > Testing applications which depend on external hardware are always hard to > test. > > > Frank > > -- > Niels Breet > maemo.org webmaster > > > _______________________________________________ > maemo-developers mailing list > [email protected] > https://lists.maemo.org/mailman/listinfo/maemo-developers >
_______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
