You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Laszlo Kishalmi <la...@gmail.com> on 2022/11/27 23:25:09 UTC
[DISCUSSION] Gradle Patch Release for NetBeans 16
Dear all,
This is a kind of notice / discussion.
Frequent visitors of GitHub might notice, that I've created a new
Milestone NB16u1. There are a handful of important fixes in our Gradle
Support that would improve the Gradle/JDK compatibility. I think those
are important, as some of them are fixing regressions.
It's a bit unfortunate that these fixes have arrived late of our NB16
release phase. They could be annoying, but I would not stop the release
train on them. So I've decided to step up and create an unusual patch
release for NB16. I would like it to keep this update release low
profile, so we could deliver it ASAP.
Some things to know:
* Created a branch for this named: release161
* The milestone is NB16u1
* I'm going to create PR-s against the new branch, by cherry-picking
PR-s landed on master.
* Once done, there would be (hopefully) one vote round on the whole
source release zip.
* NB16u1 will be delivered trough our Update Center. (Of course, the
zip source distribution would be available, but the convenience
binary would be just the nbm package)
* I would steer this small update release as an RM, if there would be
no objection.
Current PR candidates to be included in NB16u1:
* https://github.com/apache/netbeans/pull/5014
* https://github.com/apache/netbeans/pull/4995
* https://github.com/apache/netbeans/pull/4984
* https://github.com/apache/netbeans/pull/4985
Also I hope that there would be a fix for this as well:
https://github.com/apache/netbeans/issues/5015
As usual feedback is welcome!
--
Laszlo Kishalmi
Re: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Laszlo Kishalmi <la...@gmail.com>.
Yes. The UC, where it can be tested will be on Apache Jenkins. Once I
set up the build job, I'd post it here.
On 11/27/22 18:58, Ernie Rael wrote:
> I'm salivating at the thought of running NetBeans on a recent jdk and
> work on old gradle version projects.
>
> For testing, is it possible and simple to have a nb16u1 update center,
> which I can manually add locally?
>
> -ernie
>
> On 22/11/27 3:25 PM, Laszlo Kishalmi wrote:
>> Dear all,
>>
>> This is a kind of notice / discussion.
>>
>> Frequent visitors of GitHub might notice, that I've created a new
>> Milestone NB16u1. There are a handful of important fixes in our
>> Gradle Support that would improve the Gradle/JDK compatibility. I
>> think those are important, as some of them are fixing regressions.
>>
>> It's a bit unfortunate that these fixes have arrived late of our NB16
>> release phase. They could be annoying, but I would not stop the
>> release train on them. So I've decided to step up and create an
>> unusual patch release for NB16. I would like it to keep this update
>> release low profile, so we could deliver it ASAP.
>>
>> Some things to know:
>>
>> * Created a branch for this named: release161
>> * The milestone is NB16u1
>> * I'm going to create PR-s against the new branch, by cherry-picking
>> PR-s landed on master.
>> * Once done, there would be (hopefully) one vote round on the whole
>> source release zip.
>> * NB16u1 will be delivered trough our Update Center. (Of course, the
>> zip source distribution would be available, but the convenience
>> binary would be just the nbm package)
>> * I would steer this small update release as an RM, if there would be
>> no objection.
>>
>> Current PR candidates to be included in NB16u1:
>>
>> * https://github.com/apache/netbeans/pull/5014
>> * https://github.com/apache/netbeans/pull/4995
>> * https://github.com/apache/netbeans/pull/4984
>> * https://github.com/apache/netbeans/pull/4985
>>
>> Also I hope that there would be a fix for this as well:
>>
>> https://github.com/apache/netbeans/issues/5015
>>
>>
>> As usual feedback is welcome!
>>
>>
>> --
>>
>> Laszlo Kishalmi
>>
>
>
> ---------------------------------------------------------------------
> 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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Ernie Rael <er...@raelity.com>.
I'm salivating at the thought of running NetBeans on a recent jdk and
work on old gradle version projects.
For testing, is it possible and simple to have a nb16u1 update center,
which I can manually add locally?
-ernie
On 22/11/27 3:25 PM, Laszlo Kishalmi wrote:
> Dear all,
>
> This is a kind of notice / discussion.
>
> Frequent visitors of GitHub might notice, that I've created a new
> Milestone NB16u1. There are a handful of important fixes in our Gradle
> Support that would improve the Gradle/JDK compatibility. I think those
> are important, as some of them are fixing regressions.
>
> It's a bit unfortunate that these fixes have arrived late of our NB16
> release phase. They could be annoying, but I would not stop the
> release train on them. So I've decided to step up and create an
> unusual patch release for NB16. I would like it to keep this update
> release low profile, so we could deliver it ASAP.
>
> Some things to know:
>
> * Created a branch for this named: release161
> * The milestone is NB16u1
> * I'm going to create PR-s against the new branch, by cherry-picking
> PR-s landed on master.
> * Once done, there would be (hopefully) one vote round on the whole
> source release zip.
> * NB16u1 will be delivered trough our Update Center. (Of course, the
> zip source distribution would be available, but the convenience
> binary would be just the nbm package)
> * I would steer this small update release as an RM, if there would be
> no objection.
>
> Current PR candidates to be included in NB16u1:
>
> * https://github.com/apache/netbeans/pull/5014
> * https://github.com/apache/netbeans/pull/4995
> * https://github.com/apache/netbeans/pull/4984
> * https://github.com/apache/netbeans/pull/4985
>
> Also I hope that there would be a fix for this as well:
>
> https://github.com/apache/netbeans/issues/5015
>
>
> As usual feedback is welcome!
>
>
> --
>
> Laszlo Kishalmi
>
---------------------------------------------------------------------
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: [External] : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Martin Balin <mb...@apache.org>.
Hi,
Yes, there are several fixes which are related to Gradle & projects in general which did not make it to 16.0 because me and Svatopluk did not want to delay the release, e.g. https://github.com/apache/netbeans/pull/5006 <https://github.com/apache/netbeans/pull/5006> Getting these into 16.0.1 will be great. I can work on that.
Martin
> On 28. 11. 2022, at 10:08, Neil C Smith <ne...@apache.org> wrote:
>
> On Sun, 27 Nov 2022 at 23:25, Laszlo Kishalmi <la...@gmail.com> wrote:
>> It's a bit unfortunate that these fixes have arrived late of our NB16
>> release phase. They could be annoying, but I would not stop the release
>> train on them. So I've decided to step up and create an unusual patch
>> release for NB16. I would like it to keep this update release low
>> profile, so we could deliver it ASAP.
>
> Thanks! In principle, great ...
>
>> * Created a branch for this named: release161
>
> Please don't create extra branches called release*.
>
> The patch releases we've done in the past have gone into the release
> branch, and these need to as well. We don't need all the other things
> that come with release branches!
>
> However, you'll need to give us a few days to tidy up the main release
> vote and get branches tidied up. Please change the base branch on the
> PRs to release160, and I'll merge and/or notify you when we can merge.
> Can we delete release161 quite soon?
>
> Amongst other things, the extra branch would have been picked up by
> Jenkins, if the build pipeline wasn't currently marked as disabled! I
> know Eric was looking at some changes here - builds currently meant to
> be down?
>
>> * I would steer this small update release as an RM, if there would be
>> no objection.
>
> No objection to you taking a lead on signing, vote, etc. However, we
> don't have individual RMs on main releases any more for a reason.
> Please liaise with us (release team) on build, schedule, etc. Martin
> might want to consider whether VSCode needs the same updates? Eric
> and I might want to check implications on build process, nightly
> publishing, etc. And the links that will need to go into the catalog
> file have changed since the last time we did this.
>
> We should also look at documenting it this time! :-)
>
> 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://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!I9WKr_2TgmRXcJVBLcE0ksW22GbVfSRYjVXSWK-x_KGJGI3DWr6OlsFSJ8OmHwGeJ6uNePGSO9zipadrHKs2Hw$
>
>
>
Re: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Sun, 27 Nov 2022 at 23:25, Laszlo Kishalmi <la...@gmail.com> wrote:
> It's a bit unfortunate that these fixes have arrived late of our NB16
> release phase. They could be annoying, but I would not stop the release
> train on them. So I've decided to step up and create an unusual patch
> release for NB16. I would like it to keep this update release low
> profile, so we could deliver it ASAP.
Thanks! In principle, great ...
> * Created a branch for this named: release161
Please don't create extra branches called release*.
The patch releases we've done in the past have gone into the release
branch, and these need to as well. We don't need all the other things
that come with release branches!
However, you'll need to give us a few days to tidy up the main release
vote and get branches tidied up. Please change the base branch on the
PRs to release160, and I'll merge and/or notify you when we can merge.
Can we delete release161 quite soon?
Amongst other things, the extra branch would have been picked up by
Jenkins, if the build pipeline wasn't currently marked as disabled! I
know Eric was looking at some changes here - builds currently meant to
be down?
> * I would steer this small update release as an RM, if there would be
> no objection.
No objection to you taking a lead on signing, vote, etc. However, we
don't have individual RMs on main releases any more for a reason.
Please liaise with us (release team) on build, schedule, etc. Martin
might want to consider whether VSCode needs the same updates? Eric
and I might want to check implications on build process, nightly
publishing, etc. And the links that will need to go into the catalog
file have changed since the last time we did this.
We should also look at documenting it this time! :-)
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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by László Kishalmi <la...@gmail.com>.
Yes, exactly.
On Sun, Nov 27, 2022, 17:47 Michael Bien <mb...@gmail.com> wrote:
> On 28.11.22 00:25, Laszlo Kishalmi wrote:
> > Dear all,
> >
> > This is a kind of notice / discussion.
> >
> > Frequent visitors of GitHub might notice, that I've created a new
> > Milestone NB16u1. There are a handful of important fixes in our Gradle
> > Support that would improve the Gradle/JDK compatibility. I think those
> > are important, as some of them are fixing regressions.
> >
> > It's a bit unfortunate that these fixes have arrived late of our NB16
> > release phase. They could be annoying, but I would not stop the
> > release train on them. So I've decided to step up and create an
> > unusual patch release for NB16. I would like it to keep this update
> > release low profile, so we could deliver it ASAP.
> >
> > Some things to know:
> >
> > * Created a branch for this named: release161
> > * The milestone is NB16u1
> > * I'm going to create PR-s against the new branch, by cherry-picking
> > PR-s landed on master.
> > * Once done, there would be (hopefully) one vote round on the whole
> > source release zip.
> > * NB16u1 will be delivered trough our Update Center. (Of course, the
> > zip source distribution would be available, but the convenience
> > binary would be just the nbm package)
> > * I would steer this small update release as an RM, if there would be
> > no objection.
> >
> > Current PR candidates to be included in NB16u1:
> >
> > * https://github.com/apache/netbeans/pull/5014
> > * https://github.com/apache/netbeans/pull/4995
> > * https://github.com/apache/netbeans/pull/4984
> > * https://github.com/apache/netbeans/pull/4985
> >
> > Also I hope that there would be a fix for this as well:
> >
> > https://github.com/apache/netbeans/issues/5015
> >
> >
> > As usual feedback is welcome!
>
> I think I like this approach. Just to be sure I understand: this also
> means there will be no RELEASE161 artifacts in maven-central? The only
> binaries of this release are the updated gradle modules in the update
> center?
>
> -mbien
>
> >
> >
> > --
> >
> > Laszlo Kishalmi
> >
>
>
Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by László Kishalmi <la...@gmail.com>.
Go on!
On Sun, Dec 18, 2022 at 12:03 PM Svata Dedic <sv...@gmail.com>
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 <la...@gmail.com>
> 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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Laszlo Kishalmi <la...@gmail.com>.
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 <la...@gmail.com> 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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Fri, 23 Dec 2022 at 06:35, Laszlo Kishalmi <la...@gmail.com> 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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Laszlo Kishalmi <la...@gmail.com>.
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 <sv...@gmail.com> 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 <la...@gmail.com> 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-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
>>
>>
>>
>
> ---------------------------------------------------------------------
> 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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Martin Balín <ma...@windowslive.com>.
This issue will definitely be the one to include it in 16u1.
Martin
> On 18. 12. 2022, at 21:03, Svata Dedic <sv...@gmail.com> 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 <la...@gmail.com> 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-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
>
>
>
---------------------------------------------------------------------
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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Svata Dedic <sv...@gmail.com>.
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 <la...@gmail.com> 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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Sun, 18 Dec 2022 at 16:58, Laszlo Kishalmi <la...@gmail.com> 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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Laszlo Kishalmi <la...@gmail.com>.
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, <la...@gmail.com>
> 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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Sat, 17 Dec 2022, 07:08 László Kishalmi, <la...@gmail.com>
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
Posted by László Kishalmi <la...@gmail.com>.
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 <ne...@apache.org> wrote:
> On Fri, 16 Dec 2022 at 07:31, Ernie Rael <er...@raelity.com> 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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Fri, 16 Dec 2022 at 07:31, Ernie Rael <er...@raelity.com> 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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Ernie Rael <er...@raelity.com>.
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 <la...@gmail.com>
> <la...@gmail.com> 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
> <https://github.com/apache/netbeans/pulls?q=is%3Apr+is%3Aclosed+label%3A16u1>
> <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
> <https://github.com/apache/netbeans/pulls?q=is%3Apr+milestone%3ANB16u1+is%3Aclosed>
> <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 <sk...@apache.org>
> <sk...@apache.org> 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 <ne...@apache.org> <ne...@apache.org>
> 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 <ne...@apache.org>
> <ne...@apache.org> wrote:
>
> On Mon, 28 Nov 2022 at 15:43, László Kishalmi
> <la...@gmail.com> <la...@gmail.com> 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-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@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-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@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-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
> <https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists>
> <https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> <ma...@netbeans.apache.org>
> <de...@netbeans.apache.org>
> For additional commands, e-mail: dev-help@netbeans.apache.org
> <ma...@netbeans.apache.org> <de...@netbeans.apache.org>
>
> For further information about the NetBeans mailing lists,
> visit:https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> <https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists>
> <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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Thomas Kellerer <sh...@gmx.net>.
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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by László Kishalmi <la...@gmail.com>.
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
On 12. 12. 2022, at 23:42, Laszlo Kishalmi <la...@gmail.com>
<la...@gmail.com> 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
<https://github.com/apache/netbeans/pulls?q=is%3Apr+is%3Aclosed+label%3A16u1>
<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
<https://github.com/apache/netbeans/pulls?q=is%3Apr+milestone%3ANB16u1+is%3Aclosed>
<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 <sk...@apache.org>
<sk...@apache.org> 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 <ne...@apache.org> <ne...@apache.org>
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 <ne...@apache.org>
<ne...@apache.org> wrote:
On Mon, 28 Nov 2022 at 15:43, László Kishalmi
<la...@gmail.com> <la...@gmail.com> 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-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@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-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@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-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
<https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists>
<https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
<ma...@netbeans.apache.org>
<de...@netbeans.apache.org>
For additional commands, e-mail: dev-help@netbeans.apache.org
<ma...@netbeans.apache.org> <de...@netbeans.apache.org>
For further information about the NetBeans mailing lists,
visit:https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
<https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists>
<https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists>
Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Martin Balin <mb...@apache.org>.
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 <la...@gmail.com> 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 <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 <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 <sk...@apache.org> 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 <ne...@apache.org>
>>>> 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 <ne...@apache.org> wrote:
>>>>> On Mon, 28 Nov 2022 at 15:43, László Kishalmi <la...@gmail.com> 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-unsubscribe@netbeans.apache.org
>>>> For additional commands, e-mail: dev-help@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-unsubscribe@netbeans.apache.org
>>>> For additional commands, e-mail: dev-help@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-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 <https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists>
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org <ma...@netbeans.apache.org>
> For additional commands, e-mail: dev-help@netbeans.apache.org <ma...@netbeans.apache.org>
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists <https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists>
Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Laszlo Kishalmi <la...@gmail.com>.
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 <sk...@apache.org> 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 <ne...@apache.org>
>>> 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 <ne...@apache.org>
>>> wrote:
>>>> On Mon, 28 Nov 2022 at 15:43, László Kishalmi
>>>> <la...@gmail.com> 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-unsubscribe@netbeans.apache.org
>>> For additional commands, e-mail: dev-help@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-unsubscribe@netbeans.apache.org
>>> For additional commands, e-mail: dev-help@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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 6 Dec 2022 at 03:54, Laszlo Kishalmi <la...@gmail.com> 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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Laszlo Kishalmi <la...@gmail.com>.
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 <sk...@apache.org> 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 <ne...@apache.org>
>> 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 <ne...@apache.org> wrote:
>>> On Mon, 28 Nov 2022 at 15:43, László Kishalmi <la...@gmail.com> 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-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@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-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@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-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: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Martin Balin <mb...@apache.org>.
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 <sk...@apache.org> 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 <ne...@apache.org>
> 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 <ne...@apache.org> wrote:
>>
>> On Mon, 28 Nov 2022 at 15:43, László Kishalmi <la...@gmail.com> 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-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@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-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@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-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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Eric Barboni <sk...@apache.org>.
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 <ne...@apache.org>
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 <ne...@apache.org> wrote:
>
> On Mon, 28 Nov 2022 at 15:43, László Kishalmi <la...@gmail.com> 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-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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Mon, 28 Nov 2022 at 15:55, Neil C Smith <ne...@apache.org> wrote:
>
> On Mon, 28 Nov 2022 at 15:43, László Kishalmi <la...@gmail.com> 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-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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Mon, 28 Nov 2022 at 15:43, László Kishalmi <la...@gmail.com> 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.
> We had as far as I remember 3 update releases for 12 LTS. Out of the 3 one
> was released with maven artifacts due to some issues with the original
> RELEASE120.
Funny, my memory was that there had been 3 too, but only 2 listed in
netbeansrelease.json. Maybe it just got discussed?
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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by László Kishalmi <la...@gmail.com>.
Dear all,
release161 branch has been removed, PR-s have been re-targeted to
release160.
We had as far as I remember 3 update releases for 12 LTS. Out of the 3 one
was released with maven artifacts due to some issues with the original
RELEASE120.
On Mon, Nov 28, 2022 at 5:57 AM Eric Barboni <sk...@apache.org> wrote:
> Hi,
> Sorry for the disabled jobs. Was not intended. Thought it was because too
> many scan last week.
>
> If we can assume that release160 is ok then you have to check for
>
> https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json
> section release160
> and a adapt to add the new commit hash (should be a tag ) (with name u1 )
> and maven version "mavenversion": "RELEASE160-u1" if a new maven is needed,
> vsixVersion if needed
> build job build the last artefacts but the RM can choose to not call a
> vote on them
>
> For the BOM approach , could be nice but I guess we should use the apache
> groupId, (org.apache.netbeans) otherwise we will have our RELEASE* in the
> path to get a proper last version.
>
> Best Regards
> Eric
>
> -----Message d'origine-----
> De : Neil C Smith <ne...@apache.org>
> Envoyé : lundi 28 novembre 2022 12:26
> À : Michael Bien <mb...@gmail.com>
> Cc : dev@netbeans.apache.org
> Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16
>
> On Mon, 28 Nov 2022 at 10:22, Michael Bien <mb...@gmail.com> wrote:
> >
> > On 28.11.22 10:16, Neil C Smith wrote:
> > > On Mon, 28 Nov 2022 at 01:47, Michael Bien <mb...@gmail.com> wrote:
> > >> I think I like this approach. Just to be sure I understand: this
> > >> also means there will be no RELEASE161 artifacts in maven-central?
> > >> The only binaries of this release are the updated gradle modules in
> > >> the update center?
> > > I can't say I "like" the approach. :-) It's the one we have, and
> > > it's a bit of a pain, which is why we've not done it very often!
> >
> > Yeah I can see that. I just think it is good to have a
> > more-lightweight way of releasing a patch if there is the need.
>
> If you think my comment was based on it being too lightweight, you've
> misunderstood what I meant! The need to manually splice two update
> catalogs, one for testing and voting, then the main one for releasing, is a
> pain.
>
> At least we don't have to JAR sign the NBMs any more! But yes, practice,
> documenting, and (ideally) some automation would be good.
> particularly if we need to ship high priority updates.
>
> > Eric knows since he told me how to filter the versions you see on the
> > new NB application wizard. There is also a 120-1 btw ;)
>
> That was for a different reason, I believe. Looks like the u1 was
> requested by Jaroslav -
> https://lists.apache.org/thread/pn9w856x14gqjj4dm9949sgh5vjnod5n
> Discussion of BOM there too.
>
> Another old discussion on update process which might be of interest (also
> bit on BOM) -
> https://lists.apache.org/thread/ysvpkxnnjp22rdv040msvh4o14xn2lds
>
> > There is probably only one u1 since there was only one update to the
> > LTS release, right?
>
> There were two. There was also an 11.2-u1 which didn't get a Maven
> update. There were earlier ones too, but not listed in
> netbeansrelease.json as the build process changed with 11.2, which also
> changed the patch release process to that outlined in the above threads.
> Not that we've done that for a while. And it also appears that I said the
> splicing of the catalog is "not too much work" - I may have changed my
> mind! :-)
>
> > I bet you are already thinking about how to preload the update in your
> > codelerity NB bundles :)
>
> Not unless we decide to release an updated Apache NetBeans binary zip.
> Our installers will always use the contents of the latest binary zip
> release, and you can do a binary comparison of the contents (a deliberate
> design decision).
>
> 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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Eric Barboni <sk...@apache.org>.
Hi,
Sorry for the disabled jobs. Was not intended. Thought it was because too many scan last week.
If we can assume that release160 is ok then you have to check for
https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json section release160
and a adapt to add the new commit hash (should be a tag ) (with name u1 ) and maven version "mavenversion": "RELEASE160-u1" if a new maven is needed, vsixVersion if needed
build job build the last artefacts but the RM can choose to not call a vote on them
For the BOM approach , could be nice but I guess we should use the apache groupId, (org.apache.netbeans) otherwise we will have our RELEASE* in the path to get a proper last version.
Best Regards
Eric
-----Message d'origine-----
De : Neil C Smith <ne...@apache.org>
Envoyé : lundi 28 novembre 2022 12:26
À : Michael Bien <mb...@gmail.com>
Cc : dev@netbeans.apache.org
Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16
On Mon, 28 Nov 2022 at 10:22, Michael Bien <mb...@gmail.com> wrote:
>
> On 28.11.22 10:16, Neil C Smith wrote:
> > On Mon, 28 Nov 2022 at 01:47, Michael Bien <mb...@gmail.com> wrote:
> >> I think I like this approach. Just to be sure I understand: this
> >> also means there will be no RELEASE161 artifacts in maven-central?
> >> The only binaries of this release are the updated gradle modules in
> >> the update center?
> > I can't say I "like" the approach. :-) It's the one we have, and
> > it's a bit of a pain, which is why we've not done it very often!
>
> Yeah I can see that. I just think it is good to have a
> more-lightweight way of releasing a patch if there is the need.
If you think my comment was based on it being too lightweight, you've misunderstood what I meant! The need to manually splice two update catalogs, one for testing and voting, then the main one for releasing, is a pain.
At least we don't have to JAR sign the NBMs any more! But yes, practice, documenting, and (ideally) some automation would be good.
particularly if we need to ship high priority updates.
> Eric knows since he told me how to filter the versions you see on the
> new NB application wizard. There is also a 120-1 btw ;)
That was for a different reason, I believe. Looks like the u1 was requested by Jaroslav - https://lists.apache.org/thread/pn9w856x14gqjj4dm9949sgh5vjnod5n
Discussion of BOM there too.
Another old discussion on update process which might be of interest (also bit on BOM) - https://lists.apache.org/thread/ysvpkxnnjp22rdv040msvh4o14xn2lds
> There is probably only one u1 since there was only one update to the
> LTS release, right?
There were two. There was also an 11.2-u1 which didn't get a Maven update. There were earlier ones too, but not listed in netbeansrelease.json as the build process changed with 11.2, which also changed the patch release process to that outlined in the above threads. Not that we've done that for a while. And it also appears that I said the splicing of the catalog is "not too much work" - I may have changed my mind! :-)
> I bet you are already thinking about how to preload the update in your
> codelerity NB bundles :)
Not unless we decide to release an updated Apache NetBeans binary zip.
Our installers will always use the contents of the latest binary zip release, and you can do a binary comparison of the contents (a deliberate design decision).
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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Mon, 28 Nov 2022 at 10:22, Michael Bien <mb...@gmail.com> wrote:
>
> On 28.11.22 10:16, Neil C Smith wrote:
> > On Mon, 28 Nov 2022 at 01:47, Michael Bien <mb...@gmail.com> wrote:
> >> I think I like this approach. Just to be sure I understand: this also
> >> means there will be no RELEASE161 artifacts in maven-central? The only
> >> binaries of this release are the updated gradle modules in the update
> >> center?
> > I can't say I "like" the approach. :-) It's the one we have, and it's
> > a bit of a pain, which is why we've not done it very often!
>
> Yeah I can see that. I just think it is good to have a more-lightweight
> way of releasing a patch if there is the need.
If you think my comment was based on it being too lightweight, you've
misunderstood what I meant! The need to manually splice two update
catalogs, one for testing and voting, then the main one for releasing,
is a pain.
At least we don't have to JAR sign the NBMs any more! But yes,
practice, documenting, and (ideally) some automation would be good.
particularly if we need to ship high priority updates.
> Eric knows since he told me how to filter the versions you see on the
> new NB application wizard. There is also a 120-1 btw ;)
That was for a different reason, I believe. Looks like the u1 was
requested by Jaroslav -
https://lists.apache.org/thread/pn9w856x14gqjj4dm9949sgh5vjnod5n
Discussion of BOM there too.
Another old discussion on update process which might be of interest
(also bit on BOM) -
https://lists.apache.org/thread/ysvpkxnnjp22rdv040msvh4o14xn2lds
> There is probably only one u1 since there was only one update to the LTS
> release, right?
There were two. There was also an 11.2-u1 which didn't get a Maven
update. There were earlier ones too, but not listed in
netbeansrelease.json as the build process changed with 11.2, which
also changed the patch release process to that outlined in the above
threads. Not that we've done that for a while. And it also appears
that I said the splicing of the catalog is "not too much work" - I may
have changed my mind! :-)
> I bet you are already thinking about how to preload the update in your
> codelerity NB bundles :)
Not unless we decide to release an updated Apache NetBeans binary zip.
Our installers will always use the contents of the latest binary zip
release, and you can do a binary comparison of the contents (a
deliberate design decision).
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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Michael Bien <mb...@gmail.com>.
On 28.11.22 10:16, Neil C Smith wrote:
> On Mon, 28 Nov 2022 at 01:47, Michael Bien <mb...@gmail.com> wrote:
>> I think I like this approach. Just to be sure I understand: this also
>> means there will be no RELEASE161 artifacts in maven-central? The only
>> binaries of this release are the updated gradle modules in the update
>> center?
> I can't say I "like" the approach. :-) It's the one we have, and it's
> a bit of a pain, which is why we've not done it very often!
Yeah I can see that. I just think it is good to have a more-lightweight
way of releasing a patch if there is the need.
Its also good to practice this from time to time for bugfixes to make
sure the process is working in case of high priority security fixes.
>
> We've only pushed Maven artefacts for a patch update once - see
> RELEASE120-u1. I can't remember why we chose to on that one.
Eric knows since he told me how to filter the versions you see on the
new NB application wizard. There is also a 120-1 btw ;)
The maven build of 120 didn't work properly that is why its filtered out
if I remember correctly (i believe thats basically why 120-1 exists).
There is probably only one u1 since there was only one update to the LTS
release, right?
> The only way I can think we could change that, which has been
> discussed before, is publishing all modules via spec version instead,
> and publishing a cluster BOM for all releases and patch updates. It
> would be a good change, but also potentially a lot of work for
> something we only need infrequently.
I bet you are already thinking about how to preload the update in your
codelerity NB bundles :)
best regards,
michael
>
> 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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Neil C Smith <ne...@apache.org>.
On Mon, 28 Nov 2022 at 01:47, Michael Bien <mb...@gmail.com> wrote:
> I think I like this approach. Just to be sure I understand: this also
> means there will be no RELEASE161 artifacts in maven-central? The only
> binaries of this release are the updated gradle modules in the update
> center?
I can't say I "like" the approach. :-) It's the one we have, and it's
a bit of a pain, which is why we've not done it very often!
We've only pushed Maven artefacts for a patch update once - see
RELEASE120-u1. I can't remember why we chose to on that one.
The only way I can think we could change that, which has been
discussed before, is publishing all modules via spec version instead,
and publishing a cluster BOM for all releases and patch updates. It
would be a good change, but also potentially a lot of work for
something we only need infrequently.
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: [DISCUSSION] Gradle Patch Release for NetBeans 16
Posted by Michael Bien <mb...@gmail.com>.
On 28.11.22 00:25, Laszlo Kishalmi wrote:
> Dear all,
>
> This is a kind of notice / discussion.
>
> Frequent visitors of GitHub might notice, that I've created a new
> Milestone NB16u1. There are a handful of important fixes in our Gradle
> Support that would improve the Gradle/JDK compatibility. I think those
> are important, as some of them are fixing regressions.
>
> It's a bit unfortunate that these fixes have arrived late of our NB16
> release phase. They could be annoying, but I would not stop the
> release train on them. So I've decided to step up and create an
> unusual patch release for NB16. I would like it to keep this update
> release low profile, so we could deliver it ASAP.
>
> Some things to know:
>
> * Created a branch for this named: release161
> * The milestone is NB16u1
> * I'm going to create PR-s against the new branch, by cherry-picking
> PR-s landed on master.
> * Once done, there would be (hopefully) one vote round on the whole
> source release zip.
> * NB16u1 will be delivered trough our Update Center. (Of course, the
> zip source distribution would be available, but the convenience
> binary would be just the nbm package)
> * I would steer this small update release as an RM, if there would be
> no objection.
>
> Current PR candidates to be included in NB16u1:
>
> * https://github.com/apache/netbeans/pull/5014
> * https://github.com/apache/netbeans/pull/4995
> * https://github.com/apache/netbeans/pull/4984
> * https://github.com/apache/netbeans/pull/4985
>
> Also I hope that there would be a fix for this as well:
>
> https://github.com/apache/netbeans/issues/5015
>
>
> As usual feedback is welcome!
I think I like this approach. Just to be sure I understand: this also
means there will be no RELEASE161 artifacts in maven-central? The only
binaries of this release are the updated gradle modules in the update
center?
-mbien
>
>
> --
>
> Laszlo Kishalmi
>
---------------------------------------------------------------------
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