Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "How to create a release of EMFStore"
m (→How to create a milestone release of EMFStore) |
m (→How to create a final release of EMFStore) |
||
| Line 20: | Line 20: | ||
== How to create a final release of EMFStore == | == How to create a final release of EMFStore == | ||
To release a final version, you need to replace the version numbers manually and drop the qualifier: | To release a final version, you need to replace the version numbers manually and drop the qualifier: | ||
| − | * Increase the version milestone number globally for all MANIFEST.MF and features.xml files in all repositories, e.g. if you currently have version 0.8.9.qualifier in, your workspace you would end up with 0.9.0. | + | * Increase the version milestone number globally for all MANIFEST.MF and features.xml files in all repositories, e.g. if you currently have version ''0.8.9.qualifier'' in, your workspace you would end up with ''0.9.0''. |
| − | * Proceed with hudson and the upload of the build, but use the directory ''releases'' instead of ''milestones'' | + | * Proceed with hudson and the upload of the build as with the milestone release, but use the directory ''releases'' instead of ''milestones'' |
* Switch back the relase to the continuous integration versioning scheme by adding the qualifier to the release version. For example, if you currently have version 0.9.0 in your workspace, you would end up with 0.9.0.qualifier. | * Switch back the relase to the continuous integration versioning scheme by adding the qualifier to the release version. For example, if you currently have version 0.9.0 in your workspace, you would end up with 0.9.0.qualifier. | ||
Revision as of 10:17, 17 April 2012
Contents
How to create a milestone release of EMFStore
- In org.eclipse.emf.emfstore.site/buckminster.properties set the qualifier.replacement-property to the current milestone, e.g. M945, and deactivate the generated qualifier.replacement as shown below:
qualifier.replacement.*=M945 #qualifier.replacement.*=generator:lastModified #generator.lastModified.format='v'yyyyMMdd-HHmm
- Commit with a message such as "release 0.8.9.M945" and push your changes to the emfstore.core repository.
- Wait for the hudson job to recognize these changes (currently <= 5 minutes) and build.
- Download the artifact site.p2 as a zip-file from the build that was triggered by your commit (look for your commit message).
- Using scp (or WinScp) login with your Eclipse committer account at dev.eclipse.org, and move the content of /home/data/httpd/download.eclipse.org/emf-store/milestones/latest to /home/data/httpd/download.eclipse.org/emf-store/milestones/archive into a new subfolder named after the version, e.g. 0.8.9.M944, if it does not yet exist. You might have to download and re-upload, if the server does now allow you to move files.
- Upload the unpacked zip-file and the zip-file itself to /home/data/httpd/download.eclipse.org/emf-store/milestones/latest
- Switch back the relase to the continuous integration versioning scheme
#qualifier.replacement.*=M945 qualifier.replacement.*=generator:lastModified generator.lastModified.format='v'yyyyMMdd-HHmm
How to create a final release of EMFStore
To release a final version, you need to replace the version numbers manually and drop the qualifier:
- Increase the version milestone number globally for all MANIFEST.MF and features.xml files in all repositories, e.g. if you currently have version 0.8.9.qualifier in, your workspace you would end up with 0.9.0.
- Proceed with hudson and the upload of the build as with the milestone release, but use the directory releases instead of milestones
- Switch back the relase to the continuous integration versioning scheme by adding the qualifier to the release version. For example, if you currently have version 0.9.0 in your workspace, you would end up with 0.9.0.qualifier.
For all releases
- Commit and push.
- Add the archived the website: http://www.eclipse.org/emfstore/download.php
- Change the permissions of all directories you touched to rwxrwsr-x recursively(!) in order to allow your group to modify the content later.
- Verify that you can install EMFStore and ECP from the updated update-site by following these instructions: http://www.eclipse.org/emfstore/download.php
- Update the link to the latest JavaDoc on the documentation websites: http://eclipse.org/emfstore/documentation.php and http://eclipse.org/emfclient/documentation.php
- Make sure the changelog is updated
- Tweet about the new release, use the hashtag #emfstore :)
Unresolved issues
Currently, there is still a known bug that prevents hudson from building the repository if there are no new changes since the last build. In this case the build will fail with the message "Nothing to do". Therefore, try not to build manually but commit a dummy-change to trigger the build.
See also
Links
- Hudson job for EMFStore https://hudson.eclipse.org/hudson/job/emf-emfstore-integration/
- SCP [3]
- WinSCP [4]
- Nothing to do bugs: https://bugs.eclipse.org/bugs/show_bug.cgi?id=363607 https://bugs.eclipse.org/bugs/show_bug.cgi?id=373753
- Version Qualifiers http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.pde.doc.user%2Ftasks%2Fpde_version_qualifiers.htm