See the generic Apache Release process – http://www.apache.org/dev/release-publishing.html.
See the generic Apache Release FAQ – http://www.apache.org/legal/release-policy.html.
See the ASF policy and documentation for releases: http://www.apache.org/dev/#releases.
See the necessary steps and requirements for the release distribution -- http://www.apache.org/dev/release-distribution.html.

Requirements

You must be a PMC member / Committer in Apache NetBeans
You must have connected your Apache ID to Apache NetBeans GitHub via GitBox: https://gitbox.apache.org
You must have access to https://github.com/apache/netbeans and https://github.com/apache/netbeans-jenkins-lib/.
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
You must have a PGP KEY for which the public key must be here: https://dist.apache.org/repos/dist/release/netbeans/KEYS
You need to have sudo access to netbeans-vm.apache.org

Preparing

...

...

...

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/view/M-R/view/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
)

...

...

For each release section you will have milestones section. This section will help branding a special Apache NetBeans milestone.

...