I believe that people do like more frequent releases. Once per quarter, let's say, seems to be a good fit. I do not believe that NetBeans release number should be bound to the supported Java release because Apache NetBeans 9.0 was just released with JDK 10 support...so that would be a cause for confusion.
I think that the major release number should change once per year, say in August. If we were to have a quarterly release, then Apache NetBeans 9.1 would be next release that would occur near the end of this calendar year, followed by 9.2 and 9.3 in the subsequent quarters. That would mean that Apache NetBeans 10 would be released next August. I personally think it may become too convoluted to try and rate major releases vs minor releases in an effort to increment the release number. Of course, using this logic it is possible to have Apache NetBeans 9.0.1, Apache NetBeans 9.1.1, etc, if a critical update needed to be released for some reason. Thanks for reading, I appreciate your time. On Tue, Aug 7, 2018 at 10:34 AM Oliver Rettig <[email protected]> wrote: > Thanks Peter for clarification. > > Isnt it possible to have an apache update center, which includes only > apache-netbeans-ide > updates? Or is this incompatible with the apache release procedure? > > > Badly worded by me, module update issue is where the update center will > be > > located > > > > On Tue, 7 Aug 2018 15:54 Oliver Rettig, <[email protected]> wrote: > > > > Phycologically people feel they have a more modern system if it > updates > > > > more frequently. There should be no reason why minor items can't be > > > > released quickly in a more agile way. I suspect though we need to > move > > > > > > out > > > > > > > of incubator status for that because there are a lot of rounds of > > > > > > approval > > > > > > > before code gets released. > > > > You could have large core releases once or twice a year and many > minor > > > > updates imbetween. > > > > > > +1 > > > > > > > This is a personal thing but I would like to get the updates without > > > > downloading a new version of the ide every time. Letting the ide auto > > > > update would be nice. I guess that could only happen when the module > > > > > > update > > > > > > > issue is resolved > > > > > > Please point me to that module update issue? > > > > > > > On Tue, 7 Aug 2018 15:24 Geertjan Wielenga, > > > > > > > > <[email protected]> wrote: > > > > > Also, Apache NetBeans is more than Java-focused, and the question > is > > > > > > also > > > > > > > > whether such prominence for Java should be given to the extent that > > > > > the > > > > > JDK > > > > > releases should be followed at all, i.e., whether this should be an > > > > > > aim of > > > > > > > > the project. It's certainly open to discussion but definitely not a > > > > > > given. > > > > > > > > Gj > > > > > > > > > > On Tue, Aug 7, 2018 at 4:22 PM, Geertjan Wielenga < > > > > > > > > > > [email protected]> wrote: > > > > > > Just as a quick FYI: Both JDK 9 and JDK 10 are supported in > Apache > > > > > > NetBeans 9, i.e., no, we've not skipped JDK 10. > > > > > > > > > > > > Gj > > > > > > > > > > > > On Tue, Aug 7, 2018 at 4:11 PM, Chuck Davis <[email protected]> > > > > > > wrote: > > > > > >> To me it makes sense to have NB reflect the level of Java > > > > > > implemented. > > > > > > > > >> For > > > > > >> example, features of JDK 11 can be added incrementally to NB > 9.1, > > > > > > 9.2, > > > -- Josh Juneau [email protected] http://jj-blogger.blogspot.com https://www.apress.com/index.php/author/author/view/id/1866
