From: Jameson Rollins <jrollins@finestructure.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: bug tracking
Date: Thu, 22 Apr 2010 11:47:13 -0400 [thread overview]
Message-ID: <87d3xr8p6m.fsf@servo.finestructure.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
I now think it is essential that we put together a bug tracker for
notmuch. Things are moving pretty quickly now, which is great, but as
the UI is frequently changing, I'm stumbling upon lots of little bugs.
As I don't have the time to stop what I'm doing and figure out patches
for them all, we really need some way to report and track issues. I
really think this is essential moving forward.
I have used things like trac and redmine in the past and they work quite
well. I don't have any other useful suggestions. One of the newfangled
git-based distributed bug trackers could be cool, but I've never used
one, or gotten any feedback from anyone who has.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next reply other threads:[~2010-04-22 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 15:47 Jameson Rollins [this message]
2010-04-22 17:37 ` bug tracking David Bremner
2010-04-26 18:31 ` Carl Worth
2010-04-26 18:42 ` Arvid Picciani
2010-04-28 12:58 ` Jameson Rollins
2010-04-28 14:34 ` David Bremner
2010-04-29 17:48 ` Servilio Afre Puentes
2010-04-29 20:01 ` Mark Anderson
2010-05-03 19:44 ` Jesse Rosenthal
2010-05-03 19:06 ` Carl Worth
2010-05-03 19:32 ` Jesse Rosenthal
2011-01-13 14:43 ` Thomas Schwinge
2011-01-13 20:49 ` Jesse Rosenthal
2011-01-14 11:46 ` Andreas Amann
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3xr8p6m.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).