On 2010-09-29, at 11:25 PM, David Greaves wrote: > Just FYI we are rolling out automated bug annotation in Nokia this week and > are looking forward to being able to deploy it in core MeeGo too (needs > OBS2.1).
Why does it need obs 2.1 exactly? > > This means that whenever a package makes it into an accepted project (Trunk), > bugs are marked and the release notes are updated. > > David > > On 29/09/10 18:29, Chris Ferron wrote: >> Here are two examples from an engineer who consistently commits with >> good change logs. First example is bugs fixes and a lot of work and >> updates to a package. The second is an example of just a bunch of bug >> fixes. I personally wish everyone put as much care as this engineer. >> >> -Chris >> >> *FIRST EXAMPLE* >> >> +Fri Sep 3 04:36:59 UTC 2010 [email protected] >> + >> +- Release version in 0.1.2 (Fixes: BMC#'s 5560, 6079) >> +- Removed 0001-re-add-placeholder-icon.patch, now upstream >> +- Removed 0002-Fixed-BMC-3456-Text-should-not-be-appearing-under.patch >> + now upstream >> + >> + Fixed: >> + - BMC#5560 - MeeGite theme: does not show text in dialogs >> + - BMC#6079 - Need graphics in meegotouch theme for audio player >> + - libmeegotouchviews, small changes to switch combobox and button >> + group spacing >> + - combobx down state in List svg graphic >> + Updated: >> + - ids.txt with new icon ids >> + - Meego-Icons.svg: update to alerts, status, mini message indicators, >> + add, delete, close app. >> + - Color on back icon >> + - Constants update (trying to remove bad characters) >> + - Text color change >> + - Switch tweaking >> + - Massive update to CSS files across the board, mainly fixing >> + text-color properties. >> + - Slider, switch, progressindicator. >> + - Some changes to css to fix text color issues. >> + - More svg upgrades >> + - prog-indicator, slider, switch. Some changes to switch graphic usage >> + - Multiple svgs, mostly topical treatment. Added panel svg >> + - quicklauncher >> + - List graphics >> + - Match base and newest visual references (blue/charcoal coloring) >> + - Text color and placement in bubbileitem >> + - Placement and size of indicator icon, >> + - colorvalue.svg to match constants.ini file >> + - libmeegotouchviews.css to include mbanner and mbubbleitem >> + - Enlarged switch, changed top-padding in text fields, changed icon >> + size in comobox for indicator >> + - button, dialog, navigationbar, and splitbuton >> + Removed: >> + - Top margin from mbanner >> + - Removed some css files that were replicating Base >> + - quicklaunch (old file) >> + - mcomboxstyle.css due to unnecessary conflicts. >> + Added: >> + - Call attachment, sms common, clock, combobox arrow, drilldown arrow >> + - Middle shadow to switch graphic >> + - Speechbubble graphics >> + - Banner style for future deprecation of infobannerstyle and increased >> + top margin to be below top toolbars >> + - Commonlayouts to core >> + - Lockscreen to meego svgs >> + - media-navigationbar (tentative graphic arrangement) >> + - Launcher spinner >> + - Constants added to constants.ini file. >> >> *SECOND EXAMPLE* >> >> +Fri Sep 24 14:54:25 UTC 2010 [email protected] >> + >> +- Release 0.1.16 (Fixes: BMC# 3581,3240,6807,5586,6395,7183,6737,6738) >> + >> + Fixed: >> + - BMC#3240 - Wrong text color on all keypad buttons >> + - BMC#3581 - Can not dial a second outgoing call without holding the f... >> + - BMC#5586 - Keypad does not use correct backgrounds for buttons >> + - BMC#6395 - [REG]The keypad in dialer page is too big >> + - BMC#6737 - Audio (speaker) button does nothing >> + - BMC#6738 - Dialer does not see or use HSP paired and connected headset >> + - BMC#6807 - + and * keys should not trigger a speed call dialog >> + - BMC#7183 - Call option button group is in wrong position >> + >> >> >> >> +------------------------------------------------------------------- >> >> >> >> >> On 09/27/2010 02:30 AM, Anas Nashif wrote: >>> Hi, >>> in addition to the request below, please make sure you add a line or 2 >>> describing what has been fixed rather than just referencing the bug >>> number, for example: >>> >>> - Fixed bmc #234, bmc #236, bmc #4523 >>> >>> is not informative enough, instead, the following format should be used: >>> >>> >>> - Fixed crash in foo when doing bar (bmc #234) >>> - Fixed theme of foo when showing bar (bmc #236) >>> - Added configuration files to fix foo when doing bar (bmc #236) >>> >>> or >>> >>> - bmc #234: crash in foo when doing bar >>> - bmc #236: Use theme of foo when showing bar >>> ... >>> .. >>> >>> Thanks, >>> Anas >>> >>> >>> >>> On 2010-09-23, at 3:57 PM, Nashif, Anas wrote: >>> >>>> 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. >>>> >>>> Thanks, >>>> Anas >>>> >>> _______________________________________________ >>> MeeGo-packaging mailing list >>> [email protected] >>> http://lists.meego.com/listinfo/meego-packaging >>> >> >> _______________________________________________ >> MeeGo-packaging mailing list >> [email protected] >> http://lists.meego.com/listinfo/meego-packaging > > > -- > "Don't worry, you'll be fine; I saw it work in a cartoon once..." > _______________________________________________ > MeeGo-packaging mailing list > [email protected] > http://lists.meego.com/listinfo/meego-packaging _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
