Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dtp-dev] Update: DTP 1.5 ramp down process

In the 6/5 PMC meeting, we discussed how to streamline the process
mentioned below, since people are now using both the dtp-pmc mailing list
and Bugzilla to vote on bug petitions.

We have decided to update the process as follows:

1. Committer sends a petition to include bug(s) in DTP 1.5 to dtp-pmc
2. PMC members visit the bug(s) in Bugzilla and use the PMC approval field
to register a vote

The rest of the process remains the same.

John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.

             06/05/2007 11:42          dtp-dev@xxxxxxxxxxx                 
             AM                                                         cc 
                                       Clarification: DTP 1.5 ramp down    
                                       process(Document link: John Graham) 

One clarification about the process described below: if there are no
approved commits to CVS, then there is no reason to produce a nightly
build, since:

1. The build would be identical to the previous one, and hence a waste of
download server resources
2. Identical nightly builds could cause confusion among users of DTP, since
they would be expecting some change based on the process below

So, since there were no approved changes committed yesterday (6/4) and
today (6/5), there are no nightly builds for 6/4 and 6/5. Based on the DTP
mailing list traffic and bug activity, however, I expect a RC3 nightly
build either tomorrow or the next day.

Committers: Remember to update approved bugs with the list of modified
plug-ins, or I will not be able to update the snapshot correctly.

John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.

             06/01/2007 11:56          dtp-dev@xxxxxxxxxxx                 
             AM                                                         cc 
                                       DTP 1.5 ramp down process           

As the DTP 1.5 release approaches at the end of this month, we have to be
careful to provide consistent, predictable builds to Europa that avoid
further defect injection (new defects or regressions). As part of the
Europa coordinated release, DTP has provided a Rampdown Policy to the
Europa working group, and we have reviewed this policy in committer meeting
a number of times since it was first approved at the end of April:

We are now in the "Test Pass" for DTP 1.5RC3, with a "Test and Fix Pass"
beginning next Tuesday, June 5, and continuing through Monday, June 11.
Note also that all bugs/enhancements must be approved by the PMC (that is,
at least two +1 votes) according to the policy for RC3, RC4 and any final
DTP 1.5 builds. In order to check that we maintain this process, the build
will be adjusted as follows:

1. DTP 1.5RC3 6/1 nightly was built from a 6/1 EST snapshot of DTP CVS
2. All subsequent DTP 1.5 builds will be based on this snapshot as well
(note: this snapshot is not the same as HEAD going forward), unless
approved fixes are added
3. A committer wishing to address further DTP 1.5 bugs/enhancements needs
to get PMC approval, following the Rampdown Policy
4. Once PMC approval is granted, the committer can check in the necessary
changes. The plug-ins changed must be noted in the associated bug
5. Upon resolving an approved bug, the committer should send mail to
dtp-dev@xxxxxxxxxxx announcing the bug number
6. The build snapshot will updated but only for the plug-ins mentioned in
email to dtp-dev
7. Any build breakage or serious defects as a result of updating the
snapshot will cause fallback to the previous snapshot version until the
problem is addressed.

This means that no changes will appear DTP 1.5 builds going forward unless
they are approved and the snapshot is updated accordingly. While this
process might seem cumbersome, it is simply a check put in place to ensure
that we are meeting our Europa requirements by following the published
Rampdown Policy.

One potential problem here is that in the past we've allowed
documentation/code comment updates freely until the release. My sense is,
however, that this option has not been widely used, and hence the impact
should be small. If you do need to update plug-in documentation/comments,
just send an email to dtp-pmc about the change, and we'll update the
snapshot to accommodate it.

Please feel free to discuss any concerns about this build procedure or the
Rampdown Policy using the dtp-pmc mailing list.

John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.

Back to the top