I guess I'm more concerned with how developers are expected to interact with the issue lists. When I look at the issues. I'm not sure what issues are considered priority. The issues have different severity levels, but as far as usefulness, I can never really be sure how many users an issue affects, etc.
On Tue, Jan 12, 2016 at 5:24 PM, Bill Deegan <[email protected]> wrote: > Tigris bug tracker is still in active usage. > Bugs are getting filed and cleared. > We are holding some of the bugs which would have been filed (which were > invalid and/or duplicate) by asking people to go to the users mailing list > first. > > If I could I'd require users need a token to enter a new bug.. Enforce > bringing the issue to users mailing list first.. > I'm not sure how that would play out though.. > > -Bill > > On Tue, Jan 12, 2016 at 9:19 AM, William Blevins <[email protected]> > wrote: > >> >> >> On Tue, Jan 12, 2016 at 5:18 PM, William Blevins <[email protected]> >> wrote: >> >>> >>> >>> On Tue, Jan 12, 2016 at 3:58 PM, Russel Winder <[email protected]> >>> wrote: >>> >>>> On Mon, 2016-01-11 at 14:42 -0800, Bill Deegan wrote: >>>> > William, >>>> > >>>> > Yes bug triages stopped a while back. >>>> > I think about the time Greg Noel disappeared, and Steven Knight took >>>> > some >>>> > big steps back from the project. >>>> > >>>> > Ideally we'd see the ability for commits to get amended to bugs they >>>> > are >>>> > related to and vice/versa. >>>> >>>> Asynchronous triage and pull request review is much more likely to work >>>> in a scattered system. I for one always failed to turn up to triage >>>> meetings as they tended to be held at 03:30+00:00. >>>> >>> >>> You are probably right about asynchronous triage; that wasn't my >>> sticking point. I think the tigris tracker is mostly only used for >>> historical reference now. It doesn't really provide any sense of priority >>> which is fairly essential for any product growth. >>> >> >> Perhaps something like a Kanban style issue listing would go a long way? >> >> >>> >>> >>>> >>>> The Go team recognize this hence their use of Rietveld and then Gerrit >>>> to handle pull requests. I am not so sure we need that level of >>>> bureaucracy but… >>>> >>>> I am very much in favour of a BitBucket/Git/JIRA or GitHub/Git/Issues >>>> setup to get the integration of pull requests, issues, and repository. >>>> For me the current status with Tigris is unviable. I think I have even >>>> lost my Tigris login credentials. To be frank, I don't actually care >>>> that I have! >>>> >>>> -- >>>> Russel. >>>> >>>> ============================================================================= >>>> Dr Russel Winder t: +44 20 7585 2200 voip: >>>> sip:[email protected] >>>> 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] >>>> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder >>>> >>>> >>>> _______________________________________________ >>>> Scons-dev mailing list >>>> [email protected] >>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>> >>>> >>> >> >> _______________________________________________ >> Scons-dev mailing list >> [email protected] >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> > > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev > >
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
