THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Tell dev mailing list that merge windows close:
"Just a reminder that the merge window for Apache NetBeans <INSERTVERSION> will close on <INSERTDATE>. See https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
After the merge window closes, merges to master will be limited to fixes intended for the <INSERTVERSION> release, and should be made in accordance with the bug priority guidelines - see https://cwiki.apache.org/confluence/display/NETBEANS/Bug+Priority+Guidelines
Please help review and merge any remaining pull requests that are intended for <INSERTVERSION> before that date. However, if a pull request is not quite ready for merging but should be considered, mark with NB <INSERTVERSION> (milestone or label) and we'll review in the first few days after freeze.
All other contributions should be held back until the merge window for <INSERTNEXTVERSION> opens, some time after the release of <INSERTVERSION>.
A first beta of <INSERTVERSION> should be available some time next week." - Create a branch release<version> in https://github.com/apache/netbeans. <version> looks like 113 for Apache NetBeans 11.3 full name of branch is release113
- Create a section for release<version> in https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json (after the copy paste, read carefully to match date, change version, change position.
- Check on Jenkins that item appears for release<version> in https://builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/ (all previous branches should be present).
- Create JIRA RELEASE Task by cloning previous Release Task (see an navigate to the last version before cloning Jira i.e.
)Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key NETBEANS-3116
Taming JSON to Prepare Beta or
...
Voting Candidates
https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json
...
- Beta releases should be distributed directly from the Jenkins build job - eg.
Producing a
...
Voting Candidate
1. Obtaining and Preparing the
...
Voting Candidate Files
On Apache Jenkins
- You have to set up json file milestone content.
- Go to the https://builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/
- Check that the build on release<version> and verify artefacts they should be branded with like a voting candidate. Cancel and relaunch build otherwise
- Wait for the job to be finished.
- Keep the build
...
- Go to the release version directories and rename the release voting candidate artifacts to have the release version in their name.
- Adjust the name change in the checksum files (or recreate them)
- Doublecheck the checksums with: find . -name '*.sha512' -exec sha512sum -c {} \;
- Commit the changes from the apache-dist directory
...