2010/11/30 Alberto Mardegan <[email protected]>: > Can we please get rid of this overhead? At least for the components I > maintain, in most of the cases bugs are filed to our internal Nokia > bugzilla, and copying that information to the meego bugzilla doesn't really > add much value. Isn't it enough if all changes are properly explained in the > .changes file?
I think one reason is that there has to have been a problem in the MeeGo stack for it to be accepted in. I mean, if a bug manifests on (wild example) Debian on SPARC but not in MeeGo, why should that be a reason for a package update alone? One relevant question - you have a You should ask your users on internal side to file on meego.com. Same code tree - same bugs should be valid BR Carsten Munk _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
