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 "Mylyn/Release Howto"
< Mylyn
(→Before the Release) |
|||
| Line 21: | Line 21: | ||
* Tag the release as R_x_y_z and R_x_y_y_e_3_3 | * Tag the release as R_x_y_z and R_x_y_y_e_3_3 | ||
---- | ---- | ||
| + | * Prepare the build environment | ||
| + | ssh [user]@build.eclipse.org | ||
| + | cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/tools co org.eclipse.mylyn/org.eclipse.mylyn.releng | ||
| + | cd org.eclipse.mylyn/org.eclipse.mylyn.releng | ||
| + | # adjust settings in local.properties as necessary | ||
| + | |||
* Build the release: | * Build the release: | ||
| − | + | ant weekly # weekly builds | |
| − | + | ant galileo # signed builds that are published to the weekly and Galileo update site | |
| − | + | * If signing times out: | |
| − | + | ant sign | |
| − | + | ant -Dtodir=galileo promote | |
| − | + | * Update mylyn.build file for Galileo builds | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | * | + | |
| − | + | ||
| − | - | + | |
| − | * | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
---- | ---- | ||
''Major releases only'' | ''Major releases only'' | ||
| Line 52: | Line 43: | ||
* Create a new section in the download archive | * Create a new section in the download archive | ||
* Create a new section in the New & Noteworthy | * Create a new section in the New & Noteworthy | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==== When the build has propagated to mirrors ==== | ==== When the build has propagated to mirrors ==== | ||
Revision as of 00:39, 11 March 2009
Contents
Before the Release
- Run AllTests
- Update the user guide from the wiki
- Run org.eclipse.mylyn.help.ui/build-helper.xml as an Ant Build (ensure org.eclipse.mylyn.wikitext* is checked out into your workspace)
- Review the user guide and commit changes to CVS
- Backport changes to the 3.3 branch
- Update 3.3 workspace to the latest
- Select branched plug-ins
- Team > Merge
- end tag: HEAD
- start tag: Merged_e_3_3_m_3_x
- select Preview the merge in the synchronize perspective
- Merge changes and resolve conflicts
- Tag branched plug-ins in 3.4 workspace (i.e. cvs head) with Merged_e_3_3_m_3_x
- select Move tag if already exists
The Release
Major releases only
- Tag the release as R_x_y_z and R_x_y_y_e_3_3
- Prepare the build environment
ssh [user]@build.eclipse.org cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/tools co org.eclipse.mylyn/org.eclipse.mylyn.releng cd org.eclipse.mylyn/org.eclipse.mylyn.releng # adjust settings in local.properties as necessary
- Build the release:
ant weekly # weekly builds ant galileo # signed builds that are published to the weekly and Galileo update site
- If signing times out:
ant sign ant -Dtodir=galileo promote
- Update mylyn.build file for Galileo builds
Major releases only
- Move the release from the weekly site to the main update site:
ssh [username]@build.eclipse.org cd /shared/tools/mylyn/weekly ./promote.sh [major] [build]
- Update the version number on the download page
- Create a new section in the download archive
- Create a new section in the New & Noteworthy
When the build has propagated to mirrors
Major releases only
- Add the mirror attribute to all site.xml files and regenerate meta-data with correct update site identifiers:
ssh [username]@build.eclipse.org cd /shared/tools/mylyn/weekly ./add-mirrors.sh ./generate-p2-metadata.sh
- Check that the site.xml files have the following URL set:
mirrorsURL="http://www.eclipse.org/downloads/download.php?file=/tools/mylyn/update/[location]/site.xml&protocol=http&format=xml"
After the release
Major releases only
- For head and e3.3 branch: Replace version numbers in all MANIFEST.MF and feature.xml files, e.g. 2.3.0.qualifier -> 2.3.1.qualifier and 2.3.0.mylynQualifier -> 2.3.1.mylynQualifier
- Make sure changes are applied to the 3.3 branch as well as the 3.4 branch