CC'ing packaging ML for real now, first attempt with unregistered email failed, of course. Am sorry for the spam. And also sorry for the TOFU.
Edit: Great, ML doesn't like our CC queue either. Summary for the ML: This is about deciding whether Maliit (wiki.meego.com/Maliit, provides the input methods for MeeGo) should become a dedicated MeeGo Core OBS project. So far it was agreed that Qt and MTF should be separate projects. The most important aspect is that Maliit has a pre-testing staging area in Core OBS for its packages, which can be managed by some of our team members. Promotion of packages still follows the normal process, from there. The selected team members from our project are: * Luis Araujo <[email protected]> (integration lead) * Rakesh Cherian <[email protected]> * Jon Nordby <[email protected]> (I am still silently hoping for a dedicated Maliit OBS project, instead of being lumped together with others.) regards, Michael On Wed, 2011-06-08 at 21:47 +0000, Peters, Brad T wrote: > > -----Original Message----- > > From: Rakesh Cherian [mailto:[email protected]] > > Sent: Tuesday, June 07, 2011 11:22 PM > > > > Hello Brad > > > > I think it is good idea to separate qt and mtf . As we all know > > building qt would take a lot of time and hinders the progress of other > > packages ( building & testing ) whenever there is a new release of qt > > and i have seen couple of issues in the past regarding integration of > > new qt component. > > There seems to be consensus around this, so let do it. I'll mention it > to Rolla (CC'd), and see what we have to do to get the process rolling. > > > > > What are the devices which you usually test for the patches ? I > > assume N900, netbook ( intel chipset ) are two of them. Are there any > > more devices which we test the patches on ? This device list would help > > us to test maliit components ( atleast sanity testing) before > > submitting > > to sandboxes which would make your life simpler. > > Has Nokia QA completely gone away? We perform some QA for each vertical > before promoting to Trunk, but I don't believe we test N900 specifically. > Seems to be a Release engineering gap. > > Cheers, > Brad > > > > > - Rakesh > > On 06/08/2011 01:46 AM, ext Peters, Brad T wrote: > > >>> This person can act as your teams gateway to the Testing projects, > > >>> > > >> for > > >> > > >>> all of the MTF packages you typically work on. > > >>> > > >>> Is this acceptable to you? If so, give me a name, email, and OBS > > user > > >>> name, and I'll add them as maintainer to devel:qt-mtf:MeeGo:1.2 and > > >>> devel:qt-mtf > > >>> > > >> > > >> Well, what happens then after MTF is removed from MeeGo 1.3? > > >> > > > I would imagine the MTF packages would eventually get yanked, > > > "qt-mtf" sandbox's would be come "qt" sandboxes, and life would go > > on. > > > Ultimately though, all we're concerned with is that there is a > > > pre-Testing staging area; if you prefer to separate qt and mtf, > > > I'm all for it. > > > > > > Cheers, > > > Brad > > > > > > > > > Our > > > > > >> roadmap > > >> states that we plan the complete removal from VKB for MeeGo 1.3, so > > at > > >> that point, those qt-mtf projects would simply not be appropriate. > > >> > > >> Getting more control (either way) would help us during this invasive > > >> phase that will lead to MeeGo 1.3, but I feel that we should also > > peek > > >> beyond MeeGo 1.3 here. > > >> > > >> Thanks, > > >> Michael _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
