Page tree
Skip to end of metadata
Go to start of metadata

Release Process

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

  1. See the generic Apache Release process –

  2. See the generic Apache Release FAQ –

  3. See the ASF policy and documentation for releases:

  4. See the necessary steps and requirements for the release distribution --

  5. And the specific amendments for Incubator releases --

Specific Steps, Details, and Examples

See: NETBEANS-1321 - Getting issue details... STATUS as a reference done for Apache NetBeans 10.0

After reading the above, some specific steps and details and examples below.

  1.  PPMC vote and tally.

  2. During incubation, IPMC vote, for example:

    Conclude and tally the vote on general@ by replying with a final [RESULT][VOTE] <subject>, which can be done after minimal 72h. Check the general@ list for examples on the format and content of such [RESULT][VOTE] emails, for example:

  3. The source distribution at

    needs to be moved (can use svn mv for that) to something like:

  4. Also, the KEYS file needed to verify netbeans distributions needs to be uploaded in the root (netbeans) dist folder there as well:

  5. Finally, the NetBeans website ( needs to provide a download link for the distribution, including (explicitly) links to:


    .e., u
    pdate the website with the release info, as that is required to make it a proper and community-visible release.

Note: If the main site is not syncing go to and click "synchronize git repositories".

Producing a Release Candidate

1. Make sure you have the Right Permissions

  1. You must be a PPMC member / Committer in Apache NetBeans
  2. You must have connected your Apache ID to Apache NetBeans GitHub via GitBox:
  3. You must be able to change the branch being used for Jenkins builds,
    i.e., see  INFRA-17082 - Getting issue details... STATUS
  4. You shall have a PGP KEY
  5. You need to have sudo access to

2. Obtaining and Preparing the Release Candidate Files

  1. Determine the version of the release,  e.g. 9.0-vc1, for voting candidate 1, later it's going to be referred as $VERSION
  2. Go to the incubator-netbeans-release job on Apache's Jenkins
  3. Build with Parameters, fill $VERSION into the VERSION input line and Build
  4. Wait the job to be finished.
  5. Download and extract the build artifacts.
  6. Check the SHA512 checksums:

    find . -name '*.sha512' -exec sha512sum --check '{}' \;
  7. Sign the Release Files

    find . -name '*.zip' -exec gpg --armor --output {}.asc --detach-sig {} \;
    # STop here if nbms are not going to be published
    find . -name '*.nbm' -exec gpg --armor --output {}.asc --detach-sig {} \;
    find . -name '*.gz' -exec gpg --armor --output {}.asc --detach-sig {} \;
  8. Verify Signatures

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

3. Verifying the Release by Checklist

  1. 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)
  2. Check the Product version:
    Start Apache NetBeans and check the Title and the Help > About Dialog
  3. Check that the splash screen has been updated.
  4. Check that the keyboard shortcut card has been updated.
  5. Check that the user directory matches the release number.
  6. 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

4. Publishing them in the staging area

Create an empty directory for the release then:

svn checkout --depth immediates apache-dist
cd apache-dist/dev && svn update --depth immediates incubator
cd incubator/netbeans && svn update --set-depth infinity

Publish to Staging Area

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

5. 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

6. Releasing a Release

The actual release can happen after the released artifacts passed the IPMC vote.

While vote candidate $VERSION is something, like: 11.0-vc3, 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 incubator
cd incubator/netbeans && svn update --set-depth infinity
svn rm incubating-netbeans-platform/* incubating-netbeans/*
# Use svn move or copy to copy the the artifact from the staging area
svn mv ../../../dev/incubator/netbeans/incubating-netbeans-platform/incubating-$VERSION incubating-netbeans-platform/incubating-$RELEASE_VERSION
svn mv ../../../dev/incubator/netbeans/incubating-netbeans/incubating-$VERSION incubating-netbeans/incubating-$RELEASE_VERSION
  1. Go to the release version directories and rename the release candidate artifacts to have the release version in their name.
  2. Adjust the name change in the checksum files (or recreate them)
  3. Doublecheck the checksums with: find . -name '*.sha512' -exec sha512sum -c {} \;
  4. Commit the changes from the apache-dist directory

7. 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:

  1. Login to NetBeans virtual machine where redirect is configured: ssh <your_apache_id>
  2. Become root using e.g. OTP MD5 online encryption: sudo /bin/bash
  3. Go to uc directory: cd /var/www/html/uc/
  4. Create new version: mkdir 9.0
  5. Go to the new directory: cd 9.0
  6. Download the new gzipped module catalog: wget
  7. Create new .htaccess file: touch .htaccess
  8. Edit the .htaccess file in vi editor and add correct redirect rule: RedirectMatch ^/uc/9.0/(.*)(\?.*)?$$1
  9. Edit the .htaccess file of the previous version and change the redirect rule: RedirectMatch ^/uc/9.0/(.*)(\?.*)?$$1
  • No labels