...
Code Block | ||||
---|---|---|---|---|
| ||||
##SUBJECT## [VOTE] Release Apache NetBeans <VERSION> ##BODY## This is our first voting candidate for the release of Apache NetBeans <VERSION>. Please follow the voting template at the bottom of this email, and note all requirements below for validating sources and convenience binaries before voting. Apache NetBeans <VERSION> constitutes all clusters in the Apache NetBeans Git repository, 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/<VERSION>/ They were built by the Jenkins pipeline : https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/<VERSION>/<BUILDNUMBER>/ ------------------------ We are primarily voting on : https://dist.apache.org/repos/dist/dev/netbeans/netbeans/<VERSION>/netbeans-<VERSION>-source.zip SHA512 : <INSERT SHA512> KEYS file : https://downloads.apache.org/netbeans/KEYS ------------------------ Associated with the primary source item we have, generated with the pipeline mentioned above : -- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans/<VERSION>/ Binaries associated with the source - netbeans-<VERSION>-bin.zip as well as update content under the nbms folder. -- at https://dist.apache.org/repos/dist/release/netbeans/netbeans-installers/<VERSION>/ InstallersAn installer for macosmacOS handcrafted using builds resources on a PMC member's MacosmacOS boxmachine. InstallersAn installer for windowsWindows signed by a PMC member using binaries created during the build process. InstallersPackages for linux using nbpackage Linux signed by a PMC member using binaries created with NBPackage during the build process. -- at https://dist.apache.org/repos/dist/release/netbeans/netbeans-vscode-ext/<VERSION>/ VsixThe vscodeVSCode extension signed by a PMC member using binaries created during the build process. ------------------------ Maven Artefacts The Maven artefacts for Apache NetBeans <VERSION> are ready on staging associated to this vote. https://repository.apache.org/content/repositories/<STAGEURLID>/ The version is : <RELEASEVERSION> ------------------------ Voting Requirementsrequirements Before voting +1 you are required to download the signed source code package, compile it as provided, and test the resulting executable on your own platform, along with also verifying that the package meets the requirements of the ASF policy on releases - http://www.apache.org/legal/release-policy.html#management In particular, you should (at least) follow these steps. 1. Download the artefact to be voted on and unzip it. 2. Check that the artefact does not contain any jar files (there are branding folders with the name *.jar). 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 and try running it. In addition to checking the sources, you shouldmay check the associated convenience binary zip, zipsinstallers, nbms and maven staging at the artefact links above. You are not expected to check every convenience binary. As well as checking any artefact functions correctly, you should check that it has been correctly signed by a PMC member, and that the source being voted on is sufficient to build the relevant binary. Separate votes will be held on other convenience binaries, including installers. Those will be dependent on this vote passing. This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as usual. (Please justify -1) Please mark your vote with (binding) only if you're an Apache NetBeans PMC member to help with voting admin. Only respond if you are going to vote, i.e., this is NOT a discussion thread. Apache NetBeans <VERSION> will be released if and when this vote passes. ----------------------- Voting template Please copy and paste the answer pattern below into your email. Fill the checkboxes as appropriate (eg. [X]). Replace <OS>, <JDK> and <TYPE> as appropriate. -- Answer pattern ------------------------ [ ] yes / +1 [ ] no / -1 (Pleaseplease justify -1) [ ] binding (member of PMC) My vote is based on [ ] I have built and tested the RCsource fromwith source<JDK> on platform<OS> (required) [ ] I have tested the binary zip with <JDK> on <OS> [ ] I have tested the binary RC on platform [ ] <TYPE> installer(s) with <JDK> on <OS> [ ] I have tested the Maven artefacts [ ] I have tested the VSCode extension --------------------------- Thank you to all contributors for all your hard work! Thanks again Best regards, |
Extends 72 to a bit more ? (OpenOffice is one week)
[] I have tested the binary RC on platform [ ] taken from Openoffice to get some quality check on binaries.
---
Release policy web page not clear on how to manage the conveniences artefacts of a release.
Release policy
https://www.apache.org/legal/release-policy.html
Release approval
Before casting +1 binding votes, individuals are REQUIRED to download all signed source code packages onto their own hardware, verify that they meet all requirements of ASF policy on releases as described below, validate all cryptographic signatures, compile as provided, and test the result on their own platform.
....
Artifacts
Compiled packages2
The Apache Software Foundation produces open source software. All releases are in the form of the source materials needed to make changes to the software being released.
As a convenience to users that might not have the appropriate tools to build a compiled version of the source, binary/bytecode packages MAY be distributed alongside official Apache releases. In all such cases, the binary/bytecode package MUST have the same version number as the source release and MUST only add binary/bytecode files that are the result of compiling that version of the source code release and its dependencies.
How do I upload a release ?¶
The repository directory https://dist.apache.org/repos/dist/release/<TLP name>/
is for official releases only, i.e. archives1 (+ sigs, hashes) that have been approved by the PMC. For this reason, by default only PMC members can update the dist/release directory tree.
-------------------
1: the word archives should be artefacts ( Source packages, Compiled packages) to match with what is before in the document
2: is compiled package an equivalent to conveniences binaries (would add it in the title)
Difficulty I encounter understanding the workflow on approval
the release vote call is not described enough to me. If RM is showing the dist/dev/<TLP name>/V1 as voting resources nothing prevent additionnal binaries sources to be put during the vote.
the release approval is not clear what to do with compiled package, PMC member may not have access to requiered platform. What to do if we want some quality