THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Code Block | ||||
---|---|---|---|---|
| ||||
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. Do the vote on the dev mailing list.
5. Creating tag for the Release:
We Assuming the vote succeeded, we should tag the beta and the release, after voting, but not the voting candidates.
...
Code Block | ||||
---|---|---|---|---|
| ||||
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 |
...
6. Releasing a Release
Vote Assuming the vote sVote shoud be done to do the release step.
...
- Go to the release version directories and rename the voting 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
...
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:
...