Re: Allow code contributions or focus on release only?

Hi Emilian, I appreciate your work on the cleanup. I guess (virtually) everyone would like to work on new features (like in my case (Java) Local Variable Type Inference support, https://cwiki.apache.org/confluence/display/NETBEANS/JDK+Modules+Support+in+NetBeans+Module+System and others). But I

Re: Allow code contributions or focus on release only?

10 > > Von: Geertjan Wielenga > Gesendet: Mittwoch, 27. September 2017 09:35 > An: dev@netbeans.incubator.apache.org > Betreff: Re: Allow code contributions or focus on release only? > > Sure, this is why I opened this discussion thread, to see how people feel > about this. I.e.

Re: Allow code contributions or focus on release only?

Also, do take note of the advice earlier in this thread from Craig Russell: I have no dog in this particular hunt, but if it were up to me I'd > prioritize: > > getting code into repositories with clean RAT reports > getting Netbeans to build and run > creating release(s) for major platforms >

Re: Allow code contributions or focus on release only?

Sure, this is why I opened this discussion thread, to see how people feel about this. I.e., this is precisely the discussion, do people think we should focus narrowly on getting the Apache NetBeans release done or should we focus on bug fixes and features too. All options are open. Gj On Wed,

Re: Allow code contributions or focus on release only?

There's heaps of improvements: https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+9.0+-+New+and+Noteworthy Gj On Wed, Sep 27, 2017 at 9:27 AM, Emilian Bold wrote: > We should also allow some new features and improvements. We cannot have > NetBeans under

Re: Allow code contributions or focus on release only?

We should also allow some new features and improvements. We cannot have NetBeans under Apache for 1 year and basically have no Apache-contributed feature to show for, only IP cleanup and stuff like that. There's a whole lot of contributors and committers: does everybody want to do only this?

Re: Allow code contributions or focus on release only?

s, with more advanced experiences. > > Gesendet von Mail für Windows 10 > > Von: Geertjan Wielenga > Gesendet: Mittwoch, 27. September 2017 09:11 > An: dev@netbeans.incubator.apache.org > Betreff: Re: Allow code contributions or focus on release only? > > Sure your PR will get

Re: Allow code contributions or focus on release only?

ever to make it clear: my Feature is > ready for Review/use etc. > > Gesendet von Mail für Windows 10 > > Von: Geertjan Wielenga > Gesendet: Mittwoch, 27. September 2017 00:28 > An: dev@netbeans.incubator.apache.org > Betreff: Re: Allow code contributions or focus on relea

Re: Allow code contributions or focus on release only?

That all sounds like a good strategy to me. +1 Wade On Sep 26, 2017 17:44, "Craig Russell" wrote: > I have no dog in this particular hunt, but if it were up to me I'd > prioritize: > > getting code into repositories with clean RAT reports > getting Netbeans to build and

Re: Allow code contributions or focus on release only?

Agree as well and really cool to see much activity and interaction. Gj On Tue, Sep 26, 2017 at 10:16 PM, Sven Reimers wrote: > Hi all, > > I fully agree with Jan.. > > Let's try to get something released first so we know the process.. > > Hope to have some time to

Re: Allow code contributions or focus on release only?

Hi all, I fully agree with Jan.. Let's try to get something released first so we know the process.. Hope to have some time to review modules real soon now.. -Sven Am 26.09.2017 22:13 schrieb "Jan Lahoda" : > +1 (I think that if we want to get some rest and fun, we could use

Re: Allow code contributions or focus on release only?

Hi, On Tue, Sep 26, 2017 at 7:15 PM Matthias Bläsing wrote: > if I'm not mistaken, the netbeans 9 feature freeze had already happened > when the migration to apache began. I would focus on bugfixing and > blocking new features. > > With the apache migration process