| Summary: | Set-up release branch and infrastructure | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Florian Thienel <florian> |
| Component: | Mylyn | Assignee: | David Carver <d_a_carver> |
| Status: | CLOSED FIXED | QA Contact: | David Williams <david_williams> |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipse |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 323335 | ||
| Bug Blocks: | |||
|
Description
Florian Thienel
I've setup the branch, vex-release. It was branched from the current vex-dev. When you are ready to have code be built for a release you can do one of several things: 1. Merge from vex-dev into the vex-release branch. This will take everything currently in vex-dev and put it into vex-release. 2. Cherry Pick commits and merge them into vex-release. The preferred way is to do a merge from vex-dev into vex-release. In order to get the automated build setup I need to have a new job created. This depends on bug 323335 being completed. This work has been done. Closing resolved bugs. Moved to Mylyn Docs Vex. |