On Thursday 30 April 2009 11:13:33 Quim Gil wrote: > These are many items but kind of makes sense to have them, isn't it. > The question is how to check and enforce them. What can be automated and > what can be evaluated via testers feedback. > > The first question is how to jump from devel to testing, which ones of > the items above (and others missing, if any) should be applied already > there. And put it in practice now in Fremantle. > > What we shouldn't do is to create extras-testing or extras and let > packages jump in without the QA process in place. Taking a buggy package > out because of a new policy is going to be much more complicated.
I might be missing something, but how is this different from, say, what debian does at http://packages.qa.debian.org ? I don't see much point reinventing (or, in this case, re-discussing) the wheel - almost all mainstream distributions do it one way or the other. Or was the question rather how such a system/policies can be customized to fit the Maemo ecosystem ?
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
