octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Release 4.2 Kickoff


From: Nicholas Jankowski
Subject: Re: Release 4.2 Kickoff
Date: Tue, 28 Jun 2016 13:28:58 -0400

On Tue, Jun 28, 2016 at 8:36 AM, John W. Eaton <address@hidden> wrote:
On 06/28/2016 03:03 AM, LachlanA wrote:
John W. Eaton wrote
What about just tagging them as blockers in the bug tracker instead of
duplicating info in the wiki?

That also excludes those without maintainer permissions from the triage
process.

That might not be a bad thing.

I don't think it's productive if the list just fills with a lot of requests along the lines of "This bug is really important to me!!!  Fix it before the release!!!"

jwe



I think something similar came up before. a short while ago we started trying to populate the wiki with a list of bugs that were 'almost done' - patch submitted but not tested, code submitted but not a patch, etc.
http://wiki.octave.org/Short_projects

I believe some of the conversation revolved around the need to pull some of them out of the bug tracker to make a more easily accessible list, as getting a top level view from the bug tracker just wasn't very efficient (or maybe we're just not making good use of it?).

The critical comment wondered if by the time we were done we wouldn't just be wasting time manually recreating the bug tracker information. is there a better way to present what is already there and make it more accessible.

nickj

reply via email to

[Prev in Thread] Current Thread [Next in Thread]