Submit them to your vendor, ie, Nokia (you'd have to ask them for where, because I don't know). Then they will submit it further to any upstream projects they use.
The reasoning for this (even when ignoring the complete Harmattan mess) is these steps: 1) A vendor might have modifications to the upstream packages/software or own packages/software he uses. Then he should handle it 2) If no modifications/directly from upstream, submit to the upstream project - it's a bug in that software then. 3) Upstream may handle the issue and fix may trickle down to the consumer through the vendor's path of upgrades If you can replicate an error in MeeGo.com images/components directly, you're of course welcome to submit to those bugtrackers. Example could be a Qt or Qt Mobility issue that happens on MeeGo.com images too. /Carsten 2011/6/22 Andrey Ponomarenko <[email protected]>: > Hi, > > Could anybody explain me where to post bug reports for MeeGo 1.2 Harmattan > [1]? > > To maemo.org Bugzilla [2] or to MeeGo Bugzilla [3]? > > Thanks! > > [1] MeeGo 1.2 Harmattan > [2] maemo.org Bugzilla > [3] MeeGo Bugzilla > > -- > Andrey Ponomarenko > Department for Operating Systems at ISPRAS > web: http://www.LinuxTesting.org > mail: [email protected] > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
