[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[platform-swt-dev] RC4 Test Pass
|
Hi all -
Down to the final week of 3.5! We need to do a test pass
on:
download: http://download.eclipse.org/eclipse/downloads/drops/I20090531-2000/index.php
Praveen Innamuri: win32 (XP), carbon (Leopard)
Lakshmi Shanmugam: gtk.x86, cocoa.x86
Carolyn MacLeod: gtk.x86_64, gtk.x86
Scott Kovatch: cocoa.x86, cocoa.x86_64
Felipe Heidrich: win32 (Vista), carbon (Tiger), win32.x86_64
Silenio Quarti: cocoa.x86, cocoa.x86_64
Grant Gayed: cocoa.x86, motif.aix, motif.hpux, motif.sparc
Bogdan Gheorghe: cocoa.x86_64, gtk (PPC), gtk (sparc), gtk (x86 solaris)
Steve Northover: win32 (XP)
FYI, here are the rules for RC4:
Focus:Serious defects only; documentation.
Fix approval: Component lead plus one other component
lead must approve all work on a component. In addition, any component lead
can veto a change with cause. No changes are to be released without associated
bug report tagged 3.5RC4 including risk assessment and prior approvals.
(Ongoing changes to component documentation do not require special approval.)
API change approval: PMC must approve all API changes.
No changes are to be released without prior approval and associated bug
report. Send the request for approval to the eclipse
pmc mailing list. If a change is made to API
to make it binary compatible with 3.4, technically this is still an API
change, and thus it should be treated in the same way as any other API
change requests.
Notification requirements:Announce bug numbers of
intended non-doc changes to platform-releng-dev@xxxxxxxxxxx
mailing list.
Extra checking requirements:Two additional committers
must check all code changes prior to release. Person who reported bug should
mark the bug as verified once they have retested.