You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Geertjan Wielenga <ge...@apache.org> on 2020/03/10 12:22:45 UTC
Apache NetBeans 12.0 -- Eric Barboni
Hi all,
Especially Eric, who volunteered to be volunteer release manager for 12.0.
Here are our dates for the 12.0 release and NetCAT 12.0:
https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
https://cwiki.apache.org/confluence/display/NETBEANS/NetCAT+12.0+Schedule
Where March 15th is listed as feature freeze.
Just making sure we're all on the same page about the above.
Thanks,
Gj
Re: Apache NetBeans 12.0 -- Eric Barboni
Posted by Sven Reimers <sv...@gmail.com>.
Hi,
awesome Eric is doing the release again,
Im currently trying to get Groovy 3.0.x support into NetBeans 12, but there
are still some rough edges... not sure if I will make it. Backup plan is to
update to last 2.5.x to ensure compatibilty with newer Java versions as a
runtime for the IDE..
-Sven
Josh Juneau <ju...@gmail.com> schrieb am Mi., 11. März 2020, 13:52:
> Thanks to Eric for managing the release, and everyone else for all of the
> work being done.
>
> I am going to be putting in a PR for Jakarta EE 8 support within the next
> couple of days....would like to get that in to 12.0. It is working in my
> environment, just need to clean it up a bit.
>
> Best Regards
>
> Josh Juneau
> juneau001@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/us/search?query=Juneau
> <https://www.apress.com/index.php/author/author/view/id/1866>
>
>
>
> On Wed, Mar 11, 2020 at 7:27 AM Eric Barboni <sk...@apache.org> wrote:
>
> > I'm physically training a lot :D Will be fit on 12.0 release :p
> >
> > Feature freeze is a bit abstract to me. After merge close, all of us
> > should be careful of PR that will go for 12.1 or 12.0 LTS.
> >
> > In some way I feel that RM on early phase can be more group work (it was
> a
> > bit like that in 11.3) :
> > making a branch, setting up json and pushing build button on Jenkins
> > for beta creation can be done by any PMC. (No signing, no vote ..)
> > and making changes remerging for beta milestone is quite easy too,
> with
> > help of PR. That lower the workload.
> >
> > The remaining works is locked to RM but it's a matter of hours for each
> > round of candidate.
> > The hard stuff is VC preparation with signing that is done by RM and
> > co RM (for installers) on their own computer.
> >
> > --
> > What I'm start thinking is instead of a xx.u-update1 it will be quite
> easy
> > to go for xx. instead of complex construct (if 11.3 need patch then go to
> > 11.31) full updating web + mirror with the 11.31.
> >
> > This is informal :D
> >
> > Best Regard
> > Eric
> >
> > -----Message d'origine-----
> > De : Neil C Smith <ne...@apache.org>
> > Envoyé : mercredi 11 mars 2020 11:08
> > À : dev <de...@netbeans.apache.org>
> > Objet : Re: Apache NetBeans 12.0 -- Eric Barboni
> >
> > On Tue, 10 Mar 2020 at 12:22, Geertjan Wielenga <ge...@apache.org>
> > wrote:
> > > Especially Eric, who volunteered to be volunteer release manager for
> > 12.0.
> >
> > I'm glad Eric is doing 12.0 - I think having someone who has already been
> > an RM is a good thing to keep in mind for future LTS.
> >
> > I'm also happy to pick up any tasks here if need be, and it might also be
> > good if the person considering doing 12.1 touched base now too? Am aware
> > that this release process will be twice as long, and have NetCAT, as well
> > as potentially more likelihood of updates through the year - all
> > potentially increasing the RM workload. Eric, any thoughts there?
> >
> > On updates, part of me feels we might want to find "something" that needs
> > updating in 11.3 and test changes in pushing updates across larger user
> > base?
> >
> > On Tue, 10 Mar 2020 at 13:12, Geertjan Wielenga <ge...@apache.org>
> > wrote:
> > > — Make nb-javac less prominently required and explicitly state that
> > > ideally a JDK later than 8 should be used.
> >
> > Possibly an option to switch off the notification (similarly to the old
> > userdir one) would be good? 12.0 may not be the time to be too radical
> in
> > changing that process, but being able to stop it nagging and more info in
> > the download dialog would be good.
> >
> > > — Several small but annoying bugs in the FlatLaf support (see recent
> > > e-mail here by Jaroslav Tulach).
> >
> > Well, on the FlatLaF / HTML wizards front, I'd much rather see us drop
> the
> > HTML wizard entirely!
> >
> > Assuming we don't, we really need to battle test the ergonomics
> enablement
> > and JavaFX download there. It too often results in an infinite
> enablement
> > loop and blank wizard.
> >
> > > — JDK 15 enhancements being worked on by Oracle developers, e.g., new
> > > sealed type etc.
> >
> > Do those really need priority in 12.0 vs 12.1? Freeze is in a week!
> >
> > More importantly would be ensuring JDK 14 support, including nb-javac
> when
> > installed?
> >
> > Best wishes,
> >
> > Neil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
Re: Apache NetBeans 12.0 -- Eric Barboni
Posted by Josh Juneau <ju...@gmail.com>.
Thanks to Eric for managing the release, and everyone else for all of the
work being done.
I am going to be putting in a PR for Jakarta EE 8 support within the next
couple of days....would like to get that in to 12.0. It is working in my
environment, just need to clean it up a bit.
Best Regards
Josh Juneau
juneau001@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau
<https://www.apress.com/index.php/author/author/view/id/1866>
On Wed, Mar 11, 2020 at 7:27 AM Eric Barboni <sk...@apache.org> wrote:
> I'm physically training a lot :D Will be fit on 12.0 release :p
>
> Feature freeze is a bit abstract to me. After merge close, all of us
> should be careful of PR that will go for 12.1 or 12.0 LTS.
>
> In some way I feel that RM on early phase can be more group work (it was a
> bit like that in 11.3) :
> making a branch, setting up json and pushing build button on Jenkins
> for beta creation can be done by any PMC. (No signing, no vote ..)
> and making changes remerging for beta milestone is quite easy too, with
> help of PR. That lower the workload.
>
> The remaining works is locked to RM but it's a matter of hours for each
> round of candidate.
> The hard stuff is VC preparation with signing that is done by RM and
> co RM (for installers) on their own computer.
>
> --
> What I'm start thinking is instead of a xx.u-update1 it will be quite easy
> to go for xx. instead of complex construct (if 11.3 need patch then go to
> 11.31) full updating web + mirror with the 11.31.
>
> This is informal :D
>
> Best Regard
> Eric
>
> -----Message d'origine-----
> De : Neil C Smith <ne...@apache.org>
> Envoyé : mercredi 11 mars 2020 11:08
> À : dev <de...@netbeans.apache.org>
> Objet : Re: Apache NetBeans 12.0 -- Eric Barboni
>
> On Tue, 10 Mar 2020 at 12:22, Geertjan Wielenga <ge...@apache.org>
> wrote:
> > Especially Eric, who volunteered to be volunteer release manager for
> 12.0.
>
> I'm glad Eric is doing 12.0 - I think having someone who has already been
> an RM is a good thing to keep in mind for future LTS.
>
> I'm also happy to pick up any tasks here if need be, and it might also be
> good if the person considering doing 12.1 touched base now too? Am aware
> that this release process will be twice as long, and have NetCAT, as well
> as potentially more likelihood of updates through the year - all
> potentially increasing the RM workload. Eric, any thoughts there?
>
> On updates, part of me feels we might want to find "something" that needs
> updating in 11.3 and test changes in pushing updates across larger user
> base?
>
> On Tue, 10 Mar 2020 at 13:12, Geertjan Wielenga <ge...@apache.org>
> wrote:
> > — Make nb-javac less prominently required and explicitly state that
> > ideally a JDK later than 8 should be used.
>
> Possibly an option to switch off the notification (similarly to the old
> userdir one) would be good? 12.0 may not be the time to be too radical in
> changing that process, but being able to stop it nagging and more info in
> the download dialog would be good.
>
> > — Several small but annoying bugs in the FlatLaf support (see recent
> > e-mail here by Jaroslav Tulach).
>
> Well, on the FlatLaF / HTML wizards front, I'd much rather see us drop the
> HTML wizard entirely!
>
> Assuming we don't, we really need to battle test the ergonomics enablement
> and JavaFX download there. It too often results in an infinite enablement
> loop and blank wizard.
>
> > — JDK 15 enhancements being worked on by Oracle developers, e.g., new
> > sealed type etc.
>
> Do those really need priority in 12.0 vs 12.1? Freeze is in a week!
>
> More importantly would be ensuring JDK 14 support, including nb-javac when
> installed?
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Apache NetBeans 12.0 -- Eric Barboni
Posted by Neil C Smith <ne...@apache.org>.
On Wed, 11 Mar 2020 at 12:27, Eric Barboni <sk...@apache.org> wrote:
> I'm physically training a lot :D Will be fit on 12.0 release :p
I look forward to the training montage video :-)
> Feature freeze is a bit abstract to me. After merge close, all of us should be careful of PR that will go for 12.1 or 12.0 LTS.
Well, at least everything that goes in 12.0 should have your review
and you have final call on it if need be - it's mainly your workload
that stands to increase! In my opinion, we also need to be careful
of pulling in anything that changes too much of what is being covered
by NetCAT - being involved with NetCAT for 9 made me wary of providing
too much of a moving target for that process.
> In some way I feel that RM on early phase can be more group work (it was a bit like that in 11.3) :
> making a branch, setting up json and pushing build button on Jenkins for beta creation can be done by any PMC. (No signing, no vote ..)
> and making changes remerging for beta milestone is quite easy too, with help of PR. That lower the workload.
Agreed, and a good thing for more people to know how that all works,
particularly whoever wants to do 12.1, and if there's a week you can't
do it - shout up (assuming weekly betas are right still?) ...
> The remaining works is locked to RM but it's a matter of hours for each round of candidate.
> The hard stuff is VC preparation with signing that is done by RM and co RM (for installers) on their own computer.
... yes, that's kind of a one person thing, although the hardest thing
might just be waiting for svn! ;-)
I was actually thinking there's a bunch of stuff here around JIRA
issue management, related PR triaging/reviewing, etc. that might need
opening up more - I wonder how much NetCAT will increase the work
there. And just generally working out how that fits in / gets
managed.
> What I'm start thinking is instead of a xx.u-update1 it will be quite easy to go for xx. instead of complex construct (if 11.3 need patch then go to 11.31) full updating web + mirror with the 11.31.
Not sure the point you're making here? I went with 11.2-u1 mainly not
to have 11.21 before 11.3. But the choice of version number seems a
minimal concern. You thinking of whole release for update? NB
11.2-u1 was just vote on full sources, plus putting the required
update NBMs on the mirrors. Don't see how it could be less complex.
> This is informal :D
:-)
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Apache NetBeans 12.0 -- Eric Barboni
Posted by Eric Barboni <sk...@apache.org>.
I'm physically training a lot :D Will be fit on 12.0 release :p
Feature freeze is a bit abstract to me. After merge close, all of us should be careful of PR that will go for 12.1 or 12.0 LTS.
In some way I feel that RM on early phase can be more group work (it was a bit like that in 11.3) :
making a branch, setting up json and pushing build button on Jenkins for beta creation can be done by any PMC. (No signing, no vote ..)
and making changes remerging for beta milestone is quite easy too, with help of PR. That lower the workload.
The remaining works is locked to RM but it's a matter of hours for each round of candidate.
The hard stuff is VC preparation with signing that is done by RM and co RM (for installers) on their own computer.
--
What I'm start thinking is instead of a xx.u-update1 it will be quite easy to go for xx. instead of complex construct (if 11.3 need patch then go to 11.31) full updating web + mirror with the 11.31.
This is informal :D
Best Regard
Eric
-----Message d'origine-----
De : Neil C Smith <ne...@apache.org>
Envoyé : mercredi 11 mars 2020 11:08
À : dev <de...@netbeans.apache.org>
Objet : Re: Apache NetBeans 12.0 -- Eric Barboni
On Tue, 10 Mar 2020 at 12:22, Geertjan Wielenga <ge...@apache.org> wrote:
> Especially Eric, who volunteered to be volunteer release manager for 12.0.
I'm glad Eric is doing 12.0 - I think having someone who has already been an RM is a good thing to keep in mind for future LTS.
I'm also happy to pick up any tasks here if need be, and it might also be good if the person considering doing 12.1 touched base now too? Am aware that this release process will be twice as long, and have NetCAT, as well as potentially more likelihood of updates through the year - all potentially increasing the RM workload. Eric, any thoughts there?
On updates, part of me feels we might want to find "something" that needs updating in 11.3 and test changes in pushing updates across larger user base?
On Tue, 10 Mar 2020 at 13:12, Geertjan Wielenga <ge...@apache.org> wrote:
> — Make nb-javac less prominently required and explicitly state that
> ideally a JDK later than 8 should be used.
Possibly an option to switch off the notification (similarly to the old userdir one) would be good? 12.0 may not be the time to be too radical in changing that process, but being able to stop it nagging and more info in the download dialog would be good.
> — Several small but annoying bugs in the FlatLaf support (see recent
> e-mail here by Jaroslav Tulach).
Well, on the FlatLaF / HTML wizards front, I'd much rather see us drop the HTML wizard entirely!
Assuming we don't, we really need to battle test the ergonomics enablement and JavaFX download there. It too often results in an infinite enablement loop and blank wizard.
> — JDK 15 enhancements being worked on by Oracle developers, e.g., new
> sealed type etc.
Do those really need priority in 12.0 vs 12.1? Freeze is in a week!
More importantly would be ensuring JDK 14 support, including nb-javac when installed?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Apache NetBeans 12.0 -- Eric Barboni
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 10 Mar 2020 at 12:22, Geertjan Wielenga <ge...@apache.org> wrote:
> Especially Eric, who volunteered to be volunteer release manager for 12.0.
I'm glad Eric is doing 12.0 - I think having someone who has already
been an RM is a good thing to keep in mind for future LTS.
I'm also happy to pick up any tasks here if need be, and it might also
be good if the person considering doing 12.1 touched base now too? Am
aware that this release process will be twice as long, and have
NetCAT, as well as potentially more likelihood of updates through the
year - all potentially increasing the RM workload. Eric, any thoughts
there?
On updates, part of me feels we might want to find "something" that
needs updating in 11.3 and test changes in pushing updates across
larger user base?
On Tue, 10 Mar 2020 at 13:12, Geertjan Wielenga <ge...@apache.org> wrote:
> — Make nb-javac less prominently required and explicitly state that ideally
> a JDK later than 8 should be used.
Possibly an option to switch off the notification (similarly to the
old userdir one) would be good? 12.0 may not be the time to be too
radical in changing that process, but being able to stop it nagging
and more info in the download dialog would be good.
> — Several small but annoying bugs in the FlatLaf support (see recent e-mail
> here by Jaroslav Tulach).
Well, on the FlatLaF / HTML wizards front, I'd much rather see us drop
the HTML wizard entirely!
Assuming we don't, we really need to battle test the ergonomics
enablement and JavaFX download there. It too often results in an
infinite enablement loop and blank wizard.
> — JDK 15 enhancements being worked on by Oracle developers, e.g., new
> sealed type etc.
Do those really need priority in 12.0 vs 12.1? Freeze is in a week!
More importantly would be ensuring JDK 14 support, including nb-javac
when installed?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Apache NetBeans 12.0 -- Eric Barboni
Posted by Geertjan Wielenga <ge...@apache.org>.
Some items we need to resolve for 12.0:
— Make nb-javac less prominently required and explicitly state that ideally
a JDK later than 8 should be used. (Not dropping anything here, just
strongly recommending.)
— JavaFX Gluon project nbactions support via an extension to the wizard
API. (Assigned to Jaroslav Tulach.)
— Several small but annoying bugs in the FlatLaf support (see recent e-mail
here by Jaroslav Tulach).
— JDK 15 enhancements being worked on by Oracle developers, e.g., new
sealed type etc.
Gj
On Tue, 10 Mar 2020 at 13:22, Geertjan Wielenga <ge...@apache.org> wrote:
> Hi all,
>
> Especially Eric, who volunteered to be volunteer release manager for 12.0.
>
> Here are our dates for the 12.0 release and NetCAT 12.0:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
>
> https://cwiki.apache.org/confluence/display/NETBEANS/NetCAT+12.0+Schedule
>
> Where March 15th is listed as feature freeze.
>
> Just making sure we're all on the same page about the above.
>
> Thanks,
>
> Gj
>