RE: [hyades-dev] Commiter vote required for M10 check-in

[Harm Sluiman <sluiman@xxxxxxxxxx>]

You are correct. This is the process
agreed on the weekly commiter call this week. The minutes were not posted
(and yes they should have been) but all the commiters were on the call
and agreed to this process.
On a call (weekly at the moment) we
review all outstanding candidate defects for possible integration. A decision
is made as to when the fix can go in or if it should be deferred. All commiters
must approve.
Defects not handled in the call or any
new defects need to go through the same process. It was agreed that commiters
could post a defect as a candidate to fix for a vote, along with the problem,
the solution, the impact, how it was being tested for regression, and when
it would be ready to drop, to the mailing list for the other commiters
to vote. The commiters have 24 hours to vote, At this stage a missing vote
is considered approval. Soon this will switch to a required position from
all commiters before moving the fix in.

We are using the mailing list to do
this so those outside the contributing developers can see any final changes
going into the final 3.0 drivers. The volume of defects is low so the volume
of mail should be low. If there is any debate, we will arrange a quick
commiter call.

Thanks for your time.
--------------------------------------------------------------------------
Harm Sluiman, STSM,  
phone:905-413-4032   fax: 4920  
cell: 416-432-9754
mailto:sluiman@xxxxxxxxxx
Admin : Gabrielle Chapman chapmaga@xxxxxxxxxx  Tie: 969-2323

Michael.Norman@xxxxxxxxxxxxx
Sent by: hyades-dev-admin@xxxxxxxxxxx

05/26/2004 11:49 AM

Please respond to
hyades-dev

To	hyades-dev@xxxxxxxxxxx
cc
Subject	RE: [hyades-dev] Commiter vote required for M10 check-in

I think the rule at the moment is that a committer
has to recommend it 
to the rest of the committers.  In other words if you are not acommitter
find the committer with responsibility for the relevant area, work with
them, then get them to promote it to the rest of the group, with the 
vote happening on hyades-dev. 
 
 
Harm should confirm this, but whatever happens the vote has to be on 
hyades-dev so that there isa public archived record of the activity, so
if you are seeing a stream of email you don't need to read, sorry about
that.

Mike

-----Original Message-----
From: sluiman [mailto:sluiman@xxxxxxxxxx]
Sent: Wednesday, May 26, 2004 4:36 PM
To: hyades-dev
Subject: Re: [hyades-dev] Commiter vote required for M10 check-in




Peter please work through Joe the submit defect fixes for approval. 

Thanks for your time.
------------------------------------------------------------------------
--
Harm Sluiman, STSM,  
phone:905-413-4032   fax: 4920  
cell: 416-432-9754
mailto:sluiman@xxxxxxxxxx
Admin : Gabrielle Chapman chapmaga@xxxxxxxxxx  Tie: 969-2323 



Peter Sun <psun@xxxxxxxxxx> 
Sent by: hyades-dev-admin@xxxxxxxxxxx 

05/26/2004 11:21 AM 
Please respond to
hyades-dev


To
hyades-dev@xxxxxxxxxxx 
cc
hyades-dev-admin@xxxxxxxxxxx 
Subject
[hyades-dev] Commiter vote required for M10 check-in

                





The following M10 defects require Committer's approval: 

Target drop date to cvs:        May 26 afternoon EST
Target regression test date:May 26 afternoon EST 
Target candidate drop:        May 27 (pass 2) 

Defect 63867: 
bugzilla_63867 -- Datapool Editor: Value class values are not being 
updated correctly.

Rationale: 

In this release, we are adding support for Display Value Classes which
allows consumers to customize the Datapool Editor to handle different 
editors (for example, a color chooser).  A bug was found by a consumer
of the component noting that the values were not being updated 
correctly.  This was due to a missing call to the Display Value Class
API.  This was not an issue for base Hyades because all values are
stored as strings and the default string editor always returned the 
updated value.  The fix involves adding a call to the update method
of 
the display value class and using the updated value.  The fix is 
currently being tested by the consumer who found the bug (it is not yet
checked into CVS).  Without this fix, the feature is basically useless
for complex editors whose getValue() does not return the actual value 
(for example a combo box). 

Risk Assessment: 

No API change. Does not impact consumers except that value objects get
updated properly. 
Low to Medium risk change. 


==================================================
Peter Sun 
Staff Software Engineer . Rational Software . IBM Software Group
(781) 676-2758 (TEL) . (781) 676-7510 (FAX)




_______________________________________________
hyades-dev mailing list
hyades-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/hyades-dev