Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "LDT/Developer Area/Development"

< LDT
(Update sites organization)
(APITools)
Line 76: Line 76:
  
 
= APITools =
 
= APITools =
All the org.eclipse.koneki.ldt* plugins are checked against APITools to ensure the consistence of LDT public API.
+
All the org.eclipse.ldt* plugins are checked against APITools to ensure the consistence of LDT public API.
 
When checkouting the code in an eclipse workspace, you must set an API baseline used by APITool check your development against, in our case, the API baseline have to be the last stable version of the LDT standalone product. To work on the LDT remote feature, you have to install the last stable version of remote feature in the product used as reference.
 
When checkouting the code in an eclipse workspace, you must set an API baseline used by APITool check your development against, in our case, the API baseline have to be the last stable version of the LDT standalone product. To work on the LDT remote feature, you have to install the last stable version of remote feature in the product used as reference.
  

Revision as of 10:51, 20 August 2014

Git repositories

LDTs source code is available on the Git repositories of the Eclipse Foundation. There are several repositories:

http://git.eclipse.org/c/ldt/org.eclipse.ldt.git/ Lua Development Tools source code
http://git.eclipse.org/c/ldt/org.eclipse.metalua.git/ MetaLua source code

Bugzilla severity and priority

Severity Definition
blocker A problem preventing a function from being used, no work around, blocking progress on multiple fronts
critical A problem preventing a function from being used, no work around
major A problem preventing a function from being used, but a work around is possible
normal Not used in LDT(Default value in Bugzilla, so can mean a bug has not been sorted)
minor A problem not affecting the actual function, but the behavior is not natural
trivial A problem not affecting the actual function, a typo would be an example
enhancement A new feature or improvement of an existing one


Priority Definition
P1 Must be fixed within the current milestone.
P2 Must be fixed before the release.
P3 Would be fixed before release, if possible.
P4 Would be probably fixed someday.
P5 Not important to our long-term plans.

Update sites organization

The active Hudson jobs perform the continuous integration of LDT projects and deploy signed p2 repos to the nightly update sites.

TODO Switch to LDT update sites There are 2 kind of nightly updates sites (repositories) :

  • nightly: /home/data/httpd/download.eclipse.org/ldt/updates-nightly, which is a composite repo of the last successful builds of the 'master' branch of each Koneki projects.
  • nightly-maintenance: /home/data/httpd/download.eclipse.org/ldt/updates-nightly-maintenance, which is the same one but for the active maintenance branch.

All the last releases are stored in /home/data/httpd/download.eclipse.org/ldt/releases repository which is composed of :

  • stable: /home/data/httpd/download.eclipse.org/ldt/releases/stable which contains all the last stable releases.
  • milestones: /home/data/httpd/download.eclipse.org/ldt/releases/milestones which contains all the last milestones.

Previous releases can be found in at /home/data/httpd/archive.eclipse.org/ldt/releases. (with the same structure)

APITools

All the org.eclipse.ldt* plugins are checked against APITools to ensure the consistence of LDT public API. When checkouting the code in an eclipse workspace, you must set an API baseline used by APITool check your development against, in our case, the API baseline have to be the last stable version of the LDT standalone product. To work on the LDT remote feature, you have to install the last stable version of remote feature in the product used as reference.

The API baseline can be set in the eclipse preference under the menu "Plug-in development/Api baseline".

To go further with Api Tool, see the related wiki: http://wiki.eclipse.org/PDE/API_Tools.

Delivery Process

TODO Switch to LDT paths All the path in this section are relative to /home/data/httpd/download.eclipse.org/koneki on build.eclipse.org

Maintenance versions delivery

Maintenance Milestone

  • "Commit freeze" on all maintenance branches.
  • Be sure the last version build corresponds to the last commit wanted.
  • Test the last nightly-maintenance build.
  • execute script releases:

python erclt.py mm -mv 1.0.1RC1 which do :

 Deliver a new milestone repo.
 Deliver new milestone products.
  • Tag the last commit of the maintenance branches.

Maintenance Minor versions

  • Test the milestones version which is the releases candidate.

If tests are ok :

  • execute script releases:

python erclt.py ms -mv 1.0.1RC1 -sv 1.0.1

which do :

 Deliver stable repo.
 Archive milestones repo.
 Deliver stable products.
 Archive milestones products.

If script execution is ok:

  • Tag the maintenance branches.
  • Increment version to the next maintenance version then commit it.

Stables versions delivery

Milestones versions

  • "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:

  • execute script releases:

python erclt.py m -mv 0.9RC2

which do :

 Deliver repo.
 Deliver new products.
 

If script execution is ok:

  • Tag the last commit of the master branches.

Major versions

  • Test the milestones version which is the releases candidate.

If tests are ok :

  • execute script releases:

python erclt.py s -mv 0.9RC2 -sv 0.9

which do :

 Archive stable repo.
 Deliver stable repo.
 Archive milestones repo.
 Archive stable products.
 Deliver stable products.
 Archive milestones products.

If script execution is ok:

  • 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

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)

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
  • Increment debugger version includes in init.lua
  • Increment documentation version (org.eclipse.koneki.ldt.doc.user/build-help.xml, org/eclipse/koneki/ldt/debug/ui/DocumentationLinksConstants.java and plugin.xml)
  • deploy User guide (wiki)
  • Update Koneki website links to the wiki user guide.

Enable Statistic

Done automatically now by the release script.

  • Move in repo
    • cd releases/stable/${NUM.VERSION}/${repo}
  • Unzip artifacts.jar
    • unzip artifacts.jar
  • Modify artifacts.xml (add p2.statsURI and download.stats property)
<properties size="3">
    <property name="p2.timestamp" value="1339531652273"/>
    <property name="p2.compressed" value="true"/>
    <property name="p2.statsURI" value="http://download.eclipse.org/stats/ldt"/>

....

<artifact classifier="org.eclipse.update.feature" id="org.eclipse.koneki.ldt" version="0.8.0.201206122001">
      <properties size="6">
        <property name="artifact.size" value="20464"/>
        <property name="download.size" value="20464"/>
        <property name="maven-groupId" value="org.eclipse.koneki.ldt-features"/>
        <property name="maven-artifactId" value="org.eclipse.koneki.ldt"/>
        <property name="maven-version" value="0.8.0-SNAPSHOT"/>
        <property name="download.contentType" value="application/zip"/>
        <property name='download.stats' value='org.eclipse.koneki.ldt_0.8.0.201206122001'/>
      </properties>
  • Zip it
    • zip artifacts.jar artifacts.xml
  • remove artifacts.xml
    • rm artifacts.xml

(see : http://wiki.eclipse.org/Equinox_p2_download_stats)

Back to the top