Overview

Every PMC member should read the below docs at least once, several times, because the Apache NetBeans PMC members are responsible to verify and ensure releases are done in compliance with these rules:

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 INFRA-17082 - Getting issue details... STATUS .
You must have a PGP KEY (http://www.apache.org/dev/release-distribution.html#sigs-and-sums) 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 the Code Base and Jenkins TLP Job

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/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. NETBEANS-3116 - Getting issue details... STATUS )

Taming JSON to Prepare Beta or Release Candidates

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

If nothing is set in the section, it will release a dev version of current branch. 11.3-dev.

Preparing for beta:

Milestone section key are commit hash. If you want a commit hash to form a beta1 you need to add milestone entry (do not forget position):

"<commit hash>":{"version": "beta1","position": "1"}

Branding will contains beta information

Preparing for voting candidate:

Milestone section key are commit hash. If you want a commit hash to form a beta1 you need to add milestone entry (do not forget position):

"<commit hash>":{"vote": "1","position": "2"}

Branding will contains release information

Producing a Beta

1. Obtaining and Preparing the Beta files

On Apache Jenkins

You have to set up json file milestone content.
Go to https://ci-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 beta in their name. Cancel and relaunch build otherwise
Wait for the job to be finished.
Keep the build

On your computer

Download and extract the build artifacts.

Check the SHA512 checksums:

find . -name '*.sha512' -execdir sha512sum --check '{}' \;
#alternative
for z in $(find . -name '*.sha512'); do cd $(dirname $z); sha512sum ./$(basename $z) --check --quiet; cd - >/dev/null; done

On the NetBeans virtual machine

Prepare apidoc folder

sudo su -
cd /var/www/bits.netbeans.org
mkdir 11.3

2. Distributing Beta via mailing lists

Beta releases should be distributed directly from the Jenkins build job - eg.

Producing a Release Candidate

1. Obtaining and Preparing the Release Candidate Files

On Apache Jenkins

You have to set up json file milestone content.
Go to the https://builds.apache.org/view/M-R/view/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

On your computer

Download and extract the build artifacts.

Check the SHA512 checksums:

find . -name '*.sha512' -execdir sha512sum --check '{}' \;
#alternative
for z in $(find . -name '*.sha512'); do cd $(dirname $z); sha512sum ./$(basename $z) --check --quiet; cd - >/dev/null; done

NB. check (and create if necessary) .sha512 files for nbm/updates.xml and nbm/tasks.jar

Sign the Release Files

export GPG_EMAIL="YOU@apache.org"
find . -name '*.zip' -exec gpg -u $GPG_EMAIL --armor --output {}.asc --detach-sign {} \;
# Stop here if nbms are not going to be published
find . -name '*.nbm' -exec gpg -u $GPG_EMAIL --armor --output {}.asc --detach-sign {} \;
find . -name '*.gz' -exec gpg -u $GPG_EMAIL --armor --output {}.asc --detach-sign {} \;
# nbm licenses
find . -name '*.license' -exec gpg -u $GPG_EMAIL --armor --output {}.asc --detach-sign {} \;
# nbm/updates.xml and nbm/tasks.jar
find . -name '*.jar' -exec gpg -u $GPG_EMAIL --armor --output {}.asc --detach-sign {} \;
find . -name '*.xml' -exec gpg -u $GPG_EMAIL --armor --output {}.asc --detach-sign {} \;

Verify Signatures

find . -name '*.asc' -exec gpg --verify {} \;

2. Verifying the Release by Checklist

