I left out the -dev list from the reply On Mon, 2010-10-18 at 13:57 +0300, Matti Airas wrote: > (Cross-posting to meego-dev and meego-packaging since the first attempt > at meego-packaging didn't yield any responses. Sorry for the > inconvenience.) > > Hi, > > Once I have built some Python packages in my home project at MeeGo OBS, > what is the proper workflow to get the packages integrated into the core > (and handset) repos? > > Specifically, I'd initially be interested getting python-pexpect from > home:mairas in there (it's used internally at Nokia by some teams but > obviously has potentially wider interest), and after that the PySide: > Python for Qt toolchain and the respective Python bindings for Qt, Qt > Mobility, and MeeGo Touch Framework. > > Cheers,
High level description for the process here: http://wiki.meego.com/Release_Engineering/Process#How_the_code_reaches_the_Trunk.2FRelease That IMO could be made a bit clearer. AFAIK in general you should request promotion for those packages from devel: project (not your home:). It helps if you have some feature request in bugzilla requesting functionality that your packages provides. You can do the promotion request using osc. something like osc submitrequest devel:your_project package-name Trunk:Testing -m "message with references to relevant bugzilla entries" After some time you'll get the verdict to your email from release engineering team. Someone from release engineering might have better answers for you. -Timo > > ma. > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
