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 "LDT/Developer Area/Development"
(→Update sites organization) |
|||
Line 30: | Line 30: | ||
All the old releases could be found in /home/data/httpd/archive.eclipse.org/koneki/releases. (with the same structure) | All the old releases could be found in /home/data/httpd/archive.eclipse.org/koneki/releases. (with the same structure) | ||
+ | |||
+ | = Delivery Process = | ||
+ | All the path in this section are relative to <tt>/home/data/httpd/download.eclipse.org/koneki</tt> on <tt>build.eclipse.org</tt> | ||
+ | |||
+ | === Maintenance version : === | ||
+ | *"Commit freeze" on all maintenance branches. | ||
+ | *Be sure the last version build corresponds to the last commit wanted. | ||
+ | *Test the last nightly-maintenance build. | ||
+ | If tests are ok: | ||
+ | *Copy all directories from <tt>nightly-maintenance/</tt> to <tt>releases/stables/${NUM.VERSION}</tt>. | ||
+ | *Check the files permissions. | ||
+ | *Tag the last commit of the maintance branches. | ||
+ | *Increment version to the next maintenance version then commit it. | ||
+ | |||
+ | === Milestones version : === | ||
+ | *"Commit freeze" on all master branches. | ||
+ | *Be sure the last version build corresponds to the last commit wanted. | ||
+ | *Test the last nightly build. | ||
+ | If tests are ok: | ||
+ | *Copy all directories from <tt>nightly</tt> to <tt>releases/milestones/${MILESTONES.VERSION}</tt>. | ||
+ | *Check the files permissions. | ||
+ | *Tag the last commit of the master branches. | ||
+ | |||
+ | === Majeur version : === | ||
+ | *Test the milestones version which is the releases candidate. | ||
+ | If tests are ok : | ||
+ | *Copy all the directories from <tt>releases/stable/${NUM.VERSION}</tt> to <tt>/home/data/httpd/archive.eclipse.org/koneki/releases/${NUM.VERSION}</tt> | ||
+ | *Delete all directories in <tt>releases/stable/${NUM.VERSION}</tt> | ||
+ | *Copy all directories from <tt>releases/milestones/${MILESTONES.VERSION}</tt> in <tt>releases/stable/${NUM.VERSION}</tt> | ||
+ | *Delete all directories in <tt>releases/milestones/${MILESTONES.VERSION}</tt> | ||
+ | *Check the files permissions. | ||
+ | *Tag the master branches. | ||
+ | *Create maintenance branches. | ||
+ | *Increment version on master branches then commit it. | ||
+ | *Increment version to the next maintenance version then commit it. | ||
+ | *Change hudson configuration of maintenance builds to build the new one. | ||
+ | |||
+ | === Simultaneous Release : === | ||
+ | * To be Completed | ||
+ | |||
+ | === Increment version Process : === | ||
+ | * Increment feature version (pom.xml) | ||
+ | * Increment product feature version (pom.xml) | ||
+ | * Increment product version and its dependencies version | ||
+ | * Increment feature version includes in category.xml | ||
+ | |||
+ | === Simultaneous Release migration : === | ||
+ | *Update target platform (.target) | ||
+ | *Add the new plaform profile in root pom.xml | ||
+ | *Change the default repo use to build in root pom.xml (<eclipse-site> property) |
Revision as of 12:38, 6 July 2012
Contents
Git repositories
Koneki source code is available on the Git repositories of the Eclipse Foundation. There are several repositories:
org.eclipse.koneki.commons.git | Contains plug-ins that aim at being re-used by other Koneki projects (generic UI components, helpers, ...) |
org.eclipse.koneki.ldt.git | Contains the Lua Development Tools source code |
org.eclipse.koneki.protocols.git | Contains different sub-projects providing the core components enabling protocols (OMA-DM, ...) manipulation in the tools |
org.eclipse.koneki.simulators.git | Contains different sub-projects providing the components enabling protocols (OMA-DM, ...) simulation in the tools |
Update sites organization
The active Hudson jobs perform the continuous integration of Koneki projects and deploy signed p2 repos to the nightly update sites.
There are 2 kind of nightly updates sites (repositories) :
- nightly:/home/data/httpd/download.eclipse.org/koneki/updates-nightly, which is an aggregating of the last successful builds of master branch for each Koneki projects.
- nightly-maintenance:/home/data/httpd/download.eclipse.org/koneki/updates-nightly-maintenance, which is the same one but for the maintenance branch.
All the last releases are store in /home/data/httpd/download.eclipse.org/koneki/releases repository which is composed of :
- stable: /home/data/httpd/download.eclipse.org/koneki/releases/stable which contains all the last stable releases.
- milestones: /home/data/httpd/download.eclipse.org/koneki/releases/milestones which contains all the last milestones.
All the old releases could be found in /home/data/httpd/archive.eclipse.org/koneki/releases. (with the same structure)
Delivery Process
All the path in this section are relative to /home/data/httpd/download.eclipse.org/koneki on build.eclipse.org
Maintenance version :
- "Commit freeze" on all maintenance branches.
- Be sure the last version build corresponds to the last commit wanted.
- Test the last nightly-maintenance build.
If tests are ok:
- Copy all directories from nightly-maintenance/ to releases/stables/${NUM.VERSION}.
- Check the files permissions.
- Tag the last commit of the maintance branches.
- Increment version to the next maintenance version then commit it.
Milestones version :
- "Commit freeze" on all master branches.
- Be sure the last version build corresponds to the last commit wanted.
- Test the last nightly build.
If tests are ok:
- Copy all directories from nightly to releases/milestones/${MILESTONES.VERSION}.
- Check the files permissions.
- Tag the last commit of the master branches.
Majeur version :
- Test the milestones version which is the releases candidate.
If tests are ok :
- Copy all the directories from releases/stable/${NUM.VERSION} to /home/data/httpd/archive.eclipse.org/koneki/releases/${NUM.VERSION}
- Delete all directories in releases/stable/${NUM.VERSION}
- Copy all directories from releases/milestones/${MILESTONES.VERSION} in releases/stable/${NUM.VERSION}
- Delete all directories in releases/milestones/${MILESTONES.VERSION}
- Check the files permissions.
- Tag the master branches.
- Create maintenance branches.
- Increment version on master branches then commit it.
- Increment version to the next maintenance version then commit it.
- Change hudson configuration of maintenance builds to build the new one.
Simultaneous Release :
- To be Completed
Increment version Process :
- Increment feature version (pom.xml)
- Increment product feature version (pom.xml)
- Increment product version and its dependencies version
- Increment feature version includes in category.xml
Simultaneous Release migration :
- Update target platform (.target)
- Add the new plaform profile in root pom.xml
- Change the default repo use to build in root pom.xml (<eclipse-site> property)