...

1. You must be a PMC member / Committer in Apache NetBeans
2. You must have connected your Apache ID to Apache NetBeans GitHub via GitBox: https://gitbox.apache.org
3. You must have access to https://github.com/apache/netbeans and https://github.com/apache/netbeans-jenkins-lib/.
4. You must be able to connect to Apache CI Jenkins instance builds,
   i.e., see 

   Jira
   server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key INFRA-17082

5. You shall have a PGP KEY
6. You need to have sudo access to netbeans-vm.apache.org

Preparing code base

1. 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."

1. Create a branch release<version> in the https://github.com/apache/netbeans. <version> looks like 113 for Apache NetBeans 11.3 full name of branch is release113
2. 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

Producing a Beta

1. Obtaining and Preparing the Beta files

...