Hi, I'm wondering how does the release blocker thing work in 1.2 and MeeGo RE atm. In this SR there is 5 bugs mentioned and none of them are accepted (or even suggested) as release or update blockers? So when is that release blocker status needed exactly to get package to MeeGo 1.2?
Best Regards, Marko On Mon, Jun 13, 2011 at 7:50 AM, Peter Zhu <[email protected]> wrote: > Hi Rusty Lynch, > The following change has been accepted. See the changelog below. > > Comments: > Thank you > > Thanks, > MeeGo Release Engineering Team > > [This message was auto-generated] > --- > > Request #20541: > > submit: devel:meego-ux/meego-ux-daemon(r87) -> > MeeGo:1.2:oss:Testing/meego-ux-daemon > > > Message: > * Sat Jun 11 2011 Rusty Lynch <[email protected]> - 0.2.17 > - Fixed BMC #18694 removing a placeholder empty translation > - Fixed BMC #18907 by adding support for notifications to specify > a decline action > - Fixed BMC #15530 by finishing the support for displaying notifications > in the lockscreen > - Fix BMC #18763 by handling an unexpected corner case in the logic to map > unknown windows to desktop files. > - Fix BMC #18892 by adding support for running a first time boot application > before m-u-d IIF the first time boot app is installed and it has never been > run and successfully exited. > - supress component window warning by providing an inhibitScreenSaver > property on the mainWindow, even though this is not something we want > to provide for the homescreen > > State: accepted 2011-06-12T21:49:57 peter > Comment: Thank you > > > History: new 2011-06-12T21:04:03 rusty > > _______________________________________________ > MeeGo-commits mailing list > [email protected] > http://lists.meego.com/listinfo/meego-commits > _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
