Giving up on JIRA and switching to a new system for reporting bugs? That is a great idea...
> Interesting point, > > JIRA seems very decoupled from everything else at the moment. We have a > lot of open tickets there ~3000 and we're not doing a great job keeping an > eye on it. ...because it allows the project to throw away all those bugs nobody pays attention to! > it might allow people to raise bugs more freely as more users would have GH > accounts then Apache JIRA accounts so it make it easier for users to submit > bugs.. An Apache project like NetBeans doesn't need more incoming bugs, it needs more incoming fixes! Enough of sad bitter like-to-be truthful irony. Me and my OracleLabs colleagues need to track issues and fixes on many fronts. In the internal JIRA, in the NetBeans JIRA and connect it all with pull requests. Yes, it seems that GitHub PRs and Apache JIRA issues aren't super-connected, but that's the last problem we have. Giving up on Apache JIRA isn't going to help us. Our workflow is complicated by its own. -jt Btw. thinking about switching to GitHub Issues shows that Microsoft, after taking over the GitHub, is doing really good job and is re-gaining the trust of open source communities. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
