Indeed, let's discuss it again after the last release of 2019. I think we can handle it. We should not overreact. In the meantime, can you consider spending less time sending long e-mails? We need your enthusiasm to be focused on actually helping with the Apache NetBeans releases -- maybe you can participate in the NetCAT process or in the PPMC process -- your name is not here, where it should be:
http://netbeans-vm.apache.org/synergy/client/app/#/run/29/v/2 https://lists.apache.org/thread.html/59deb812e0f9632291d0e4dfacc364fdaf6055348a35cae42f56f760@%3Cgeneral.incubator.apache.org%3E Thanks, Gj On Tue, Nov 13, 2018 at 11:17 PM Christian Lenz <[email protected]> wrote: > -1 for only 2 releases per year. This is far to less and will end up with > the Oracle model, where we only have 2 releases per year (Round About, look > at the Roadmaps, you see often big time between a new release and an old > one). We will not be competitive to other IDEs, we are still now lack of a > lot of Features (Little ones, which make everyone happy and Handy and big > ones). IMHO the biggest Problem now with the NetCat is still the donation > process. I guess, it will be less problematic after we have everything in > Apache and completed donation. > > To put it back to the JDK Version is also not good, again only IMHO, > because NetBeans is still not a Java DIE anymore we should remove this > thinking which is still in the heads of a lot of developers. And to put > that thinking away, NetBeans Needs more advertisement of the other Features > and more implementation of stuff, which is still missing (Angular, Vue, > JSON Schema, other language supports, etc.) > > How will the Patches look like? Only bug fixes? What About Major Releases > like 11, 12, 13 and in between 11.1, 11.2 with new Features? > > I mean we can have 11 in Feb and 12 in I don’t know August which is 6 > Months and in between we should have 11.1 and 11.2 which is not only a > bugfix for a lot of Bugs, also with new Features, but not that big. So > Maybe no NetCat for 11.1 and 11.2 or not that much time spending on that. > Maybe reducing the NetCat process or changing it? Come one, there can be a > lot more stuff to make it better and possible. I know and this is a big > Benefit, that NetBeans is real stable. I switched from Eclipse now 5 years > ago to NetBeans, because of 2 simple Plugins of Eclipse, that broke the > whole IDE. I know that we Need that Quality. So IntelliJ or the JetBrains > based IDEs are also real stable. > > So I think we can handle it. > > And no, using the development Version is not an Option, they are often not > stable and not possible to use it in production. I tried it from 7.0 – 7.2 > I end up with a nightly build with a lot of NPE after starting the DIE so I > had to go back tot the stable Version and had to wait 3 more months for the > new Fancy Features. > > Agian, I think after the donation process, it will be more easy, so we > should wait a whole year 2019 to see what happens then and should discuss > it again after the last release of 2019. We should not overreact yet. > > My 2 cents > > > Cheers > > Chris > > > > > Von: Laszlo Kishalmi > Gesendet: Dienstag, 13. November 2018 18:08 > An: [email protected] > Betreff: Re: [DISCUSS] Apache NetBeans roadmap updates > > Well, it is not that simple. > > Having major plugins to have their own release means that you shall > replicate at least some of the release infrastructure/process/people > work for it. > > On the other hand one of the greatest values of NetBeans is that it just > works out of the box. Having some plugins create their own releases > means moving to the Eclipse model as plugins might creating frictions > from release to release between each other and the IDE. I had to listen > countless discussions of my colleges which version of eclipse to use > with which version of plugins, until the Eclipse distribution creators > showed up. So I would not go that route. > > Having two releases per year with 3 month patch releases sounds fair to me. > > For those who want the new and shiny, there was always a possibility to > use the development version. > > On 11/13/18 8:03 AM, Alexander Romanenko wrote: > > Sorry if this was discussed before and I missed it. > > Are there any reasons why major plugins cannot have their own release > > schedule? From org perspective, i think (1) puts less pressure on testers > > to test all features at once, including ones they are not familiar with. > > (2) less pressure from users about not having access to plugins that are > > "complete" months ago but have to wait for arbitrary global release date. > > > > вт, 13 нояб. 2018 г. в 9:59, Neil C Smith <[email protected]>: > > > >> On Tue, 13 Nov 2018, 14:16 Emilian Bold <[email protected] wrote: > >> > >>> Two releases per year seems more manageable. > >>> > >> The point of 4 was to be more manageable though. Less changes, less > >> pressure for new features to meet deadlines (dropping 3 months less of > an > >> issue) > >> > >> I'm happy with either, but I don't think the current situation with > lots of > >> changes / things still being donated is a good model for how this might > >> work once the dust settles. > >> > >> Best wishes, > >> > >> Neil > >> > > --------------------------------------------------------------------- > 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 > > >
