On Fri, Sep 24, 2010 at 09:26, Marius Vollmer <[email protected]> wrote: > ext Alexander Kanevskiy <[email protected]> writes: > >> On Thu, Sep 23, 2010 at 18:16, Roger WANG <[email protected]> wrote: >>> "Nashif, Anas" <[email protected]> writes: >>> >>>> Hi, >>>> We have noticed recently that bug fixes are being submitted but >>>> without a bug number in the change log (.changes file) but with >>>> detailed bug information in the commit message, which is used for >>>> communication, but is never part of the resulting package. >>> >>>> Please add the bmc numbers or features you are working on in the >>>> .changes file also, this is critical and otherwise changes will be >>>> declined. >>> >>> What should I do if I find a bug is fixed by the new version later, >>> after the package is accepted? >> >> if bug is not anymore reproducible with newly accepted version and >> this version doesn't link to that bug, then close bug with >> "WORKSFORME" resolution. > > There is, however, a difference between a bug that can not be reproduced > and we might thus have a bug that we haven't fixed, and a bug that is > known and fixed already, and we can forget about it. We might want to > distinguish these in Bugzilla.
We might not. If we can't link code changes to reported issue, there is no value of having information on "non-reproducible anymore in that version" bugs. -- br, Alexander Kanevskiy _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
