Proposed plan for final release of 9.0

[Geertjan Wielenga <ge...@googlemail.com>]

Hi all,

Right now in the current state of Apache NetBeans, our releases are
'blocker based' rather than 'time based', i.e., when blockers are fixed,
we'll release.

The primary purpose of releases for the moment continues to be to integrate
into the Apache way of doing things, rather than focusing strongly on new
features and so on.

Here's what needs to be done from that perspective:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Final+Release

I.e., the idea is to fix the blockers that remain, to put a vote candidate
together from the release90 branch -- for purposes of doing the community
acceptance survey, PPMC vote and IPMC vote -- and when that vote passes to
release that candidate as Apache NetBeans (incubating) 9.0.

I.e., this means the idea is to not create an rc2 release, but instead to
focus on the next release that we do to be the final release of 9.0.

Since this is 'blocker based', the release can be put together as and when
the blockers are fixed, which could be a week from now or a month from now,
depending on how quickly we get it done.

Ideas, responses, feedback welcome.

Thanks,

Gj

Re: Proposed plan for final release of 9.0

[Emilian Bold <em...@protonmail.ch>]

What's in a name, right?

Let's just call any bits 9.0 and see later if we go to 9.1 or NetBeans 2018.10 or NetBeans 2019 or whatever.

One thing is that NetBeans 9 will be Java SE only, but I don't expect we can wait until we IP review the 2nd donation too...

We could at least have NetCAT summarily look into using the NetBeans 8.2 modules on top of 9.0 in case users need Java EE or else whatever we are missing?

--emi

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On 5 June 2018 3:36 PM, Geertjan Wielenga <ge...@googlemail.com> wrote:

> Hi all,
> 
> Right now in the current state of Apache NetBeans, our releases are
> 
> 'blocker based' rather than 'time based', i.e., when blockers are fixed,
> 
> we'll release.
> 
> The primary purpose of releases for the moment continues to be to integrate
> 
> into the Apache way of doing things, rather than focusing strongly on new
> 
> features and so on.
> 
> Here's what needs to be done from that perspective:
> 
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Final+Release
> 
> I.e., the idea is to fix the blockers that remain, to put a vote candidate
> 
> together from the release90 branch -- for purposes of doing the community
> 
> acceptance survey, PPMC vote and IPMC vote -- and when that vote passes to
> 
> release that candidate as Apache NetBeans (incubating) 9.0.
> 
> I.e., this means the idea is to not create an rc2 release, but instead to
> 
> focus on the next release that we do to be the final release of 9.0.
> 
> Since this is 'blocker based', the release can be put together as and when
> 
> the blockers are fixed, which could be a week from now or a month from now,
> 
> depending on how quickly we get it done.
> 
> Ideas, responses, feedback welcome.
> 
> Thanks,
> 
> Gj



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Proposed plan for final release of 9.0

[Jaroslav Tulach <ja...@gmail.com>]

> I.e., this means the idea is to not create an rc2 release, but instead to
> focus on the next release that we do to be the final release of 9.0.
>
>
This is a bit up-side-down, but given the way the system works, it is
probably correct. One does all the work and prepares the final bits and
uploads them to staging repository. The vote begins:
- when approved - the bits are made to public download area and the release
is announced.
- when rejected - the bits are removed and one tries again

As such +1 to fix the stoppers and prepare bits for 9.0 vote candidate.
-jt