Bugzilla severity and priority

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 Koneki (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 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 a composite repo of the last successful builds of the 'master' branch of each Koneki projects.

nightly-maintenance: /home/data/httpd/download.eclipse.org/koneki/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/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 can be found in /home/data/httpd/archive.eclipse.org/koneki/releases. (with the same structure)

APITools

All the org.eclipse.koneki.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".