On 10/7/18 12:22 AM, Neil C Smith wrote:
Hi,
On Sat, 6 Oct 2018, 21:16 Antonio Vieiro, wrote:
For 9.0 we could use a branch named "9.0-vc3" (same as the tag in
incubator-netbeans).
I'm not sure I understand the reasoning for branching like that? Surely we
could just as easily tag master
I have been working on the "NB Modules" Profiler test spec. I also signed up
for the "Web Project" test spec. However, since Java EE and Java Web
Applications are not yet supported with NetBeans 10, does it make sense for me
to go through this specification? If we do add this test, then we'd
Hi there,
Right now NetBeans calculates it's default heap size on 20% of the
system memory, but cap it on 1Gb.
Is it usually enough? Most of my machines have 16Gb ram and one of the
first things I do is to set the heap limit to 2Gb or more. I thing the
20 % is good, but we might move the cap
Hi,
On Sat, 6 Oct 2018, 21:16 Antonio Vieiro, wrote:
> For 9.0 we could use a branch named "9.0-vc3" (same as the tag in
> incubator-netbeans).
I'm not sure I understand the reasoning for branching like that? Surely we
could just as easily tag master? What's your thoughts behind it? It might
m
I was thinking we could merge to another branch instead of to master.
For 9.0 we could use a branch named "9.0-vc3" (same as the tag in
incubator-netbeans). In fact we could update the jenkins release job
to push the javadoc to this new repo as well. And so on with the rest
of releases.
We then c
> On **GitHub**, Antonio wrote:
> Do we want to merge this into master? Or asf-site instead? How is web
> publishing set up? Can we discuss in the mailing list?
OK, bringing that discussion onto the mailing list (although I do need
to fix where the GitHub notifications are going, so may be here
