EMT

The EMT (Engineering Management Team) manages short term release priorities for the gLlite middleware distribution. This involves managing updates, scheduling changes and defining developer priorities. There are representatives from JRA1, SA1 and SA3. Longer term objectives are handled by the TCG and filter down to the EMT for release planning.

Current Status

We currently operate in a mode of continuous updates to the production releases gLite3.0 and gLite 3.1. We follow a weekly cycle of releases to PPS. Patches typically remain on PPS for a couple of weeks before being transferred to production.

Integration and build

Patches which have been built and are ready for certification (but not yet taken) can be found here

Patches ready for certification

Certification

The following savannah search shows which patches are currently in certification.

Patches in certification

More information on certification is available here

Cert wiki

Pre-production

PPS currently has the following patches

Patches in PPS

Unreleased patch summary

The full list of currently unreleased patches can be found here - priority is colour coded

Unreleased patches

EMT Meeting minutes

The EMT normally meets twice a week, on Monday and Wednesday. The timetable and agendas are available through Indico.

The Minutes are linked from the relevant agenda and are stored on EDMS.

Mailing List

The EMT mailing list is fairly high volume, and frequently continues discussions from the meetings.

project-eu-egee-middleware-emt@cernNOSPAMPLEASE.ch

You can subscribe via simba.

Bug Tracking

Certain bugs are judged as being of sufficient severity to be tracked by the glite release coordination team.

BugTracker

This status is independent of the severity defined for the bug, although a correlation between 'critical' bugs and those tracked by the EMT clearly exists.

A tracked bug

• Is a developer priority
• Can be explicitly cited in cluster manager's weekly reports
• Can originate from a request via GDB or TMB
• Will result in a priority patch (if no workaround is available)

Patch submission

Patches are the mechanism for getting a software change deployed. For services that are in development no patches are required.

gLite 3.0.2

The term gLite 3.0.2 is used to refer to the second large set of updates released after the deployment of gLite 3.0.0. We now operate a policy of continuous updates of services and do not make releases such as this.

It was released on 21/08/06 - more info here

For components originating from gLite middleware development, relevant tags can be found here.

The Process

The software process is described in MSA3.2.

Software License

• Text to be added to the source files
• Text of the Apache-2 license