* [sup-talk] sup bug tracker
@ 2009-11-06 16:33 William Morgan
2009-11-07 11:15 ` Tero Tilus
0 siblings, 1 reply; 3+ messages in thread
From: William Morgan @ 2009-11-06 16:33 UTC (permalink / raw)
To: Sup-talk mailing list
Hi all,
I've put a slightly modified Roundup installation here for tracking Sup
bugs:
http://masanjin.net/sup-bugs/
Please use this to submit your bug reports and feature requests. If you
have existing bug reports or feature requests and you don't want to rely
on my faulty memory any more, feel free to resubmit them here.
You should be able to create new issues without having to register.
However, if you want to receive email about an issue when updates
happen, you will have to register. Sorry! On the plus side, registration
is super quick because I've disabled the email confirmation step.
If anyone has written Roundup detectors in the past, let me know. There
are a couple things I'd like to tweak.
I'm going to point the 0.9.1 crash message there too.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [sup-talk] sup bug tracker
2009-11-06 16:33 [sup-talk] sup bug tracker William Morgan
@ 2009-11-07 11:15 ` Tero Tilus
2009-11-07 16:32 ` William Morgan
0 siblings, 1 reply; 3+ messages in thread
From: Tero Tilus @ 2009-11-07 11:15 UTC (permalink / raw)
To: sup-talk
William Morgan, 2009-11-06 18:33:
> If you have existing bug reports or feature requests and you don't
> want to rely on my faulty memory any more, feel free to resubmit
> them here.
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?
Should we (The SITF) skim mailinglist archives and transfer reported
unfixed bugs (with links to archives) to tracker?
> I'm going to point the 0.9.1 crash message there too.
Sup home http://sup.rubyforge.org/ is not yet pointing there.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [sup-talk] sup bug tracker
2009-11-07 11:15 ` Tero Tilus
@ 2009-11-07 16:32 ` William Morgan
0 siblings, 0 replies; 3+ messages in thread
From: William Morgan @ 2009-11-07 16:32 UTC (permalink / raw)
To: sup-talk
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-11-07 16:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-06 16:33 [sup-talk] sup bug tracker William Morgan
2009-11-07 11:15 ` Tero Tilus
2009-11-07 16:32 ` William Morgan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox