I started to migrate my Bugs to Apache. They are still valid over the years. About 180 or so (more/less). So to migrate others will take users care that NetBeans moves to Apache and they will see it in JIRA or wherever. It will be good, if this could Combine with github issue tracker, because not everyone has an Apache account or want one, but most of the developers, thats my opinion, have a github account and want to create tickets there, this is more transparent for all of us.
I have things at my daily work, which are pain in the asses, like the update functionality of NPM packages per Project, or the search to adding a new one, or the biggesete Problem is to have multiple files which Points to different Project types in one Project. Which Project will win? I had a html5 project with a package json, now we added a pom file to it because we needed it for Nexus and now it is a maven Project…so my stuff like build theHTML5 project, run grunt or gulp or npm or the other Options made only for the HTML5 project, doesn’t work anymore. And and and. Had long discussions about that but in the and, if we want to let the community be a part of it, we should spread it more widely and not only over Mailing lists. Often People uses what is new and fancy, yeah that is not the Apache way but we should not force that People that they Need this stuff. Gesendet von Mail für Windows 10 Von: Geertjan Wielenga Gesendet: Freitag, 13. Oktober 2017 13:35 An: [email protected] Betreff: Re: NetBeans 9 release date On Fri, Oct 13, 2017 at 1:28 PM, Antonio Vieiro <[email protected]> wrote: > > BTW, will all the issues at netbeans.org be migrated to JIRA? > There are various schools of thought on this question. We could move all issues over. Many of the issues are old or out of date or irrelevant, i.e., for features that are no longer there, etc. It would be a massive task for someone to, once the issues are moved, evaluate all of them. It's certainly doable. A different approach is to create issues from scratch, i.e., the issues we create in Apache NetBeans JIRA from scratch will be issues that the Apache NetBeans community cares about, versus heaps of issues in the Oracle NetBeans Bugzilla that maybe no one in Apache NetBeans will be concerned about but that would need to be evaluated anyway if we were to migrate everything over to Apache NetBeans JIRA. We could back up the Bugzilla issues somewhere and refer to them or link to them as needed in Apache NetBeans JIRA. Anyway, multiple approaches and if we can't agree on a specific way forward we could vote on it. Gj
