The EMT (Engineering Management Team) manages short term release priorities for Glite 3. This involves defining cycles of 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


Integration is putting together a release tagged as 3.0.3. This change will be the latest WMS/LB tags and Condor 6.7.19.


Certification is testing 3.0.2

Beyond many bug fixes, this includes

  • WMS to support Glue 1.2
  • shallow resubmission of DAG nodes

As more updates are moved to the new software process involving 'patches', the following savannah search will show which patches are in certification.

Patches in certification

Current certification status is here

Cert wiki

We cannot make predictions about when a set of updates will leave certification.


The PPS has 3.0.1 available


The production service has 3.0.1 available

EMT Meeting minutes

The EMT normally meets twice a week, on Monday and Wednesday. A short summary of these meetings is forthcoming on indico.

Bug Tracking

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


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
  • Is explicitly cited in cluster manager's weekly reports
  • Will result in a priority patch for the next set of updates taken into certification

Further Platform Evolution

Various issues which touch many components are under ongoing consideration;

  • Move to java 1.5
  • Move to VDT 1.3.10 and SLC4
  • Apache licensing

The Process

The software process is described in MSA3.2.

This topic: LCG > WebHome > LCGGridDeployment > LCGReleasePreparation > Glite3planning > Glite3PS
Topic revision: r10 - 2006-07-12 - OliverKeeble
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback