Hi, On Oct 23, 2013, at 9:03 AM, Max Waterman <[email protected]> wrote:
> On 22/10/13 16:01, Balestrieri, Francesco wrote: >>>> A will report bugs in Jira, and we will be asking community members >>>> > >and anybody else who has a bug for Crosswalk to do the same. Obviously >>>> > >it's easier to use a single tracker tool, but if anybody finds Github >>>> > >useful for e.g. task tracking, there is nothing preventing that. >>> > >>> >I'd rather not have a murky situation in which some bugs end up in GitHub >>> >and >>> >others in JIRA, and the same happens to tasks and other things. Whether we >>> >agree that all bug reports go into JIRA and only JIRA or GitHub is >>> >orthogonal, >>> >what I would realy like is for everyone to agree on a single solution now >>> >and >>> >start updating whatever documentation needs to be updated. >> Yes I agree. > > I would like to offer an alternative opinion ;) > > In my experience, JIRA puts up a big barrier to filing bugs - compared to > github issues, and even other channels such as email. I know *I* have felt > the pressure to *not* file a bug, and I have also heard the same from others. How is it different? You still need to create an account, you still need to find the right components and so on. Sure the UI of Jira is a bit complex and could be improved but beside that I guess it’s the same thing. Big projects uses Jira successfully for example the Qt Project. > > IMO, being able to report bugs easily is the most important thing. Otherwise > you might not get to know about the bugs at all. > It is easy to see both extremes on this scale....make it 'impossible' to > report bugs means no bugs at all - woo hoo!; yet, allowing vague reports with > lack of info means you can't even reproduce them, let alone track how well > they are being fixed/etc. > > Yes, I understand that not being able to manage the bugs is also important, > and it occurs to me that it might be good to have a person whose > responsibility it is to capture bug reports, no matter where they are > reported, and manually import them into JIRA. > Poor person. Bug triaging is boring to the extreme that’s why in general the project agree that it should be the responsibility of everyone to triage. For example Qt Project, WebKit, Blink, Chromium uses that model, the triaging is done by everyone. QA obviously monitor the reports and triage much more but they are not the only souls to do that. In general a bug triaged by the dev team has more chance to end up to the right person than the QA Team affecting (devs know better areas of expertise). To me having two bug databases is calling for problems : we may forget bugs and worst we *impose* the entire community to check two different places which is just bad (even if as soon as someone open and issue in github you move them to JIRA by the poor guy). > Anyway, I feel that there needs to be an easier way to file bugs than JIRA, > even if JIRA is actually the final 'one true' bug repository. Well we may want to do like Chromium, a template/page ready to fill which behind the scene fill the right comboboxes and so on. https://code.google.com/p/chromium/issues/entry is dead simple. At the end the problem is not the place where to put the bug reports but rather how to make easy to report. QA should work on a simple way to report bug and the problem will be solved. Using another issue tracking system is not a good idea IMHO. P.S. : I hate JIRA. I hated when Qt project moved to it and I still hate it today. It’s ridiculously overcomplicated and cover way too many use cases that 60% of the projects don’t need making it a bloated software. > > IMO, bugzilla offerred a good 'middle ground', but it seems we're past the > point of deciding which tool to use. > > Preparing to 'disagree and commit' ;) > > Max. > _______________________________________________ > Crosswalk-dev mailing list > [email protected] > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