Go through the Apache Incubator Release Checklist
(whether a project is in the Apache Incubator or not, these items need to be checked since they're important for all Apache releases)
Check the Product version:
Start Apache NetBeans and check the Title and the Help > About Dialog
Check that the splash screen has been updated.
Check that the user directory matches the release number.
Check GPL License is present and need to be accepted:
1. Start NetBeans with an empty User directory
2. Open a Java SE project: installing nb-javac shall present GPL
3. Start NetBeans with an empty User directory
4. Create a new PHP project: installing Graal JS shall present GPL

3. Publishing them in the staging area

Create an empty directory for the release then:

svn checkout --depth immediates https://dist.apache.org/repos/dist/ apache-dist
cd apache-dist/dev && svn update --depth immediates netbeans
cd netbeans && svn update --set-depth infinity

Publish to Staging Area

svn rm netbeans-platform/* netbeans/*
mkdir netbeans-platform/$VERSION, netbeans/$VERSION
# Copy the netbeans-platform and netbeans artifacts with checksums and signatures in place
svn add netbeans-platform/* netbeans/*
svn --username "<your-apache-username>" commit -m "Apache NetBeans $VERSION."

4. Creating tag for the Release:

Go to your local git repository clone. Collect the git commit hash from the release build job.

git fetch --all
git tag -a $VERSION -m "Apache NetBeans $VERSION." $HASH
git push origin $VERSION
# or if you've disabled upstream push
git push https://github.com/apache/netbeans.git $VERSION

5. Releasing a Release

Vote shoud be done to do the release step.

While vote candidate $VERSION is something, like: 11.0-vc1, the actual $RELEASE_VERSION is: 11.0

# Go to the apache-dist directory which had been previously checked out in Step 4.
cd release && svn update --depth immediates netbeans
cd netbeans && svn update --set-depth infinity
# svn rm netbeans-platform/* netbeans/* # need to keep LTS and latest non-LTS ?
# Use svn move or copy to copy the the artifact from the staging area
svn mv ../../dev/netbeans/netbeans-platform/$VERSION netbeans-platform/$RELEASE_VERSION
svn mv ../../dev/netbeans/netbeans/$VERSION netbeans/$RELEASE_VERSION

Go to the release version directories and rename the release 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

6. Updating redirect for NetBeans Distribution Update Center

Once release is synchronized across all download mirrors it is necessary to update redirect for release modules to final location:

Login to NetBeans virtual machine where redirect is configured: ssh <your_apache_id>@netbeans-vm.apache.org

Become root using e.g. OTP MD5 online encryption: sudo /bin/bash

sudo /bin/bash
cd /var/www/html/uc/
mkdir 11.1
cd 11.1/
curl https://dist.apache.org/repos/dist/release/netbeans/netbeans/11.1/nbms/updates.xml.gz -o updates.xml.gz
echo ' RedirectMatch ^/uc/11.1/(.*)(\?.*)?$ http://www.apache.org/dyn/closer.lua?action=download&filename=netbeans/netbeans/11.1/nbms/$1' > .htaccess
# Update the previous version UC - need to keep LTS and non-LTS! 
cd ../10.0/
echo 'RedirectMatch ^/uc/10.0/(.*)(\?.*)?$ https://archive.apache.org/dist/incubator/netbeans/incubating-netbeans/incubating-10.0/nbms/$1' > .htaccess
vim updates.xml.gz

Modify updates.xml.gz file of previous release to contain: (how to handle LTS vs non-LTS?)
```
<notification url="https://netbeans.apache.org/download/index.html">Apache NetBeans IDE 11.0 is available!</notification>
```
element in its <module_updates> root element.

NOTE: For accessing the NetBeans Virtual VM please see netbeans-vm.apache.org

Specific Steps, Details, and Examples

See these for reference:

NetBeans 12.3 tasks: NETBEANSINFRA-238 - Getting issue details... STATUS

NetBeans 12.1 tasks: NETBEANSINFRA-212 - Getting issue details... STATUS

NetBeans 10 tasks: NETBEANS-1321 - Getting issue details... STATUS

Space shortcuts

Page tree

Overview

Requirements

Preparing the Code Base and Jenkins TLP Job

Taming JSON to Prepare Beta or Release Candidates

Preparing for beta:

Preparing for voting candidate:

Producing a Beta

1. Obtaining and Preparing the Beta files

2. Distributing Beta via mailing lists

Producing a Release Candidate

1. Obtaining and Preparing the Release Candidate Files

2. Verifying the Release by Checklist

3. Publishing them in the staging area

Create an empty directory for the release then:

Publish to Staging Area

4. Creating tag for the Release:

5. Releasing a Release

6. Updating redirect for NetBeans Distribution Update Center

Specific Steps, Details, and Examples

Space shortcuts

Page tree

Apache NetBeans Release README

Overview

Requirements

Preparing the Code Base and Jenkins TLP Job

Taming JSON to Prepare Beta or Release Candidates

Preparing for beta:

Preparing for voting candidate:

Producing a Beta

1. Obtaining and Preparing the Beta files

2. Distributing Beta via mailing lists

Producing a Release Candidate

1. Obtaining and Preparing the Release Candidate Files

2. Verifying the Release by Checklist

3. Publishing them in the staging area

Create an empty directory for the release then:

Publish to Staging Area

4. Creating tag for the Release:

5. Releasing a Release

6. Updating redirect for NetBeans Distribution Update Center

Specific Steps, Details, and Examples