sivan at omniqueue
Jun 22, 2011, 12:04 AM
Post #1 of 1
In Nokia developer, there's a special section for that. This also
Re: [MeeGo-dev] Where to post bug reports for MeeGo 1.2 Harmattan?
holds for S60 which is Nokia adaptation of Symbian.org together with
their cut of UX. Mind you, I never got a response from the bugs I
submitted as this is a non public issue tracking system. I would say
we should try to speak to Nokia people to at least have some sort of
public issue tracking so we'd be able to know if the issue is being
taken care of, rejected, or ignored altogether.
On Wed, Jun 22, 2011 at 7:40 AM, Carsten Munk <carsten [at] maemo> wrote:
> 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 forro 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.
> 2011/6/22 Andrey Ponomarenko <aponomarenko [at] ispras>:
>> Could anybody explain me where to post bug reports for MeeGo 1.2 Harmattan
>> To maemo.org Bugzilla  or to MeeGo Bugzilla ?
>>  MeeGo 1.2 Harmattan
>>  maemo.org Bugzilla
>>  MeeGo Bugzilla
>> Andrey Ponomarenko
>> Department for Operating Systems at ISPRAS
>> web: http://www.LinuxTesting.org
>> mail: aponomarenko [at] ispras
>> MeeGo-dev mailing list
>> MeeGo-dev [at] meego
> MeeGo-dev mailing list
> MeeGo-dev [at] meego
maemo-developers mailing list
maemo-developers [at] maemo