Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
Date: Tue, 03 Nov 2009 20:33:04 +0200	[thread overview]
Message-ID: <1257272880-sup-941@tilus.net> (raw)
In-Reply-To: <20091103162047.GD2963@pineapple.q.wohnheim-jahnplatz.de>

Sebastian Schwarz, 2009-11-03 18:20:
> Moreover I'd like to advertise/suggest [Roundup][1].

Now that you mention it, I've used it in couple of projects and liked
very much.

> As a note on the ease of installation: Roundup's [documentation on
> installation][4] begins with: "Set aside 15-30 minutes."  But again
> I have no personal experience to back this claim up.  Can anyone
> comment on this or Roundup in general?

I've set it up once long time ago and I don't remember anything about
it really.  Installation was fluent I guess.  ;)

Another one I like is Redmine, but its whole a lot different kind of
tool, nice and fluent tho.  It also might do pretty much what we want,
but I'd guess Roundup does it with less tuning and pluginnig.

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  parent reply	other threads:[~2009-11-03 18:36 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
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 [this message]
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=1257272880-sup-941@tilus.net \
    --to=tero@tilus.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