From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6082 Path: news.gmane.org!not-for-mail From: Alain Toussaint Newsgroups: gmane.linux.lib.musl.general Subject: Re: Time for a bug tracker? Date: Thu, 4 Sep 2014 22:38:48 -0400 Message-ID: References: <20140905003237.GA26722@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0160b7da71424e0502485e16 X-Trace: ger.gmane.org 1409884749 24190 80.91.229.3 (5 Sep 2014 02:39:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 5 Sep 2014 02:39:09 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6095-gllmg-musl=m.gmane.org@lists.openwall.com Fri Sep 05 04:39:04 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1XPjQT-0001KA-LI for gllmg-musl@plane.gmane.org; Fri, 05 Sep 2014 04:39:01 +0200 Original-Received: (qmail 11320 invoked by uid 550); 5 Sep 2014 02:39:00 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 11301 invoked from network); 5 Sep 2014 02:39:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=securivm.ca; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Iat1LkYlo3XTctKdqih9fcf+XsEdHJI3g1vVvry1vjg=; b=hvmzHL2QrZQo/eJLpV72q9lPB1QxQ4rmsWwRA0QlDMd1tt99FEQlIZ5fhjMj9fpuVZ Wx5KblcyQYqv+Ir671yQ/svRa11JihOw0jfjn5J63FaIFOAHLZ4xU6f2HRu7s95x3Eaq 39p+lA512fhChWAm1O/GKyYMVdEDjAXKUgnM4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Iat1LkYlo3XTctKdqih9fcf+XsEdHJI3g1vVvry1vjg=; b=F3zqNRNqAGcbcifBB0B00Wd6BhxqGuLlxvVhg1LRTkdVd4aZbTsY4HRya7FLv8s0C1 ilT6aJo/JyDhTbZ9KC9oHkceOx5eiD4jfk1mDtgb1hRekkVZ+SlTpds8GKWUOdCbQ4Vb grWKJU+R8ym9WJgTk1Ie/lRAK00wmAESTIh6cea6GLGoYSmWGRa3vj86KpoawVRojVX0 mPLneHT6vvT6N/iIZrA1OCiiCsKskTLyfBs0VuHicyw5s1bB4YkxVv7J7Ipmos2ZDT/N Ogflyt6vammO2fGRhTP56eJQozZtLkk2kFYzNqq7/mNv/xx8sTXLaxed2Zhl8eqefgsI rO+w== X-Gm-Message-State: ALoCoQkgxAfnG27USgPIMLc3HkCfuSwXpGIDHkWKZEgBzTV1/L+tqBFTKINWzP76vFdOfI9y2Dlw X-Received: by 10.152.29.129 with SMTP id k1mr8417923lah.81.1409884728932; Thu, 04 Sep 2014 19:38:48 -0700 (PDT) In-Reply-To: <20140905003237.GA26722@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:6082 Archived-At: --089e0160b7da71424e0502485e16 Content-Type: text/plain; charset=UTF-8 I haven't commented much here but at SAP (Montreal Labs where I work), we use Jira but I agree it's a heavyweight framework which is probably too much for the requirement you posted (it meet our needs) but I have 4 hours free Sunday so I'll look up for a good bug reporting system. I also plan to be more involved wrt musl in a year but in the meantime, I will strive to give more time to musl before that. Alain 2014-09-04 20:32 GMT-04:00 Rich Felker : > I'm wondering if we've reached the point yet where musl really should > have a bug/issue tracker. I know I've started to have a hard time > keeping track of open requests for bug fixes, features, etc. > > If we do add a bug tracker, here are some criteria I think would be > useful for selecting one: > > 1. Easily integrates with our current developers' and > users'/bug-reporters' preferred tools/workflows: > > - No need for heavy web browser, but convenient to use with one if you > do want to. > - Ability to query and make changes to issues via command line tool > and/or email if preferred. > > 2. Easy to link to other resources: > > - Mailing list message that reported an issue, if it was first > reported/discussed by email. > - Git commit that introduced bug, if it's a regression. > - Git commit in test repo that adds regression test, if any. > - Downstream bug reports (e.g. in musl-based distros). > > 3. Practical to host on light musl-based hosting: > > - No dependency on Apache or other bloated httpds. > - No dependency on ultra-bloated application frameworks or language > runtimes like Java, though Python, Perl, or PHP could possibly be > tolerable. > - No dependency on bloated database backends. > > One thing I'd like to consider, if/when we do setup a bug tracker, is > importing a sort of bug history, generated 90%-mechanically from musl > git history, so we can have searchable records of past bugs and > corresponding regression tests in it. One motivation for this is that > I'd like to have separate bug status for "fixed, pending regression > test" and "fixed, has regression test" so that we could track which > bugs are missing regression tests, and do that tracking for historical > bugs too. > > Any recommendations? I have the most experience with bugzilla, and > like it well enough, but I don't know where it stands for all the > criteria above. > > Rich > -- High confidence was slightly more associated with an incorrect response. source: http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1279512/ --089e0160b7da71424e0502485e16 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I haven't commented much here but at SAP (Montreal Lab= s where I work), we use Jira but I agree it's a heavyweight framework w= hich is probably too much for the requirement you posted=C2=A0(it meet our = needs)=C2=A0but I have 4 hours free Sunday so I'll look up for a good b= ug reporting system. I also plan to be more involved wrt musl in a year but= in the meantime, I will strive to give more time to musl before that.

Alain


2014-09-04 20:32 GMT-04:00 Rich Felker <dalias@libc.org>:
I'm wondering if we've reached the p= oint yet where musl really should
have a bug/issue tracker. I know I've started to have a hard time
keeping track of open requests for bug fixes, features, etc.

If we do add a bug tracker, here are some criteria I think would be
useful for selecting one:

1. Easily integrates with our current developers' and
=C2=A0 =C2=A0users'/bug-reporters' preferred tools/workflows:

- No need for heavy web browser, but convenient to use with one if you
=C2=A0 do want to.
- Ability to query and make changes to issues via command line tool
=C2=A0 and/or email if preferred.

2. Easy to link to other resources:

- Mailing list message that reported an issue, if it was first
=C2=A0 reported/discussed by email.
- Git commit that introduced bug, if it's a regression.
- Git commit in test repo that adds regression test, if any.
- Downstream bug reports (e.g. in musl-based distros).

3. Practical to host on light musl-based hosting:

- No dependency on Apache or other bloated httpds.
- No dependency on ultra-bloated application frameworks or language
=C2=A0 runtimes like Java, though Python, Perl, or PHP could possibly be =C2=A0 tolerable.
- No dependency on bloated database backends.

One thing I'd like to consider, if/when we do setup a bug tracker, is importing a sort of bug history, generated 90%-mechanically from musl
git history, so we can have searchable records of past bugs and
corresponding regression tests in it. One motivation for this is that
I'd like to have separate bug status for "fixed, pending regressio= n
test" and "fixed, has regression test" so that we could trac= k which
bugs are missing regression tests, and do that tracking for historical
bugs too.

Any recommendations? I have the most experience with bugzilla, and
like it well enough, but I don't know where it stands for all the
criteria above.

Rich



-- High confidence was slightly more associated with an incorrect response.

source: http://www.ncbi.nlm.nih.gov/pmc= /articles/PMC1279512/
--089e0160b7da71424e0502485e16--