Re: [DISCUSS] Becoming a top level Apache project

As stated, I am now going to open a VOTE thread, since we have had some discussion now on this topic, in this thread, as well as in various others, and everyone has had a chance to comment on our becoming a top level project and there appears to be consensus around this. However, a VOTE thread is

Re: [DISCUSS] Becoming a top level Apache project

On Fri, 8 Mar 2019, 11:23 Geertjan Wielenga, wrote: > Hope I got it right, Neil. If so, I like it! > Pretty much, yes. As one of those involved in the thread that brought up the idea of time-based quarterly releases I do feel a tiny twinge of guilt when we use it as a stick to beat ourselves

Re: [DISCUSS] Becoming a top level Apache project

Hi, Slowly catching up on emails having been busy with some consultancy work the last month ... this still bothers me and feels like a fudge that needs addressing ... On Thu, 7 Mar 2019 at 16:27, Laszlo Kishalmi wrote: > I'm not sure, that I'm answering your question, though besides major >

Re: [DISCUSS] Becoming a top level Apache project

Thanks Laszlo, OK, numbering approach is “normal” for major releases and are not every release (at least as planned going forward.) That should provide more stability although I understand with the present migration of both NetBeans and the Java parts — changes are going to be the rule for a

Re: [DISCUSS] Becoming a top level Apache project

Dear Dave, I'm not sure, that I'm answering your question, though besides major versions we are planning to have a major version every 6 months with an optional minor release 3 months away from the major one. Previously we tried to make a release in every 3 months, though we think that's

Re: [DISCUSS] Becoming a top level Apache project

Also on QU40 **YES**.   Each release contains a “What’s new” on the website containing the release notes (extracted for JIRA), for example, [here for Apache NetBeans 10](). The project aims to make no backward incompatible changes

Re: [DISCUSS] Becoming a top level Apache project

+1 good releases, good community, good leadership - and some very ok-ish understanding about how ASF projects are done. Go for it! LieGrue,strub On Thursday, 7 March 2019, 14:32:28 CET, Bertrand Delacretaz wrote: Hi, On Thu, Mar 7, 2019 at 11:59 AM Geertjan Wielenga wrote: >

Re: [DISCUSS] Becoming a top level Apache project

Hi, On Thu, Mar 7, 2019 at 11:59 AM Geertjan Wielenga wrote: > ...Maturity assessment is here: > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Maturity+Model+Assessment+for+NetBeans .. Thanks - as an incubation mentor I think this project is ready to graduate, and is a great

Re: [DISCUSS] Becoming a top level Apache project

For the current release, here: https://netbeans.apache.org/download/nb100/index.html For each release there is such a page listing features. Gj On Thu, Mar 7, 2019 at 12:37 PM Mr_Krava wrote: > Just looking at QU40.Where is the "Whats new" requirement we have said is > in each release? > >

Re: [DISCUSS] Becoming a top level Apache project

Just looking at QU40.Where is the "Whats new" requirement we have said is in each release? CheersBrian CUNKA On Thursday, 7 March 2019, 9:59:18 pm AEDT, Geertjan Wielenga wrote: Hi all, We've discussed this in various ways before, but let's try to hammer down what needs to be done

Re: [DISCUSS] Becoming a top level Apache project

Also sending this to d...@netbeans.apache.org, in case dev@netbeans.incubator.apache.org, just in case. Gj On Thu, Mar 7, 2019 at 11:52 AM Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > Hi all, > > We've discussed this in various ways before, but let's try to hammer down > what