Hi,

We have a bug triage for Mer at 12:00 UTC to 13:00 UTC today,
typically 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 first 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). Then we'll review tasks
afterwards and if there's enough time

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
151     Installing IMG on debian6 had some errors       IMG

Then we'll walk through not triaged tasks:

https://bugs.merproject.org/buglist.cgi?emailassigned_to1=1&query_format=advanced&bug_severity=task&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
146     maybe net-tools should be in base set?  .Project-core
147     Use --with-gnu-ld and --with-gnu-as     gcc
148     update rpmlint to version 1.4   rpmlint
153     Include xrandr to core  .Project-core
154     Evaluate zif vs zypp    .Other
157     update openssl to version 1.0.0g (note: security fixes) openssl

And then if we have enough time, we'll go through not-taken bugs and
re-review prioritization and bug content:

https://bugs.merproject.org/buglist.cgi?query_format=advanced&emailassigned_to1=1&order=Importance&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=not-taken&emailtype1=substring

bug_id  bug_severity    priority        short_desc      component
141     major   High    Updating connman package over SSH breaks connection     
connman
95      normal  High    Mer package signing is not implemented  Other
145     normal  High    Complete the Mer-OBS packaging story    OBS
73      major   Normal  ofonod segfaults at boot on N900        ofono
132     normal  Normal  python contains a timestamp     python
143     normal  Normal  vim contains timestamps vim
134     normal  Normal  rpm test cases require fakechroot       rpm
124     normal  Normal  Specifying raw image format adds syslinux +
syslinux-extlinux to the package list   mic
99      normal  Normal  No proper information shown when package doesn't
provide all needed packages     gerrit-patchset-created
127     normal  Normal  /usr/lib/libboardname.so.1 is not stripped properly     
boardname
135     normal  Normal  prelink depends on gawk but it should depend on
/bin/awk        prelink
142     normal  Normal  giflib contains a timestamp     giflib
139     normal  Low     catch pkgconfig .pc files not in -devel subpackage      
rpmlint-MeeGo
116     normal  Low     Removing nano generates warning in post scripts nano

BR
Carsten Munk


Reply via email to