On 22-10-2013 18:10, Balestrieri, Francesco wrote:
-----Original Message-----
From: [email protected] [mailto:crosswalk-
[email protected]] On Behalf Of Raphael Kubo da Costa
Sent: Tuesday, October 22, 2013 1:04 PM
To: [email protected]
Subject: [Crosswalk-dev] Migration to JIRA?
I'm seeing a ton of comments to GitHub issues indicating they have been
moved to JIRA, but I don't see any emails here announcing the migration or
giving any more details about the plans other than Francesco's message that
JIRA would start being used "soon".
Since this is an open project with potentially non-Intel contributors at least
watching the mailing list, it would be good if the people involved could give
more details on the whys, whens and whats of this migration.
Fair point. We have used Github successfully until now, but as we move to more
release channels, more components, bug triage process and possibly more bug
reports from different sources, we (PM, QA and at least some of the development
leads) felt the need for a more structured bug and feature tracking tool, and
Jira was chosen. That is not to say that the same cannot be achieved with the
Github tracker, but it requires a lot of discipline and is time consuming (for
those who need to verify that the bug information is consistent) and
error-prone. The core issue is that there is no way in Github to enforce that
certain labels are present, or that if one label is present others aren't.
It is sad that we won't have an integrated solution anymore. I find it
valuable to mention pull requests, code, users, etc on the comments of
the bug.
Not to mention features like closing bugs just by mentioning on the
changelog "Fixes #123".
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
