Re: Apache NetBeans 11.0 has been Branched!

2019-02-13 Thread Geertjan Wielenga
Awesome! Gj On Wed, Feb 13, 2019 at 8:47 AM Laszlo Kishalmi wrote: > Dear all, > > With a little help and push on the PR-s, I've created the release110 > branch to host our Apache NetBeans 11.0 codeline. > > The first vc1 is currently building from it. I still have to check, sign > and upload

Re: Who wants to be the release manager for NetBeans 11.0?

2019-02-13 Thread Neil C Smith
Hi, Sorry for the late reply .. On Tue, 12 Feb 2019 at 07:22, Emilian Bold wrote: > I really think Neil can do it by himself. And he has 2 other previous RMs > to ask questions. No, I can't, for the reason I first said - I've got a big deadline for a client coming up related to a library I

useSystemAAFontSettings

2019-02-13 Thread Glenn Holmer
What's the reasoning behind not having this on by default in etc/netbeans.conf? Does it work well on some OS and not on others? In Linux (Debian testing/KDE Plasma), NetBeans looks just awful without it. -J-Dawt.useSystemAAFontSettings=on -- Glenn Holmer (Linux registered user #16682) "After

Apache NetBeans 11.0-vc1 Is Available for Testing!

2019-02-13 Thread Laszlo Kishalmi
Dear Community, I'd like to announce that the first build for testing form release110 branch is available for download. As this build is for testing purpose only, we are not going to do the release dance and voting around it. See the artifacts here:

Re: Apache NetBeans 11.0 has been Branched!

2019-02-13 Thread Matthias Bläsing
Hi, Am Mittwoch, den 13.02.2019, 10:44 -0800 schrieb Laszlo Kishalmi: > BTW, as we are not really going to release this build and that would be > true for the next one. > Shall we play the release dance and upload everything to the staging > area and create vote threads? we can skip this. We

Re: Apache NetBeans 11.0 has been Branched!

2019-02-13 Thread Laszlo Kishalmi
Well, I know Gj preference, though I agree with Neil. Let's leave that change for the next release, if we would graduate by that time the vc would be meaningless anyway. On 2/13/19 10:58 AM, Geertjan Wielenga wrote: Well, I’d vote for keeping the -vc tags, even for pre-voting builds, for

Re: Apache NetBeans 11.0 has been Branched!

2019-02-13 Thread Laszlo Kishalmi
BTW, as we are not really going to release this build and that would be true for the next one. Shall we play the release dance and upload everything to the staging area and create vote threads? I think probably not. Is the Jenkins build link would be just fine to share? (I'd do the Git

Re: Apache NetBeans 11.0 has been Branched!

2019-02-13 Thread Geertjan Wielenga
Well, even when we graduate we’ll be voting, as PMC, except that there’ll be no IPMC vote. Gj On Wednesday, February 13, 2019, Laszlo Kishalmi wrote: > Well, I know Gj preference, though I agree with Neil. > > Let's leave that change for the next release, if we would graduate by that > time

Re: Apache NetBeans 11.0 has been Branched!

2019-02-13 Thread Geertjan Wielenga
Yes, to me, makes sense. Let’s not dance needlessly. Gj On Wednesday, February 13, 2019, Laszlo Kishalmi wrote: > BTW, as we are not really going to release this build and that would be > true for the next one. > Shall we play the release dance and upload everything to the staging area > and

Re: Apache NetBeans 11.0 has been Branched!

2019-02-13 Thread Geertjan Wielenga
Well, I’d vote for keeping the -vc tags, even for pre-voting builds, for simplicity. Gj On Wednesday, February 13, 2019, Neil C Smith wrote: > On Wed, 13 Feb 2019 at 18:44, Laszlo Kishalmi > wrote: > > Shall we play the release dance and upload everything to the staging > > area and create

Re: Apache NetBeans 11.0 has been Branched!

2019-02-13 Thread Neil C Smith
On Wed, 13 Feb 2019 at 18:44, Laszlo Kishalmi wrote: > Shall we play the release dance and upload everything to the staging > area and create vote threads? .. > (I'd do the Git tagging though.) Sounds good! Maybe call them beta-1, beta-2, or -rc1, -rc2, etc. though? Be good to keep -vc for

Re: useSystemAAFontSettings

2019-02-13 Thread Laszlo Kishalmi
Probably we can do that. A few response from Windows and Mac users trying out that setting won't hurt. As far as I remember the defaults for Win and Linux were different, and if you set it just on then it would hurt windows font rendering. I would also recommend to use OpenJDK 12 build 30+

RE: Use Graal.js parser for NetBeans 11 was: Where is `Oracle JS Parser Implementation` built from?

2019-02-13 Thread Eduardo Quintanilla
Should the plugin be installed by default(Before opening a Java EE project) as nb-javac plugin? In my tests if the plugin is not installed before opening a Java EE project(Maven) then Netbeans stops responding. Eduardo Quintanilla Software Developer Block Networks  -Original

Re: Apache NetBeans 11.0 has been Branched!

2019-02-13 Thread Geertjan Wielenga
We appear to now have our first candidate, applicable for NetCAT and any other testing we want to do, on a common basis: https://builds.apache.org/job/incubator-netbeans-release/384/artifact/dist/ In particular, use this one from the link above, the binary of NetBeans IDE 11.0 vc1: