Hi, We have a bug triage for Mer at 12:00 UTC today, happening every Monday in #mer-meeting on irc.freenode.net (http://webchat.freenode.net)
A bug triage is a process to: Ensure bug report completeness Analyze and move bug to proper component if needed Set Assignee of bug report (via "Assigned to" field) to proper bug owner if any exist Set appropriate bug priority Adjust bug severity properly (initially set by bug reporter) Resolve obvious invalid, duplication, won’t fix bugs etc. Forward bugs in upstream components to upstream bugtrackers and adding the upstream URL to the URL field of the report, if applicable Check if bugs should become tasks We'll be searching for all non-task bugs that has need-triage@ as bug assignee and go through them one by one in the meeting, utilizing the Mer MeetBot (http://wiki.debian.org/MeetBot). Software developers are more than welcome to attend, to add a technical angle and perhaps assign some bugs to themselves to work on. The bugs we will try to walk through can be found using: https://bugs.merproject.org/buglist.cgi?emailassigned_to1=1&query_format=advanced&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=trivial&bug_severity=enhancement&bug_status=NEEDINFO&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=TRIAGEDUPSTREAM&bug_status=REOPENED&email1=need-triage&emailtype1=substring bug_id short_desc component 126 Upgrade package to latest upstream util-linux 127 /usr/lib/libboardname.so.1 is not stripped properly boardname 132 python contains a timestamp python 129 Refreshing wifi conection Other BR Carsten Munk
