Page History

...

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

...

commit message could be something like: "Apache NetBeans 9.0-beta RC1."
It may be possible to skip the --username "<your-apache-username>", but it shouldn't hurt. You'll be asked for a password.

...

5. Creating tag for the release candidate:

-let CANDIDATE be "rc1", "rc2", etc. depending on which candidate this is
-determine the git revision that was used to build the release - go to the Jenkins job, and look for a long hash after "Revision:". Will be referred to as $HASH.
-prepare a commit message - could be something like "$CANDIDATE of $VERSION release", or something more descriptive. ($COMMIT)
-do the tag:
git tag -a '$VERSION-$CANDIDATE' -m "$COMMIT" $HASH
-push the tag:
git push origin '$VERSION-$CANDIDATE'
(assuming the Apache repo is "origin" for you)

...

6. Releasing a Release Candidate

To actually release a candidate, move it to the release area. In addition to the staging area, the release area needs to be checked out:

...

$ svn commit -m "<commitmessage>" dev/incubator/netbeans/release/incubator/netbeans/

...

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:

...