[maemo-developers] extras-testing QA checklist (proposal)
From: Attila Csipa maemo at csipa.in.rsDate: Sat Oct 24 01:29:10 EEST 2009
- Previous message: extras-testing QA checklist (proposal)
- Next message: extras-testing QA checklist (proposal)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thursday 22 October 2009 14:31:38 Quim Gil wrote: >> Feedback please. This checklist is common for developers (before >> promnoting their applications to extras-testing) and betatesters (before >> giving them farewell to reach Extras). > >Lack of bug reporting database > >http://bugs.maemo.org is the preferred option. Otherwise it needs to be >identified in the http://maemo.org/packages/ page. As you might have noticed :) I ran into this one myself, so (after a short chat with GA on irc) I'd like to clarify a few things, potentially of interest to other folks in -testing, too: Is bugs.maemo.org really the preferred option ? There is no visible automatic, or user level registration of projects there, nor clear guidelines how to register a projects with b.m.o. According to GA, the process includes manual intervention and there is also no grouping (by Maemo categories), so it has great potential to get messy when projects start to migrate en masse to - testing. Opening a product for 'mirror', a one-liner script, for example, seems like a huge overkill. If we forego b.m.o, how do we identify this on the alternatively suggested packages page ? Again, I found no apparent way of entering such information on the page, nor wiki guideline (surely we don't want that sort of things stuffed into package descriptions?).
- Previous message: extras-testing QA checklist (proposal)
- Next message: extras-testing QA checklist (proposal)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]