On 11/30/2010 04:02 PM, Carsten Munk wrote:
That got cut a little short.. One relevant question - you have a bugs component on bugs.meego.com too?. You should ask your users on internal side to file on meego.com - It's same code tree after all, same bugs should be valid.
Yes, we have. Indeed, the best thing would be that people directly filed bugs to the MeeGo bugzilla (which is the upstream for our project), but in practice this won't happen: all bugs are created on the bugzilla instance relevant to the project under test (for Nokia products, this is the Nokia internal bugzilla) and very rarely this information is being duplicated elsewhere.
I agree that in a perfect world, we would have a distribution maintainer that would take care of cloning the relevant bugs to the upstream bugtracker, but the sad truth is that we don't, and the same developer who fixes the bug is often the same guy who is packaging the component both for MeeGo and the Nokia internal program. It's a resourcing problem, indeed, but still it would be good if MeeGo process would acknowledge it and take some steps to make contributors' lives easier. :-)
Ciao, Alberto -- http://blog.mardy.it <-- geek in un lingua international! _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
