[meego-packaging] Changelog must refer to a feature # or bug #
carsten at maemo.org
Tue Nov 30 06:02:04 PST 2010
2010/11/30 Carsten Munk <carsten at maemo.org>:
> 2010/11/30 Alberto Mardegan <mardy at users.sourceforge.net>:
>> 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
> Carsten Munk
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.
More information about the MeeGo-packaging