> Shall we have a wait period, then close these issues as invalid/incomplete/cannot reproduce?
+1 > Also just to mention one of the easiest way to contribute big to NetBeans is try to check if a bug is really reproducable, if not then ask back for more information. Indeed. --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Tue, Dec 25, 2018 at 10:25 PM Laszlo Kishalmi <laszlo.kisha...@gmail.com> wrote: > > Well, the list is quite interesting. If these were the only priority > things to do it wouldn't be that hard to release 11.0. Though it > displays a bit more that we shall do something about our JIRA issues. > Most issues reported on these list (especially the critical ones), > cannot be reproduced, poorly documented and/or abandoned by their creator. > > Shall we have a wait period, then close these issues as > invalid/incomplete/cannot reproduce? I'm thinking of: > > 1. Someone creates an incomplete issue in the JIRA > 2. A community member asks for update in the comments. > 3. If there is no update on the JIRA for 3 months and a community > member revisits the issue he/she can close it as > invalid/incomplete/cannot reproduce > > Alternate flow: > > 1. Someone creates an incomplete issue in the JIRA > 2. A community member asks for update in the comments. > 3. If there is no update on the JIRA for 3 months and a community > member revisits the issue he/she marks it with the label > "closeifnofeedback" > 4. Issues with "closeifnofeedback" not updated for one month can be > closed as invalid/incomplete/cannot reproduce > > Of course it is optional process. > > It would help to get rid off issues like: > > * https://issues.apache.org/jira/browse/NETBEANS-646 > * https://issues.apache.org/jira/browse/NETBEANS-885 > * https://issues.apache.org/jira/browse/NETBEANS-699 > * https://issues.apache.org/jira/browse/NETBEANS-939 > * https://issues.apache.org/jira/browse/NETBEANS-416 > > etc. There are many. > > Also just to mention one of the easiest way to contribute big to > NetBeans is try to check if a bug is really reproducable, if not then > ask back for more information. > > On 12/25/18 6:28 AM, Christian Lenz wrote: > > Hey all, > > > > until now I use NetBeans 10 VC5 and waiting for the release w/o vc5 where I > > know it will be more or less the same. So for now I have a Little list of > > my priorities for NetBeans 11: > > > > Performance: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20NETBEANS%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20%22ide%20-%20Performance%22 > > > > Criticals: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20NETBEANS%20AND%20status%20%3D%20Open%20AND%20priority%20%3D%20Critical > > > > > > So as I said this is only my „wishlist“ to taking care of. I will help as > > much as I can but hope of the help of the pros of the NetBeans IDE > > components. > > > > The other thing is, did we now decided to not have a quarterly release > > anymore still for 2019? What does that mean? What will Change? Only to come > > up with that the biggest competitor IntelliJ still has quarterly Releases > > and Eclipse now too. IMHO it will be more easier after the complete > > donation Phase as I mentioned before. > > > > We should create a Backlog for the next release like a release 11 backlog > > where we know what will implemented to have a better overview of everything. > > > > > > Cheers > > > > Chris > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
