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] sup bug tracker
Date: Sat, 07 Nov 2009 08:32:08 -0800	[thread overview]
Message-ID: <1257610340-sup-9345@masanjin.net> (raw)
In-Reply-To: <1257591624-sup-8158@tilus.net>

Reformatted excerpts from Tero Tilus's message of 2009-11-07:
> What should be the policy with issues are reported/discussed on irc or
> mailinglist but are not reported to tracker?  Should The Sup Issues
> Task Force(TM) ;) report them to tracker or try to push the original
> reporter to do it?

I would like all new issues to go on the tracker, and I think it's
completely reasonable to tell people who report things to the mailing
list or IRC to instead use the issue tracker instead.

> Should we (The SITF) skim mailinglist archives and transfer reported
> unfixed bugs (with links to archives) to tracker?

If the SITF wants to creating issues for existing bug reports, that
would be very helpful. But please don't do it to the point that you get
sick of it.

> Sup home http://sup.rubyforge.org/ is not yet pointing there.

Fixed, thanks!
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      reply	other threads:[~2009-11-07 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 16:33 William Morgan
2009-11-07 11:15 ` Tero Tilus
2009-11-07 16:32   ` William Morgan [this message]

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=1257610340-sup-9345@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