Re: [VOTE] [RELEASE] Apache OFBiz 18.12.12 - third attempt
+1 Jacopo, please could you try tagging the commit you used for the release sources as 'release18.12.12'. That should then trigger the building of a non-snapshot docker container image. Building of docker container images is not an official release channel for OFBiz, so no need to publicise that any such images exist. But it would be good to test that images are getting built by GitHub actions in response to tagging releases in case we want to highlight the availability of docker images in future. If this vote fails, we should be able to 'move' the release tag for the next release attempt, prompting the build of the next non-snapshot docker image. Thanks, Dan. On Tue, 13 Feb 2024 at 08:35, Jacopo Cappellato wrote: > This is the vote thread, third attempt, to publish "Apache OFBiz > 18.12.12", twelfth > release from the release18.12 branch. > > The release files can be downloaded from here: > https://dist.apache.org/repos/dist/dev/ofbiz/ > and are: > * apache-ofbiz-18.12.12.zip > * KEYS: text file with keys > * apache-ofbiz-18.12.12.zip.asc: the detached signature file > * apache-ofbiz-18.12.12.zip.sha512: checksum file > > Please download and test the zip file and its signatures (for > instructions on testing the signatures see > http://www.apache.org/info/verification.html). > > Vote: > [ +1] release as Apache OFBiz 18.12.12 > [ -1] do not release > > This vote is open for at least 5 days. > > For more details about this process please refer to > http://www.apache.org/foundation/voting.html > -- Daniel Watford
Re: Do we want to upgrade node.js ?
OFBIZ-12901 created to address the Node.js upgrade: https://issues.apache.org/jira/browse/OFBIZ-12901 On Thu, 15 Feb 2024 at 17:50, Daniel Watford wrote: > Hi Jacques, > > Upgrading sounds a good idea to me. > > We only use Node.js as part of our build process, so we should catch any > problems/incompatibilities quite easily. > > On Thu, 15 Feb 2024 at 11:42, Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > >> Le 15/02/2024 à 10:08, Jacques Le Roux a écrit : >> > Hi, >> > >> > After installing Scorecard as a GH actions (OFBIZ-12899), we got a >> suggestion to upgrade node.js from 16 to 20 version. >> > >> > Do we want to do that? >> > >> > TIA >> > >> > Jacques >> >> node.js 16 is EOL: >> https://github.com/nodejs/Release/#end-of-life-releases >> >> > > -- > Daniel Watford > -- Daniel Watford
Re: Do we want to upgrade node.js ?
Hi Jacques, Upgrading sounds a good idea to me. We only use Node.js as part of our build process, so we should catch any problems/incompatibilities quite easily. On Thu, 15 Feb 2024 at 11:42, Jacques Le Roux wrote: > Le 15/02/2024 à 10:08, Jacques Le Roux a écrit : > > Hi, > > > > After installing Scorecard as a GH actions (OFBIZ-12899), we got a > suggestion to upgrade node.js from 16 to 20 version. > > > > Do we want to do that? > > > > TIA > > > > Jacques > > node.js 16 is EOL: https://github.com/nodejs/Release/#end-of-life-releases > > -- Daniel Watford
Re: Do we want to upgrade node.js ?
Le 15/02/2024 à 10:08, Jacques Le Roux a écrit : Hi, After installing Scorecard as a GH actions (OFBIZ-12899), we got a suggestion to upgrade node.js from 16 to 20 version. Do we want to do that? TIA Jacques node.js 16 is EOL: https://github.com/nodejs/Release/#end-of-life-releases
Do we want to upgrade node.js ?
Hi, After installing Scorecard as a GH actions (OFBIZ-12899), we got a suggestion to upgrade node.js from 16 to 20 version. Do we want to do that? TIA Jacques
