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, there is a sour feeling when hear how next version of language plugin is already done, yet it’s not allowed to use until some arbitrary release party. I have 1.3 million views Zend Framework (PHP) tutorials and I regularly get asked to show how to setup NetBeans instead of proprietary one I currently use they cannot afford. Unfortunately, that is a non-starter as the lessons showing what Zend Framework is capable of in *current, yet already half-a-year-old* version is not possible in editor that has even older version. I am not going to teach outdated content just to promote NetBeans on the screen, even though that would be excellent motivation for me to show it off. Some replies here have idea about psychological comfort of frequent releases. As a language user, I do not notice much underlying platform releases. Again, this feeling may come from the conflict in my first point. More releases mean that NetBeans has a better chance to keep up with *ALL* languages by maximizing probability that do not have to wait long for next version of, say, EcmaScript. However, do language plugin users really care about the underlying *IDE framework* release version? Sure, there may come a time when NetBeans 14 might have some fancy editor feature so have to wait until “PHP plugin version 21” or even “Java plugin version 7” catches up to IDE release, but that is a VERY tolerable wait that does not actively prohibit usage. Then the editor framework can take however many years to have releases.
On 2018/08/07 08:46:06, Geertjan Wielenga <geertjan.wiele...@googlemail.com.INVALID> 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 to enable us to organize features > coming in through donations and otherwise into releases. > > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+Cycle > > Right now, we have a clear suggestion around in which month of the year we > will release. I.e., the Apache NetBeans (incubating) 9.0 release was our > August release (and we even managed to release it a few days early, in > July, hurray!). So, this year, we will have another release in November, > that's our next big target, if we agree with the above proposal. > > 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 the other releases minor. However, that's just a thought, > another one could be that we should simply consider how large the features > are that we have added and base major/minor on that. Or we could try to > follow the JDK release numbering more or less. > > Anyway, thoughts welcome, > > Gj > --------------------------------------------------------------------- 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
