Hi all,
quoting from http://wiki.meego.com/Release_Engineering/Submission_Checklist:
==============
Step 3: Changelog must refer to a feature # or bug #
* My package .changes file and commit message refer to a valid bug # or
feature # in bugzilla.
o If my change is trivial and cosmetic, then I can by-pass this step.
o For major package upgrades that include new features or major API
changes, a feature # is required. For minor package upgrades to a package that
mostly includes bug fixes, a bug # will suffice.
* If there isn't an existing bug #, then I will file one and refer to it.
* If there isn't an existing feature #, then I will file one and wait for
the product management forum to set the feature state to ACCEPTED, then submit
my change.
* Once I submit my change, I will change the status of the bug # or feature
# to RESOLVED.
==============
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?
Ciao,
Alberto
--
http://blog.mardy.it <-- geek in un lingua international!
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
