-
Notifications
You must be signed in to change notification settings - Fork 2
Release Process
reprogrammer edited this page Nov 1, 2014
·
5 revisions
- Remove the following folders and files from the
*.updatesite
plug-in.features/
plugins/
artifacts.jar
content.jar
logs.zip
- Open
*.updatesite/site.xml
in Eclipse. - Remove all the features listed in
site.xml
but not any categories. - Select the the category in the
Site Map
. Then, press theAdd Feature...
button and select the feature plug-in from the popped up dialog. - Press the button
Build
.
- Install the new release of from the local file system into fresh instances of Eclipse to make sure that it installs successfully.
- Copy the contents of the directory
*.updatesite
intopublic_html/updates
of the machine hosting the update site. - Repeat the first step for the remote update site.
-
Be careful not to delete any
build.xml
files. For some reason, the build script of the update site sometimes deletes some of the other build scripts. -
Commit the changes to the update site and change log. Use a commit message of the following form
Released v<x>.<y>.<z>.<qualifier> This commit belongs to issue #<release-issue>.
In the above message, <x>
, <y>
, <z>
and <qualifier>
are parts of the version of the generated feature, and <release-issue>
is the number of the issue devoted to this particular release.
-
Push the commit to the remote repository.
-
Tag the commit containing the new release using the following command.
git tag v<x>.<y>.<z>.<qualifier> <commit-sha>
Push the created tag to the remote repository using the following command.
git push --tags
- List a summary of the fixed issues on the release page of the github repository.
- Push the update site to the release git repository and tag it similarly.