subject:"\[External\] \: RE\: \[DISCUSSION\] Gradle Patch Release for NetBeans 16"

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-23 Thread Laszlo Kishalmi

These changes will be in the January release of VSCode plugin, according 
to Martin.


Your assumption on the artifacts is correct.

On 12/23/22 10:59, Neil C Smith wrote:

On Fri, 23 Dec 2022 at 06:35, Laszlo Kishalmi  wrote:

I have not bumped the versions since the last build of 16u1, so if you
installed that, you have to remove the update (or just start with an new
userdir for the test.

This build
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/16/
has been done with the netbeansrelease.json updated.

I hope some of the RM team can also  take a look on it. So the voting
phase can start soon.

Looks sane at a glance, but not at a machine I can check anything
properly for a while.  Martin?  Eric?

I assume voting artefacts will be source, updated nbms and a
pre-trimmed catalog.xml?  Or is anything else required for VSCode?

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-23 Thread Neil C Smith

On Fri, 23 Dec 2022 at 06:35, Laszlo Kishalmi  wrote:
> I have not bumped the versions since the last build of 16u1, so if you
> installed that, you have to remove the update (or just start with an new
> userdir for the test.
>
> This build
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/16/
> has been done with the netbeansrelease.json updated.
>
> I hope some of the RM team can also  take a look on it. So the voting
> phase can start soon.

Looks sane at a glance, but not at a machine I can check anything
properly for a while.  Martin?  Eric?

I assume voting artefacts will be source, updated nbms and a
pre-trimmed catalog.xml?  Or is anything else required for VSCode?

Best wishes,

Neil

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

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-22 Thread Laszlo Kishalmi

Well, that's in.

I've made a new build The update center as Neil proposed could be:

https://nightlies.apache.org/netbeans/candidate/netbeans/nbms/updates.xml.gz

I have not bumped the versions since the last build of 16u1, so if you
installed that, you have to remove the update (or just start with an new
userdir for the test.

This build
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/16/
has been done with the netbeansrelease.json updated.

I hope some of the RM team can also take a look on it. So the voting
phase can start soon.

On 12/19/22 02:11, Martin Balín wrote:

This issue will definitely be the one to include it in 16u1.
Martin

On 18. 12. 2022, at 21:03, Svata Dedic wrote:

Hi,

late Friday, a colleague discovered a bug in NbProjectInfoBuilder - mishandled
compiler options (compilerArgs / allCompilerArgs / freeCompilerArgs) that fails
to load the project when NB runs on JDK19. I can provide a fix tomorrow.

-S.

On 18. 12. 22 18:28, Neil C Smith wrote:

On Sun, 18 Dec 2022 at 16:58, Laszlo Kishalmi wrote:

I'm ready to update the netbeansrelease.json. In the 12.0-u1 and 12.0-u2
it was just another entry with git hash, version and position. Would it
be the same this time, or shall I use the vote entry as well. As far as
I remember vote would remove the version suffix from the final artifacts
and other places, that might be not required for 16-uc1.

Yes, try as before and leave out vote. That does very little now, but
I think will still stop the version suffix being added. Eric even
better to answer that! Quite a lot has changed since we did 12.0
updates, but all should hopefully work OK.
Try to update netbeansrelease.json after merging and before building
if you can. The build process also publishes to
https://nightlies.apache.org/netbeans/candidate/netbeans/ now which
currently has your build without a suffix. Aside - we should look at
adding -dev as suffix to files for this as fallback.
Nightlies might be a better update centre to share for testing too if
we need to in future.
Best wishes,
Neil
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-19 Thread László Kishalmi

Go on!

On Sun, Dec 18, 2022 at 12:03 PM Svata Dedic 
wrote:

> Hi,
>
> late Friday, a colleague discovered a bug in NbProjectInfoBuilder -
> mishandled compiler options (compilerArgs / allCompilerArgs /
> freeCompilerArgs) that fails to load the project when NB runs on JDK19.
> I can provide a fix tomorrow.
>
> -S.
>
> On 18. 12. 22 18:28, Neil C Smith wrote:
> > On Sun, 18 Dec 2022 at 16:58, Laszlo Kishalmi 
> wrote:
> >> I'm ready to update the netbeansrelease.json. In the 12.0-u1 and 12.0-u2
> >> it was just another entry with git hash, version and position. Would it
> >> be the same this time, or shall I use the vote entry as well. As far as
> >> I remember vote would remove the version suffix from the final artifacts
> >> and other places, that might be not required for 16-uc1.
> >
> > Yes, try as before and leave out vote.  That does very little now, but
> > I think will still stop the version suffix being added.  Eric even
> > better to answer that!  Quite a lot has changed since we did 12.0
> > updates, but all should hopefully work OK.
> >
> > Try to update netbeansrelease.json after merging and before building
> > if you can.  The build process also publishes to
> > https://nightlies.apache.org/netbeans/candidate/netbeans/ now which
> > currently has your build without a suffix.  Aside - we should look at
> > adding -dev as suffix to files for this as fallback.
> >
> > Nightlies might be a better update centre to share for testing too if
> > we need to in future.
> >
> > Best wishes,
> >
> > Neil
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-19 Thread Martin Balín

This issue will definitely be the one to include it in 16u1.
Martin

> On 18. 12. 2022, at 21:03, Svata Dedic  wrote:
> 
> Hi,
> 
> late Friday, a colleague discovered a bug in NbProjectInfoBuilder - 
> mishandled compiler options (compilerArgs / allCompilerArgs / 
> freeCompilerArgs) that fails to load the project when NB runs on JDK19. I can 
> provide a fix tomorrow.
> 
> -S.
> 
> On 18. 12. 22 18:28, Neil C Smith wrote:
>> On Sun, 18 Dec 2022 at 16:58, Laszlo Kishalmi  
>> wrote:
>>> I'm ready to update the netbeansrelease.json. In the 12.0-u1 and 12.0-u2
>>> it was just another entry with git hash, version and position. Would it
>>> be the same this time, or shall I use the vote entry as well. As far as
>>> I remember vote would remove the version suffix from the final artifacts
>>> and other places, that might be not required for 16-uc1.
>> Yes, try as before and leave out vote.  That does very little now, but
>> I think will still stop the version suffix being added.  Eric even
>> better to answer that!  Quite a lot has changed since we did 12.0
>> updates, but all should hopefully work OK.
>> Try to update netbeansrelease.json after merging and before building
>> if you can.  The build process also publishes to
>> https://nightlies.apache.org/netbeans/candidate/netbeans/ now which
>> currently has your build without a suffix.  Aside - we should look at
>> adding -dev as suffix to files for this as fallback.
>> Nightlies might be a better update centre to share for testing too if
>> we need to in future.
>> Best wishes,
>> Neil
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
>> For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-18 Thread Svata Dedic


Hi,

late Friday, a colleague discovered a bug in NbProjectInfoBuilder - 
mishandled compiler options (compilerArgs / allCompilerArgs / 
freeCompilerArgs) that fails to load the project when NB runs on JDK19. 
I can provide a fix tomorrow.


-S.

On 18. 12. 22 18:28, Neil C Smith wrote:

On Sun, 18 Dec 2022 at 16:58, Laszlo Kishalmi  wrote:

I'm ready to update the netbeansrelease.json. In the 12.0-u1 and 12.0-u2
it was just another entry with git hash, version and position. Would it
be the same this time, or shall I use the vote entry as well. As far as
I remember vote would remove the version suffix from the final artifacts
and other places, that might be not required for 16-uc1.


Yes, try as before and leave out vote.  That does very little now, but
I think will still stop the version suffix being added.  Eric even
better to answer that!  Quite a lot has changed since we did 12.0
updates, but all should hopefully work OK.

Try to update netbeansrelease.json after merging and before building
if you can.  The build process also publishes to
https://nightlies.apache.org/netbeans/candidate/netbeans/ now which
currently has your build without a suffix.  Aside - we should look at
adding -dev as suffix to files for this as fallback.

Nightlies might be a better update centre to share for testing too if
we need to in future.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-18 Thread Neil C Smith

On Sun, 18 Dec 2022 at 16:58, Laszlo Kishalmi  wrote:
> I'm ready to update the netbeansrelease.json. In the 12.0-u1 and 12.0-u2
> it was just another entry with git hash, version and position. Would it
> be the same this time, or shall I use the vote entry as well. As far as
> I remember vote would remove the version suffix from the final artifacts
> and other places, that might be not required for 16-uc1.

Yes, try as before and leave out vote.  That does very little now, but
I think will still stop the version suffix being added.  Eric even
better to answer that!  Quite a lot has changed since we did 12.0
updates, but all should hopefully work OK.

Try to update netbeansrelease.json after merging and before building
if you can.  The build process also publishes to
https://nightlies.apache.org/netbeans/candidate/netbeans/ now which
currently has your build without a suffix.  Aside - we should look at
adding -dev as suffix to files for this as fallback.

Nightlies might be a better update centre to share for testing too if
we need to in future.

Best wishes,

Neil

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

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-18 Thread Laszlo Kishalmi


Dear Neil,

I'm ready to update the netbeansrelease.json. In the 12.0-u1 and 12.0-u2 
it was just another entry with git hash, version and position. Would it 
be the same this time, or shall I use the vote entry as well. As far as 
I remember vote would remove the version suffix from the final artifacts 
and other places, that might be not required for 16-uc1.


On 12/16/22 23:43, Neil C Smith wrote:

On Sat, 17 Dec 2022, 07:08 László Kishalmi, 
wrote:


I have not planned another build, just with the one with the updated
netbeansrelease.json.


Sure, that was all I actually meant by another build. Certainly not
suggesting anything else should go in.

I thought initially the build date in the module implementation versions
was because of netbeansrelease.json not being updated, but it's not. It's a
bug we'll have to live with for 16u1 and try to resolve by 17.

Thanks,

Neil




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

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-16 Thread Neil C Smith

On Sat, 17 Dec 2022, 07:08 László Kishalmi, 
wrote:

> I have not planned another build, just with the one with the updated
> netbeansrelease.json.
>

Sure, that was all I actually meant by another build. Certainly not
suggesting anything else should go in.

I thought initially the build date in the module implementation versions
was because of netbeansrelease.json not being updated, but it's not. It's a
bug we'll have to live with for 16u1 and try to resolve by 17.

Thanks,

Neil

>

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-16 Thread László Kishalmi

Hi Neil!
I have not planned another build, just with the one with the updated
netbeansrelease.json.
I was swamped with work this week, so I need to assess the situation and
feedback during the weekend.

Both mentioned feature requests are doable for NB17

On Fri, Dec 16, 2022 at 2:03 AM Neil C Smith  wrote:

> On Fri, 16 Dec 2022 at 07:31, Ernie Rael  wrote:
> > On 22/12/15 9:34 AM, László Kishalmi wrote:
> > > Went ahead and merged the delivery to the release160 branch. The
> update can
> > > be tested by adding the following update center URL:
> > >
> > >
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/14/artifact/dist/netbeans/nbms/updates.xml.gz
> >
> > Still running NetBeans on JDK-11
> > Inalled update with plugin manager
> >  Once it is installed, there doesn't seem to be a way to tell from
> > the plugin
> >  manager that I'm using the new stuff, but
> >  org.netbeans.modules.gradle/2 [2.29.1
> > Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215]
> >  org.netbeans.modules.gradle.java [1.20.1.1
> > Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215]
>
> Will do some testing.  Laszlo, I assume you're already planning
> another build before vote?
>
> In case not, the hash and version needs to go into
>
> https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json
> before the build for the vote is triggered.
>
> Comment initially prompted by seeing the above implementation / build
> version with date rather than hash showing up.  That actually appears
> to be another issue.  As far as I can tell we have a bunch of modules
> where the implementation version in the update centre is different to
> the IDE build?!
>
> > BTW, it would be nice if the gradle version of the project was display
> > somewhere in the project's properties.
>
> +1.
>
> +2 if the UI supported updating the Gradle project wrapper next to that!
> :-)
>
> Best wishes,
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-16 Thread Neil C Smith

On Fri, 16 Dec 2022 at 07:31, Ernie Rael  wrote:
> On 22/12/15 9:34 AM, László Kishalmi wrote:
> > Went ahead and merged the delivery to the release160 branch. The update can
> > be tested by adding the following update center URL:
> >
> > https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/14/artifact/dist/netbeans/nbms/updates.xml.gz
>
> Still running NetBeans on JDK-11
> Inalled update with plugin manager
>  Once it is installed, there doesn't seem to be a way to tell from
> the plugin
>  manager that I'm using the new stuff, but
>  org.netbeans.modules.gradle/2 [2.29.1
> Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215]
>  org.netbeans.modules.gradle.java [1.20.1.1
> Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215]

Will do some testing.  Laszlo, I assume you're already planning
another build before vote?

In case not, the hash and version needs to go into
https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json
before the build for the vote is triggered.

Comment initially prompted by seeing the above implementation / build
version with date rather than hash showing up.  That actually appears
to be another issue.  As far as I can tell we have a bunch of modules
where the implementation version in the update centre is different to
the IDE build?!

> BTW, it would be nice if the gradle version of the project was display
> somewhere in the project's properties.

+1.

+2 if the UI supported updating the Gradle project wrapper next to that! :-)

Best wishes,

Neil

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

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-15 Thread Thomas Kellerer

I had problems that NB 16 did not load my Gradle 7.5.1 projects at all.
With the fix, those projects can now be loaded and build

Thanks a lot!

Thomas


László Kishalmi schrieb am 15.12.2022 um 18:34:
> Thanks for your understanding!
>
> Went ahead and merged the delivery to the release160 branch. The update can
> be tested by adding the following update center URL:
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/14/artifact/dist/netbeans/nbms/updates.xml.gz
> On 12/13/22 07:37, Martin Balin wrote:
>
> Hello,
> Most of the fixes there are related to VSNetBeans, although related to
> Gradle or projects infrastructure. I understand your intention was
> about Gradle update itself to the latest version. If listed PRs are
> too much then these can wait and I will do VSNetBeans 16.0.301 in
> January. Not making 16u1 too big, no problem.
>
> Martin

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

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-15 Thread Ernie Rael

On 22/12/15 9:34 AM, László Kishalmi wrote:

Thanks for your understanding!

Went ahead and merged the delivery to the release160 branch. The update can
be tested by adding the following update center URL:

https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/14/artifact/dist/netbeans/nbms/updates.xml.gz

Still running NetBeans on JDK-11
Inalled update with plugin manager
Once it is installed, there doesn't seem to be a way to tell from
the plugin

manager that I'm using the new stuff, but
org.netbeans.modules.gradle/2 [2.29.1
Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215]
org.netbeans.modules.gradle.java [1.20.1.1
Netbeans/netbeans-TLP/netbeans/release160-14-on-20221215]

Opened gradle 6.1.1 project, built it
Opened gradle 6.8.3 project, built it

Tried the compose project,
[#4865] Register JDPA and Java Compiler Output on Project level #4984
No change, still stuck waiting for debugger, manual attach OK.

Restarted NetBeans on JDK-17
Repeated everything and then some. Work the same.

Looks like I can now run NetBeans on JDK-17 and run gradle projects
that require JDK-8 or JDK-11. (and probably many combinations).

Thanks a lot.
-ernie

BTW, it would be nice if the gradle version of the project was display
somewhere in the project's properties.

On 12/13/22 07:37, Martin Balin wrote:

Hello,
Most of the fixes there are related to VSNetBeans, although related to
Gradle or projects infrastructure. I understand your intention was
about Gradle update itself to the latest version. If listed PRs are
too much then these can wait and I will do VSNetBeans 16.0.301 in
January. Not making 16u1 too big, no problem.

Martin

On 12. 12. 2022, at 23:42, Laszlo Kishalmi
wrote:

Dear all,

It seems my request went a bit too well, for my like. There are a few
enhancements marked, which I think would be better to leave for NB17.
(https://github.com/apache/netbeans/pulls?q=is%3Apr+is%3Aclosed+label%3A16u1

)

I've planned NB16u1 just to iron out the wrinkles in the Gradle
support, release it quick and distribute that an an NBM. I hope you
understand and don't mind, I'd not include those enhancements for now.
It's my fault not communicating this clear enough, so I give some time
and hear your voice in that. I'm sorry.

Otherwise the delivery branch is almost ready (the version bump is missing).
https://github.com/apache/netbeans/pulls?q=is%3Apr+milestone%3ANB16u1+is%3Aclosed

On 12/5/22 19:53, Laszlo Kishalmi wrote:

Well,

I'd like to do this ASAP, if my time allows, I'd kick off the vote
later this week.

We are probably ready wit the PR-s on master. I'd reuse the delivery
branch to collect the addendum to NB16, then will merge at once in
release160.

Since the milestone is NB16u1, let's mark your the wished PR-s with
"16u1" label.

I'm going to create cherry-picked PRs from those, and remove the label
when the PR is ready for NB16u1 milestone.

On 12/1/22 10:53, Martin Balin wrote:

Hi,
Any date in mind for this release? Lazslo, release before Christmas
break or after?
I propose to label PRs and Issues going to this 16.0.1patch release
with “16p1” label?
Martin

On 1. 12. 2022, at 17:21, Eric Barboni
wrote:

It will keep jenkins busy and trigger a build per commit and do all
release stack.
Only if a release date for release160 is set in the json, jenkins will
do apidoc only.

Using delivery may be more Jenkins friendly but I don't think it's a human :p.

Eric

-Message d'origine-
De : Neil C Smith
Envoyé : jeudi 1 décembre 2022 14:52
À : dev@netbeans.apache.org
Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16

On Mon, 28 Nov 2022 at 15:55, Neil C Smith
wrote:

On Mon, 28 Nov 2022 at 15:43, László Kishalmi
wrote:

release161 branch has been removed, PR-s have been re-targeted to
release160.

Great, thanks! I'm just waiting on votes for rest of additional
binaries to start and I'll close the main vote. Want to make sure
everything is OK before we merge anything else into the branch.

OK, everything done that needs to be done, so release160 can be
considered open again for merging.

However, I wonder whether we should have a transient branch like
delivery (now deleted) for merging into? Merges into release***
branches trigger a lot of things. Eric?

Best wishes,

Neil

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

For further information about the NetBeans mailing lists,

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-15 Thread László Kishalmi

Thanks for your understanding!

Went ahead and merged the delivery to the release160 branch. The update can
be tested by adding the following update center URL:

https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/14/artifact/dist/netbeans/nbms/updates.xml.gz
On 12/13/22 07:37, Martin Balin wrote:

Martin

On 12. 12. 2022, at 23:42, Laszlo Kishalmi
wrote:

Dear all,

)

Otherwise the delivery branch is almost ready (the version bump is missing).
https://github.com/apache/netbeans/pulls?q=is%3Apr+milestone%3ANB16u1+is%3Aclosed

On 12/5/22 19:53, Laszlo Kishalmi wrote:

Well,

I'd like to do this ASAP, if my time allows, I'd kick off the vote
later this week.

We are probably ready wit the PR-s on master. I'd reuse the delivery
branch to collect the addendum to NB16, then will merge at once in
release160.

Since the milestone is NB16u1, let's mark your the wished PR-s with
"16u1" label.

I'm going to create cherry-picked PRs from those, and remove the label
when the PR is ready for NB16u1 milestone.

On 12/1/22 10:53, Martin Balin wrote:

Hi,
Any date in mind for this release? Lazslo, release before Christmas
break or after?
I propose to label PRs and Issues going to this 16.0.1patch release
with “16p1” label?
Martin

On 1. 12. 2022, at 17:21, Eric Barboni
wrote:

It will keep jenkins busy and trigger a build per commit and do all
release stack.
Only if a release date for release160 is set in the json, jenkins will
do apidoc only.

Using delivery may be more Jenkins friendly but I don't think it's a human :p.

Eric

-Message d'origine-
De : Neil C Smith
Envoyé : jeudi 1 décembre 2022 14:52
À : dev@netbeans.apache.org
Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16

On Mon, 28 Nov 2022 at 15:55, Neil C Smith
wrote:

On Mon, 28 Nov 2022 at 15:43, László Kishalmi
wrote:

release161 branch has been removed, PR-s have been re-targeted to
release160.

Great, thanks! I'm just waiting on votes for rest of additional
binaries to start and I'll close the main vote. Want to make sure
everything is OK before we merge anything else into the branch.

OK, everything done that needs to be done, so release160 can be
considered open again for merging.

However, I wonder whether we should have a transient branch like
delivery (now deleted) for merging into? Merges into release***
branches trigger a lot of things. Eric?

Best wishes,

Neil

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

For further information about the NetBeans mailing lists,
visit:https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!IlQ-QlflBngiqiJ-XrDNRp8DGqUnn5Sje469nldr9SZqZxx_bezC8Mq8hTr8TmvWQ0jAtg5rxPxLEVA$

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

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-13 Thread Martin Balin

Hello,
Most of the fixes there are related to VSNetBeans, although related to Gradle 
or projects infrastructure. I understand your intention was about Gradle update 
itself to the latest version. If listed PRs are too much then these can wait 
and I will do VSNetBeans 16.0.301 in January. Not making 16u1 too big, no 
problem.

Martin

> On 12. 12. 2022, at 23:42, Laszlo Kishalmi  wrote:
> 
> Dear all,
> 
> It seems my request went a bit too well, for my like. There are a few 
> enhancements marked, which I think would be better to leave for NB17. 
> (https://github.com/apache/netbeans/pulls?q=is%3Apr+is%3Aclosed+label%3A16u1 
> )
> 
> I've planned NB16u1 just to iron out the wrinkles in the Gradle support, 
> release it quick and distribute that an an NBM. I hope you understand and 
> don't mind, I'd not include those enhancements for now. It's my fault not 
> communicating this clear enough, so I give some time and hear your voice in 
> that. I'm sorry.
> 
> Otherwise the delivery branch is almost ready (the version bump is missing).
> 
> https://github.com/apache/netbeans/pulls?q=is%3Apr+milestone%3ANB16u1+is%3Aclosed
>  
> 
> 
> 
> On 12/5/22 19:53, Laszlo Kishalmi wrote:
>> Well,
>> 
>> I'd like to do this ASAP, if my time allows, I'd kick off the vote later 
>> this week.
>> 
>> We are probably ready wit the PR-s on master. I'd reuse the delivery branch 
>> to collect the addendum to NB16, then will merge at once in release160.
>> 
>> Since the milestone is NB16u1, let's mark your the wished PR-s with "16u1" 
>> label.
>> 
>> I'm going to create cherry-picked PRs from those, and remove the label when 
>> the PR is ready for NB16u1 milestone.
>> 
>> On 12/1/22 10:53, Martin Balin wrote:
>>> Hi,
>>> Any date in mind for this release? Lazslo, release before Christmas break 
>>> or after?
>>> I propose to label PRs and Issues going to this 16.0.1patch release with 
>>> “16p1” label?
>>> Martin
>>> 
>>> 
 On 1. 12. 2022, at 17:21, Eric Barboni  wrote:
 
 It will keep jenkins busy and trigger a build per commit and do all 
 release stack.
 Only if a release date for release160 is set in the json, jenkins will do 
 apidoc only.
 
 
 Using delivery may be more Jenkins friendly but I don't think it's a human 
 :p.
 
 Eric
 
 
 -Message d'origine-
 De : Neil C Smith 
 Envoyé : jeudi 1 décembre 2022 14:52
 À : dev@netbeans.apache.org
 Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16
 
 On Mon, 28 Nov 2022 at 15:55, Neil C Smith  wrote:
> On Mon, 28 Nov 2022 at 15:43, László Kishalmi  
> wrote:
>> release161 branch has been removed, PR-s have been re-targeted to
>> release160.
> Great, thanks!  I'm just waiting on votes for rest of additional
> binaries to start and I'll close the main vote.  Want to make sure
> everything is OK before we merge anything else into the branch.
 OK, everything done that needs to be done, so release160 can be considered 
 open again for merging.
 
 However, I wonder whether we should have a transient branch like delivery 
 (now deleted) for merging into?  Merges into release*** branches trigger a 
 lot of things.  Eric?
 
 Best wishes,
 
 Neil
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
 For additional commands, e-mail: dev-h...@netbeans.apache.org
 
 For further information about the NetBeans mailing lists, visit:
 https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!IlQ-QlflBngiqiJ-XrDNRp8DGqUnn5Sje469nldr9SZqZxx_bezC8Mq8hTr8TmvWQ0jAtg5rxPxLEVA$
  
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
 For additional commands, e-mail: dev-h...@netbeans.apache.org
 
 For further information about the NetBeans mailing lists, visit:
 https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!IlQ-QlflBngiqiJ-XrDNRp8DGqUnn5Sje469nldr9SZqZxx_bezC8Mq8hTr8TmvWQ0jAtg5rxPxLEVA$
  
 
 
 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
>>> For additional commands, e-mail: dev-h...@netbeans.apache.org
>>> 
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists 
>>> 
>>> 
>>> 
>>> 
> 
>

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-12 Thread Laszlo Kishalmi

Dear all,

I've planned NB16u1 just to iron out the wrinkles in the Gradle support,
release it quick and distribute that an an NBM. I hope you understand
and don't mind, I'd not include those enhancements for now. It's my
fault not communicating this clear enough, so I give some time and hear
your voice in that. I'm sorry.

Otherwise the delivery branch is almost ready (the version bump is missing).

https://github.com/apache/netbeans/pulls?q=is%3Apr+milestone%3ANB16u1+is%3Aclosed

On 12/5/22 19:53, Laszlo Kishalmi wrote:

Well,

I'd like to do this ASAP, if my time allows, I'd kick off the vote
later this week.

We are probably ready wit the PR-s on master. I'd reuse the delivery
branch to collect the addendum to NB16, then will merge at once in
release160.

Since the milestone is NB16u1, let's mark your the wished PR-s with
"16u1" label.

I'm going to create cherry-picked PRs from those, and remove the label
when the PR is ready for NB16u1 milestone.

On 12/1/22 10:53, Martin Balin wrote:

Hi,
Any date in mind for this release? Lazslo, release before Christmas
break or after?
I propose to label PRs and Issues going to this 16.0.1patch release
with “16p1” label?

Martin

On 1. 12. 2022, at 17:21, Eric Barboni wrote:

It will keep jenkins busy and trigger a build per commit and do all
release stack.
Only if a release date for release160 is set in the json, jenkins
will do apidoc only.

Using delivery may be more Jenkins friendly but I don't think it's a
human :p.

Eric

-Message d'origine-
De : Neil C Smith
Envoyé : jeudi 1 décembre 2022 14:52
À : dev@netbeans.apache.org
Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16

On Mon, 28 Nov 2022 at 15:55, Neil C Smith
wrote:
On Mon, 28 Nov 2022 at 15:43, László Kishalmi
wrote:

release161 branch has been removed, PR-s have been re-targeted to
release160.

Great, thanks! I'm just waiting on votes for rest of additional
binaries to start and I'll close the main vote. Want to make sure
everything is OK before we merge anything else into the branch.
OK, everything done that needs to be done, so release160 can be
considered open again for merging.

However, I wonder whether we should have a transient branch like
delivery (now deleted) for merging into? Merges into release***
branches trigger a lot of things. Eric?

Best wishes,

Neil

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

For further information about the NetBeans mailing lists, visit:
https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!IlQ-QlflBngiqiJ-XrDNRp8DGqUnn5Sje469nldr9SZqZxx_bezC8Mq8hTr8TmvWQ0jAtg5rxPxLEVA$

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

For further information about the NetBeans mailing lists, visit:
https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!IlQ-QlflBngiqiJ-XrDNRp8DGqUnn5Sje469nldr9SZqZxx_bezC8Mq8hTr8TmvWQ0jAtg5rxPxLEVA$

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-06 Thread Neil C Smith

On Tue, 6 Dec 2022 at 03:54, Laszlo Kishalmi  wrote:
> Since the milestone is NB16u1, let's mark your the wished PR-s with
> "16u1" label.
>
> I'm going to create cherry-picked PRs from those, and remove the label
> when the PR is ready for NB16u1 milestone.

We do already have a Cherry Pick label for that purpose.

Either is fine, but if we're going to use temporary version labels,
let's delete both when this is done.  Be good to prune a few unused
ones!

Best wishes,

Neil

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

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

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

2022-12-05 Thread Laszlo Kishalmi

Well,

I'd like to do this ASAP, if my time allows, I'd kick off the vote later
this week.

We are probably ready wit the PR-s on master. I'd reuse the delivery
branch to collect the addendum to NB16, then will merge at once in
release160.

Since the milestone is NB16u1, let's mark your the wished PR-s with
"16u1" label.

I'm going to create cherry-picked PRs from those, and remove the label
when the PR is ready for NB16u1 milestone.

On 12/1/22 10:53, Martin Balin wrote:

Hi,
Any date in mind for this release? Lazslo, release before Christmas break or
after?
I propose to label PRs and Issues going to this 16.0.1patch release with “16p1”
label?
Martin

On 1. 12. 2022, at 17:21, Eric Barboni wrote:

It will keep jenkins busy and trigger a build per commit and do all release
stack.
Only if a release date for release160 is set in the json, jenkins will do
apidoc only.

Using delivery may be more Jenkins friendly but I don't think it's a human :p.

Eric

-Message d'origine-
De : Neil C Smith
Envoyé : jeudi 1 décembre 2022 14:52
À : dev@netbeans.apache.org
Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16

On Mon, 28 Nov 2022 at 15:55, Neil C Smith wrote:

On Mon, 28 Nov 2022 at 15:43, László Kishalmi wrote:

release161 branch has been removed, PR-s have been re-targeted to
release160.

Great, thanks! I'm just waiting on votes for rest of additional
binaries to start and I'll close the main vote. Want to make sure
everything is OK before we merge anything else into the branch.

OK, everything done that needs to be done, so release160 can be considered open
again for merging.

However, I wonder whether we should have a transient branch like delivery (now
deleted) for merging into? Merges into release*** branches trigger a lot of
things. Eric?