I believe, an IDE release is not same as language support release. NetBeans
(or any other) IDE, as far as I am concerned is “just an editor” and a
framework for other language plugins. Then, say, PHP and even Java rides on
top of that. Mixing these two concepts together creates too much conflict.
On 2018/08/07 08:46:06, Geertjan Wielenga
wrote:
> Hi all,>
>
> We've discussed this informally, i.e., the topic of the release>
> cycle/cadence, a few times over the past months.>
>
> Let's nail it down as far as possible so that we can give clarity to our>
> users about our intentions and also
An IDE release is not same as language support release. NetBeans (or any other)
IDE, as far as I am concerned is “just an editor” and a framework for other
language plugins. Then, say, PHP and even Java rides on top of that. Mixing
these two concepts together creates too much conflict.
Then,
An IDE release is not same as language support release. NetBeans (or any
other) IDE, as far as I am concerned is “just an editor” and a framework
for other language plugins. Then, say, PHP and even Java rides on top of
that. Mixing these two concepts together creates too much conflict.
Then,
On Wednesday, August 8, 2018, William Beebe wrote:
> Release Cycle -
> A 90 day release cadence is probably too much for a volunteer
> group, so perhaps every six months.
So far, those who have been working on Apache NetBeans are converging
around a quarterly release cycle.
Gj
>
> Version
Release Cycle -
A reasonable release cadence is a Good Thing. To keep the in-between
release period short and sweet, it would be helpful to release only a new
new features to actually meet the release date. Same with bug fixes. In
fact, bug fixes should always be released even if there are no new
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
Hey everyone,
I’ve used Netbeans for PHP development since 2002. As you might assume, the JDK
release cycle is mostly irrelevant to me as a user, as it is not a dependency
for any of my work.
That said, I do think it is rather convenient to download and install the
entire package as it is
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
Badly worded by me, module update issue is where the update center will be
located
On Tue, 7 Aug 2018 15:54 Oliver Rettig, 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
> 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
On Tue, Aug 7, 2018 at 7:40 AM, Peter Steele wrote:
> 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
>
>
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
Just saying that with early releases of JDK12 now shipping I don't see the
point of a NB10. The versions of NB9 I'm using already have JDK11 features
being included.
Further, NB is Java. While it may provide functions to other languages, so
far it IS Java. So Java implementation level still
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
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 wrote:
> To me it makes sense to have NB reflect the level of Java implemented. For
> example, features of JDK 11 can be added
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, etc.
(schedule is irrelevant to me -- every 3 months is fine) but when the full
function of JDK 11 is included then NB 11 should be released. I
On Tue, 7 Aug 2018 at 09:46, Geertjan Wielenga
wrote:
> However, a separate discussion is about release numbers. Our current
> release is 9.0. How do we decide to number the other releases? A simple
> proposal might be to have our major release in August of each year and then
> all then make all
18 matches
Mail list logo
