Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
Date: Mon, 02 Nov 2009 06:53:08 -0800	[thread overview]
Message-ID: <1257173444-sup-295@masanjin.net> (raw)
In-Reply-To: <1257143690-sup-7839@tilus.net>

Reformatted excerpts from Tero Tilus's message of 2009-11-01:
> Requirement: Bug submission by email?
> I'd say we need that.

That's what we have now, basically, and what we had when we were using
ditz, and I didn't like having to do the extra work of making an issue.

> This is pretty traditional.  I'd still want to challenge a bit.  Why
> do we need severity and priority?  What would they be used for?

At least one type of ordering would be nice. There are a large class of
feature requests where my basic feeling is "sure, that would be nice,
but I've got a million other things more important to do", which I would
like to keep around as food for later thought, if nothing else, but
would like to basically ignore in the near term.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  parent reply	other threads:[~2009-11-02 14:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 21:52 Nicolas Pouillard
2009-11-02  1:17 ` Kevin Riggle
2009-11-02  8:30   ` Nicolas Pouillard
2009-11-02  7:01 ` Tero Tilus
2009-11-02  8:46   ` Nicolas Pouillard
2009-11-02  9:50     ` Tero Tilus
2009-11-02 14:58       ` William Morgan
2009-11-02 14:53   ` William Morgan [this message]
2009-11-02 17:38     ` Nicolas Pouillard
2009-11-02 14:50 ` William Morgan
2009-11-02 17:47   ` Nicolas Pouillard
2009-11-02 19:20     ` William Morgan
2009-11-02 20:23       ` Nicolas Pouillard
2009-11-02 20:40   ` Joe Wölfel
2009-11-02 21:49     ` Nicolas Pouillard
2009-11-03 14:50   ` Mike Kelly
2009-11-03 15:16     ` William Morgan
2009-11-03 15:34       ` Mike Kelly
2009-11-03 16:49         ` Reid Thompson
2009-11-03 17:03           ` Reid Thompson
2009-11-03 18:04           ` William Morgan
2009-11-03 19:30             ` Reid Thompson
2009-11-03 16:20       ` Sebastian Schwarz
2009-11-03 17:03         ` Daemian Mack
2009-11-03 18:06           ` Mike Kelly
2009-11-03 17:25         ` William Morgan
2009-11-03 17:37           ` Dan Falcone
2009-11-03 18:33         ` Tero Tilus
2009-11-03 23:11 ` Jim Cheetham
2009-11-04  0:07   ` Mike Kelly
2009-11-04  9:38     ` Michael Stapelberg
2009-11-04  9:44       ` Israel Herraiz
2009-11-04 10:00         ` Michael Stapelberg
2009-11-04 10:05           ` Israel Herraiz
2009-11-04 23:40             ` Israel Herraiz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1257173444-sup-295@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox