Re: Website changes for NB 11.1
+1 I like your proposal for the website. Josh Juneau juneau...@gmail.com http://jj-blogger.blogspot.com https://www.apress.com/us/search?query=Juneau > On Jul 10, 2019, at 4:03 AM, Neil C Smith wrote: > > Hi, > > I'm just merging and preparing for the vote thread on NB 11.1. And > while I'm waiting on things, thinking about website requirements as I > know some changes are underway already. > > At present the Downloads link goes directly to > http://netbeans.apache.org/download/nb110/nb110.html I don't think we > should directly link NB 11.1 in that way. Now we have LTS and > non-LTS, we need to consider how we present LTS and non-LTS to end > users, and make sure links to both remain easily available. > > My thought is that we should make the main menu Download go (revert) > to http://netbeans.apache.org/download/ and edit that page to include > a short intro to release schedule and which version to choose. And > move everything that isn't latest LTS and non-LTS on to sub-pages? > > eg something like. > > # Download > > Apache NetBeans is released four times a year. Our April release is a > long-term support (LTS) release that benefits from our famous NetCAT > community testing process, and will remain available and supported for > a year. Our other quarterly releases provide early access to new > features. > > ## Apache NetBeans 11 feature update 1 (NB 11.1) > Latest release of the IDE, released on July XX, 2019. > [Features][Download] > > ## Apache NetBeans 11 LTS (NB 11.0) > Latest LTS version of the IDE, released on April 4, 2019. > [Features][Download] > > ## Older releases > Older Apache NetBeans releases and pre-Apache NetBeans releases can > still be downloaded, but are no longer supported. > [Find out more] << move all text and links to sub-page > > ## Daily builds and building from source > All Apache NetBeans source code is freely available to build yourself, > or you can download (unsupported) daily development builds. > [Find out more] << move all text and links to sub-page > > > Thoughts? > > 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 > > >
[VOTE] Release Apache NetBeans 11.1 [vote candidate 1]
Dear all, This is our first voting candidate for the 11.1 release of Apache NetBeans. Apache NetBeans 11.1 constitutes all clusters in the Apache NetBeans Git repo, which together provide the NetBeans Platform (i.e., the underlying application framework), as well as all the modules that provide the Java SE, Java EE, PHP, JavaScript and Groovy features of Apache NetBeans. Build artefacts are available here: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.1-vc1/ https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.1-vc1/ Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and NOTICE files, as well as a README file with build instructions, which are the same as these: https://github.com/apache/netbeans/blob/release111/README.md We are voting on: https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.1-vc1/netbeans-11.1-vc1-source.zip SHA512: 7f49cfca8d27f2e08d0e5d9b4f61d70baddfdfa013f4a783feb2a1e203d7a1c7208321cdb0be7aa49d469c027e221999c8c0e4b9d911eec35a7d2e3cf8859466 ./netbeans-11.1-vc1-source.zip KEYS file: https://dist.apache.org/repos/dist/release/netbeans/KEYS Apache NetBeans Git Repo tag: 11.1-vc1 : https://github.com/apache/netbeans/tree/11.1-vc1 Note: NetBeans license violation checks are managed via the rat-exclusions.txt file: https://github.com/apache/netbeans/blob/release111/nbbuild/rat-exclusions.txt Rat report shows no unknown licenses, except for license files: https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-release/423/artifact/rat-release-temp/nbbuild/build/rat-report.txt Release specific wiki page: https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.1 How (and what) to try out with the release: 1. Download the artefact to be voted on and unzip it. 2. Check that the artefact does not contain any jar files, except for: - platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar which are only jars by their name 3. Verify the cryptographic signatures, the NOTICE and LICENSE file 4. Build it using the README provided by the artefact. 5. Look in nbbuild/netbeans for the NetBeans installation created by the build process. This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as usual. Please mark your vote with (binding) if you're a NetBeans PMC member to help with voting admin. NetBeans 11.1 will be released if and when this vote passes. Convenience binaries, not relevant for voting purposes, are staged at the build artefacts links above. Thank you for all the hard work! And fingers X'd my first release voting thread is all correct - speak up if there are any issues. Best wishes, Neil Volunteer Release Manager for Apache NetBeans 11.1 - 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: Final preparation for NB 11.1 voting
On Wed, 10 Jul 2019 at 14:33, Eric Barboni wrote: > > My bad, I wrote a mail last week for the building pipeline. No problem, I just hadn't realised you'd intended that pipeline to be used in the release process (yet) Just found an issue with sig tests that's also delaying the release thread - so much for this being an easy day! :-) > But yes source vote only, but I'm not sure convenience that use apache infra > can be populated without control. Totally agree. The PMC has a responsibility to ensure that things under our dist control are OK. Hence my comment earlier about a sanity check thread. ie. something like committer uploads to dist/dev, opens a mailing list thread, and as soon as three +1 checks from other PMC members, convenience binaries get moved over to dist/release? Obviously somewhat different for Maven artefacts in terms of where they end up, but same principle? I wonder how other projects handle this aspect? 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: Final preparation for NB 11.1 voting
My bad, I wrote a mail last week for the building pipeline. But yes source vote only, but I'm not sure convenience that use apache infra can be populated without control. Go ahead I will do a maven release later. Regards Eric -Message d'origine- De : Neil C Smith Envoyé : mercredi 10 juillet 2019 14:26 À : dev Objet : Re: Final preparation for NB 11.1 voting On Wed, 10 Jul 2019 at 12:43, Eric Barboni wrote: > I guess that the "new" Jenkins task do the same than the release job (need > review to be sure)). Yes, not exactly filling me with confidence there! :-) Anyway, other build tasks (Snap, Installers, etc.) rely on the netbeans-release task. Ideally all the Maven stuff would too, or we switch everything over to the new pipeline. But, an email literally 5min before I was triggering the voting candidate build, and without us having used that pipeline for any of the betas or tested with any of the depending tasks, doesn't feel right. So, unless we intend to push the schedule back by at least a week to fit in another beta, my intention is to go ahead with a vc off of netbeans-release today. Then we can figure out what's missing and how to get it in place ... > AFAIK, we vote also the nbm files as conveniences libraries, so maven > artefact are part of this concept. We don't vote on the nbms or the binaries of the IDE or platform. We vote on the sources. See eg. http://www.apache.org/legal/release-policy.html#compiled-packages The important thing is that all the source required to build the binary artefacts is in the source releases we vote on. I'm assuming this is the case, even if we might be missing some instructions? The PMC also has responsibility to ensure any convenience binaries are correctly made, signed, etc. But AFAIK we can have a sanity check thread about them after the release vote if necessary. Thanks and 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: Final preparation for NB 11.1 voting
True. :-) Gj On Wed, Jul 10, 2019 at 2:44 PM Neil C Smith wrote: > On Wed, 10 Jul 2019 at 13:39, Geertjan Wielenga > wrote: > > > > Just a note -- there's quite some new code, especially around Java EE 8 > and > > Payara, that will be in the vc for the first time -- and therefore we > > should not be surprised if we might need a vc2 to solve issues that might > > come up immediately when we try out those newest new features. We may not > > need a vc2, but if we do, we shouldn't be very surprised. > > Well, I'm at least hopeful we won't! Bear in mind, we've had three > betas, which in NB 11.0 were also called vc. So by NB 11.0 standards > this is vc4. :-) > > 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: Final preparation for NB 11.1 voting
On Wed, 10 Jul 2019 at 13:39, Geertjan Wielenga wrote: > > Just a note -- there's quite some new code, especially around Java EE 8 and > Payara, that will be in the vc for the first time -- and therefore we > should not be surprised if we might need a vc2 to solve issues that might > come up immediately when we try out those newest new features. We may not > need a vc2, but if we do, we shouldn't be very surprised. Well, I'm at least hopeful we won't! Bear in mind, we've had three betas, which in NB 11.0 were also called vc. So by NB 11.0 standards this is vc4. :-) 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: Final preparation for NB 11.1 voting
Just a note -- there's quite some new code, especially around Java EE 8 and Payara, that will be in the vc for the first time -- and therefore we should not be surprised if we might need a vc2 to solve issues that might come up immediately when we try out those newest new features. We may not need a vc2, but if we do, we shouldn't be very surprised. Gj On Wed, Jul 10, 2019 at 2:30 PM Geertjan Wielenga wrote: > I would say this is indeed the safe way to go, though we should when the > dust settles explore the direction Eric suggests to bring in the Maven > convenience builds. > > Until then, let's get the vote on the road. :-) > > Gj > > On Wed, Jul 10, 2019 at 2:26 PM Neil C Smith > wrote: > >> On Wed, 10 Jul 2019 at 12:43, Eric Barboni wrote: >> > I guess that the "new" Jenkins task do the same than the release job >> (need review to be sure)). >> >> Yes, not exactly filling me with confidence there! :-) >> >> Anyway, other build tasks (Snap, Installers, etc.) rely on the >> netbeans-release task. Ideally all the Maven stuff would too, or we >> switch everything over to the new pipeline. >> >> But, an email literally 5min before I was triggering the voting >> candidate build, and without us having used that pipeline for any of >> the betas or tested with any of the depending tasks, doesn't feel >> right. So, unless we intend to push the schedule back by at least a >> week to fit in another beta, my intention is to go ahead with a vc off >> of netbeans-release today. >> >> Then we can figure out what's missing and how to get it in place ... >> >> > AFAIK, we vote also the nbm files as conveniences libraries, so maven >> artefact are part of this concept. >> >> We don't vote on the nbms or the binaries of the IDE or platform. We >> vote on the sources. See eg. >> http://www.apache.org/legal/release-policy.html#compiled-packages The >> important thing is that all the source required to build the binary >> artefacts is in the source releases we vote on. I'm assuming this is >> the case, even if we might be missing some instructions? >> >> The PMC also has responsibility to ensure any convenience binaries are >> correctly made, signed, etc. But AFAIK we can have a sanity check >> thread about them after the release vote if necessary. >> >> Thanks and 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: Final preparation for NB 11.1 voting
I would say this is indeed the safe way to go, though we should when the dust settles explore the direction Eric suggests to bring in the Maven convenience builds. Until then, let's get the vote on the road. :-) Gj On Wed, Jul 10, 2019 at 2:26 PM Neil C Smith wrote: > On Wed, 10 Jul 2019 at 12:43, Eric Barboni wrote: > > I guess that the "new" Jenkins task do the same than the release job > (need review to be sure)). > > Yes, not exactly filling me with confidence there! :-) > > Anyway, other build tasks (Snap, Installers, etc.) rely on the > netbeans-release task. Ideally all the Maven stuff would too, or we > switch everything over to the new pipeline. > > But, an email literally 5min before I was triggering the voting > candidate build, and without us having used that pipeline for any of > the betas or tested with any of the depending tasks, doesn't feel > right. So, unless we intend to push the schedule back by at least a > week to fit in another beta, my intention is to go ahead with a vc off > of netbeans-release today. > > Then we can figure out what's missing and how to get it in place ... > > > AFAIK, we vote also the nbm files as conveniences libraries, so maven > artefact are part of this concept. > > We don't vote on the nbms or the binaries of the IDE or platform. We > vote on the sources. See eg. > http://www.apache.org/legal/release-policy.html#compiled-packages The > important thing is that all the source required to build the binary > artefacts is in the source releases we vote on. I'm assuming this is > the case, even if we might be missing some instructions? > > The PMC also has responsibility to ensure any convenience binaries are > correctly made, signed, etc. But AFAIK we can have a sanity check > thread about them after the release vote if necessary. > > Thanks and 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: Final preparation for NB 11.1 voting
On Wed, 10 Jul 2019 at 12:43, Eric Barboni wrote: > I guess that the "new" Jenkins task do the same than the release job (need > review to be sure)). Yes, not exactly filling me with confidence there! :-) Anyway, other build tasks (Snap, Installers, etc.) rely on the netbeans-release task. Ideally all the Maven stuff would too, or we switch everything over to the new pipeline. But, an email literally 5min before I was triggering the voting candidate build, and without us having used that pipeline for any of the betas or tested with any of the depending tasks, doesn't feel right. So, unless we intend to push the schedule back by at least a week to fit in another beta, my intention is to go ahead with a vc off of netbeans-release today. Then we can figure out what's missing and how to get it in place ... > AFAIK, we vote also the nbm files as conveniences libraries, so maven > artefact are part of this concept. We don't vote on the nbms or the binaries of the IDE or platform. We vote on the sources. See eg. http://www.apache.org/legal/release-policy.html#compiled-packages The important thing is that all the source required to build the binary artefacts is in the source releases we vote on. I'm assuming this is the case, even if we might be missing some instructions? The PMC also has responsibility to ensure any convenience binaries are correctly made, signed, etc. But AFAIK we can have a sanity check thread about them after the release vote if necessary. Thanks and 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: Final preparation for NB 11.1 voting
Hi, Process for release maven artefacts was done a posteriori due to the obligation to change the plugin to allow the process to reach minimal Apache standard. Documentation was aside to not slow the release process. I guess that the "new" Jenkins task do the same than the release job (need review to be sure)). It add apidoc (for sync with website) and maven artefacts. It takes information from a json file stored here https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json Maven artefact are built using the normal source as the other release artefacts. It contains nbm,Javadoc,sources,jar but it's to be populated directly on repository not on dist. Build is supposed to be independent. It trigger on commit to a release* branch or master. AFAIK, we vote also the nbm files as conveniences libraries, so maven artefact are part of this concept. Regards Eric -Message d'origine- De : Neil C Smith Envoyé : mercredi 10 juillet 2019 11:57 À : dev Objet : Re: Final preparation for NB 11.1 voting On Wed, 10 Jul 2019 at 10:36, Eric Barboni wrote: > instead of : > https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-release/ > lastSuccessfulBuild/artifact/ > > Bits should be the same but they also contains the all the maven artefacts to > avoid recalling a vote later. That could have been mentioned a little sooner! ;-) > The normal release process is here > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+R > elease+README > > To prepare maven artefacts for release > https://cwiki.apache.org/confluence/display/NETBEANS/Publishing+Apache > +NetBeans+maven+artefacts > Section> Publishing > Basically it's signing + test signing and then preparing the repository > staging at apache. Yes, I've just been editing and updating the normal release process page. Was not aware of the Maven page and as far as I can tell it's not linked in? What exactly is that Jenkins task doing differently? Is it using the output of the other build task? Are there any other sources involved? At this point, my inclination is to do the vote based on the existing task, bearing in mind we only officially vote on the sources. I'm assuming everything required to achieve the Maven artefacts will be in the source bundle? 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 - 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: Final preparation for NB 11.1 voting
Hi Neil, Would it be possible to take the bits from this place: https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release111/lastSuccessfulBuild/artifact/dist/ instead of : https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-release/lastSuccessfulBuild/artifact/ Bits should be the same but they also contains the all the maven artefacts to avoid recalling a vote later. The normal release process is here https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README To prepare maven artefacts for release https://cwiki.apache.org/confluence/display/NETBEANS/Publishing+Apache+NetBeans+maven+artefacts Section> Publishing Basically it's signing + test signing and then preparing the repository staging at apache. If not possible it would be cool if before writing the Vote thread to synchronize so I can prepare them aside. Best Regards Eric -Message d'origine- De : Geertjan Wielenga Envoyé : lundi 8 juillet 2019 15:59 À : dev Objet : Re: Final preparation for NB 11.1 voting On Mon, Jul 8, 2019 at 3:32 PM Neil C Smith wrote: > IMO with > the new release schedule we should try and address critical issues in > the non-LTS releases, but they shouldn't block non-LTS releases unless > they're a regression. Thoughts? > I agree with that a lot. Didn't see blocker issues from the two lists you provided. Gj > > Thanks and 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
AW: Website changes for NB 11.1
The download link should go to download, yes. Make no sense to go directly to a specific Version, with no link back to the overall download site. All versions are well present on the download page, so the users will see. Cheers Chris Von: Neil C Smith Gesendet: Mittwoch, 10. Juli 2019 11:03 An: dev Betreff: Website changes for NB 11.1 Hi, I'm just merging and preparing for the vote thread on NB 11.1. And while I'm waiting on things, thinking about website requirements as I know some changes are underway already. At present the Downloads link goes directly to http://netbeans.apache.org/download/nb110/nb110.html I don't think we should directly link NB 11.1 in that way. Now we have LTS and non-LTS, we need to consider how we present LTS and non-LTS to end users, and make sure links to both remain easily available. My thought is that we should make the main menu Download go (revert) to http://netbeans.apache.org/download/ and edit that page to include a short intro to release schedule and which version to choose. And move everything that isn't latest LTS and non-LTS on to sub-pages? eg something like. # Download Apache NetBeans is released four times a year. Our April release is a long-term support (LTS) release that benefits from our famous NetCAT community testing process, and will remain available and supported for a year. Our other quarterly releases provide early access to new features. ## Apache NetBeans 11 feature update 1 (NB 11.1) Latest release of the IDE, released on July XX, 2019. [Features][Download] ## Apache NetBeans 11 LTS (NB 11.0) Latest LTS version of the IDE, released on April 4, 2019. [Features][Download] ## Older releases Older Apache NetBeans releases and pre-Apache NetBeans releases can still be downloaded, but are no longer supported. [Find out more] << move all text and links to sub-page ## Daily builds and building from source All Apache NetBeans source code is freely available to build yourself, or you can download (unsupported) daily development builds. [Find out more] << move all text and links to sub-page Thoughts? 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
Website changes for NB 11.1
Hi, I'm just merging and preparing for the vote thread on NB 11.1. And while I'm waiting on things, thinking about website requirements as I know some changes are underway already. At present the Downloads link goes directly to http://netbeans.apache.org/download/nb110/nb110.html I don't think we should directly link NB 11.1 in that way. Now we have LTS and non-LTS, we need to consider how we present LTS and non-LTS to end users, and make sure links to both remain easily available. My thought is that we should make the main menu Download go (revert) to http://netbeans.apache.org/download/ and edit that page to include a short intro to release schedule and which version to choose. And move everything that isn't latest LTS and non-LTS on to sub-pages? eg something like. # Download Apache NetBeans is released four times a year. Our April release is a long-term support (LTS) release that benefits from our famous NetCAT community testing process, and will remain available and supported for a year. Our other quarterly releases provide early access to new features. ## Apache NetBeans 11 feature update 1 (NB 11.1) Latest release of the IDE, released on July XX, 2019. [Features][Download] ## Apache NetBeans 11 LTS (NB 11.0) Latest LTS version of the IDE, released on April 4, 2019. [Features][Download] ## Older releases Older Apache NetBeans releases and pre-Apache NetBeans releases can still be downloaded, but are no longer supported. [Find out more] << move all text and links to sub-page ## Daily builds and building from source All Apache NetBeans source code is freely available to build yourself, or you can download (unsupported) daily development builds. [Find out more] << move all text and links to sub-page Thoughts? 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
