caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Blair Zajac <blair@orcaware.com>
To: Sven Luther <luther@dpt-info.u-strasbg.fr>
Cc: Xavier Leroy <xavier.leroy@inria.fr>,
	Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Submitting patches to Ocaml
Date: Mon, 25 Nov 2002 22:59:28 -0800	[thread overview]
Message-ID: <3DE31BD0.1C7C6C88@orcaware.com> (raw)
In-Reply-To: <20021126064418.GA1126@iliana>

Sven Luther wrote:
> 
> On Mon, Nov 25, 2002 at 10:29:58AM -0800, Blair Zajac wrote:
> > Xavier Leroy wrote:
> > > Bugzilla has a reputation of being awfully hard to install.  Other bug
> > > tracking systems are better alternatives.  Jitterbug (what we
> > > currently use) is indeed simplistic, but fits our needs well.
> >
> > I've installed it several times on different sites and it wasn't
> > particularly hard.  And comparing it to writing a GC, it seems
> > simple :)  But it does take a while.
> 
> In my understanding, and from the few times i had interaction with
> bugzilla, in its gnome incarnation, it really is not as nice as you
> think it is :

<getting off topic>
I've looked at several BTS and decided to use it at several different
companies for internal use, so I've been quite happy with it.

The first thing I noticed browsing the Caml bugs was that there was
no mention of who categorized the bugs and who wrote any comments in
response to the bugs.  I always find this good info to have when
browsing bugs.

>   o you have to create an account.

With an account you get to attach your email address to a particular
bug if you want to watch it.  I've done with with one bug on Mozilla
that I've been waiting forever to finish (uploading bookmarks, history,
etc), and don't have to subscribe to a mailing list to see it's
progress.

> 
>   o you cannot use a mail interface.

True.

> 
> Both of these are possible with the ocaml BTS, and altough it would be
> nice to have some feedback when the bug report is processed, it works
> rather nicely, without the added complexity of bugzilla, which will, in
> my opinion, add more confusion than other thinks.

I think each BTS has things that others are missing.  Having used
Bugzilla in many projects, I've come to look for those pieces of
information.
</getting off topic>

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Plots of your system's performance plots - http://www.orcaware.com/orca/
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2002-11-26  6:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23  0:17 Blair Zajac
2002-11-25 10:11 ` Xavier Leroy
2002-11-25 18:29   ` Blair Zajac
2002-11-26  6:44     ` Sven Luther
2002-11-26  6:59       ` Blair Zajac [this message]
2002-11-27 14:42   ` [Caml-list] Bugzilla installation (was Re: Submitting patches to Ocaml) Tim Freeman

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=3DE31BD0.1C7C6C88@orcaware.com \
    --to=blair@orcaware.com \
    --cc=caml-list@inria.fr \
    --cc=luther@dpt-info.u-strasbg.fr \
    --cc=xavier.leroy@inria.fr \
    /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;
as well as URLs for NNTP newsgroup(s).