Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-08 Thread Armin Faltl

sorry, I see the prios differently:

Peter Clifton wrote:

Crasher / data loss - High (or perhaps even Critical if it is likely to be 
hit).
  
depends on type of data loss: high if recent changes disappear, critical 
if the design

vanishes (I know, the later is near impossible with move/write on saves)
It also depends if the data loss is immediately evident - if not it's worse.
Board output fault 

this is a catastrophic failure in a production environment

or incorrect netlist likely to cause design breakage
  
to my understanding an incorrect net will cause a design break with 
100.0% likelihood

- critical error

UI wart / cosmetics - Low
  

what is a wart ? freezes, hickups of state engine: medium
button should be more to the left = cosmetic: low


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-07 Thread Peter Clifton
On Fri, 2011-01-07 at 22:15 +, Peter Clifton wrote:
 Hi,
 
 Kai-Martin has rightly pointed out that by default, users don't have
 access to set certain flags on bugs - such as priority. This comes in
 handy if you know you're submitting a feature-request (which by default,
 should be the status Wishlist).

It has just been pointed out to me that I should _remind_ people, that
setting the priority status on their own bugs is BAD FORM.

The exception here really being Wishlist is a decent status to set
your feature-requests to. Leave them as New though, so a second pair
of eyes will look and review it too.

If you're triaging patches / bugs from other people.. I'm not sure quite
what statuses to suggest - lets try not to be too formal for now, but my
suggestions would be:

Crasher / data loss - High (or perhaps even Critical if it is likely to be 
hit).

Board output fault or incorrect netlist likely to cause design breakage
- High (or Medium depending on likelihood / severity of the design
breakage)

UI wart / cosmetics - Low
Feature request - Wishlist

If unsure.. leave it as Undecided

Most important is confirming the bug, and / or commenting on /
discovering a minimal reproduction if not well stated by the original
submitter.

Best wishes,

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-07 Thread Peter Clifton
On Fri, 2011-01-07 at 22:59 +, Peter Clifton wrote:
 On Fri, 2011-01-07 at 22:15 +, Peter Clifton wrote:
  Hi,
  
  Kai-Martin has rightly pointed out that by default, users don't have
  access to set certain flags on bugs - such as priority. This comes in
  handy if you know you're submitting a feature-request (which by default,
  should be the status Wishlist).
 
 It has just been pointed out to me that I should _remind_ people, that
 setting the priority status on their own bugs is BAD FORM.

Further suggestions.. as I've altered two of these already.

Just a style nit, but I don't think we should close any bugs with
sf-patches as Invalid.

This rather suggests that the problem the user is trying to patch is
somehow non-existent. If we decide we can't / won't accept a patch,
please close it with WontFix

Invalid should only be used for submitted patches if the issue is
filed against the wrong project, or works around a problem in the wrong
place - e.g. fixing a GTK theme bug by patching some horrific kludge
into PCB (NB: - that was a made-up example, not from an actual patch).


-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-07 Thread DJ Delorie

I would like some field that the release managers can use for scheduling
if/when a bug/patch/feature should be in a release.  I.e. if I tag a bug
as next bug release, then the next bug release has to wait until that
bug is fixed, but future bug release won't hold it back.  Etc.


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-07 Thread Peter Clifton
On Fri, 2011-01-07 at 18:47 -0500, DJ Delorie wrote:
 I would like some field that the release managers can use for scheduling
 if/when a bug/patch/feature should be in a release.  I.e. if I tag a bug
 as next bug release, then the next bug release has to wait until that
 bug is fixed, but future bug release won't hold it back.  Etc.

Take a look at the milestone feature in Launchpad. I've set up some
release milestones (on the main launchpad.net/pcb/ page), and you can
target particular bugs for particular milestones.

See for example:
https://launchpad.net/pcb/+milestone/next-bug-release

The release manager would just need to scan for bugs in the list which
are not Fix Released. (I think they sort by status, so that should be
easy even with lots of bugs).

You could also do an advanced search, and pick which milestone(s) you
want to find bugs targeted for. The URL gets a bit long then:

https://bugs.launchpad.net/pcb/+bugs?field.searchtext=orderby=-importancefield.status%3Alist=NEWfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEfield.status%3Alist=EXPIREDfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=FIXCOMMITTEDassignee_option=anyfield.assignee=field.bug_reporter=field.bug_supervisor=field.bug_commenter=field.subscriber=field.milestone%3Alist=36187field.tag=field.tags_combinator=ANYfield.has_cve.used=field.omit_dupes.used=field.omit_dupes=onfield.affects_me.used=field.has_patch.used=field.has_branches.used=field.has_branches=onfield.has_no_branches.used=field.has_no_branches=onsearch=Search

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user