[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[platform-ui-dev] HEAD is open Fwd: [platform-releng-dev] Transition to RC1 fix pass
- From: Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Apr 2010 21:39:52 -0400
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=V0YNkeC9R6PgFNbPZLYTWPNACxbREmTCVP/X8PX0BHHPY5MjTZRFeVj7YYCrDjs0Yz vJWI893bu8Zf7MWxAOxKwTj1g7NY6c+XpFoi8A3VEi8S+zPLBrlGtTZjw6ZF/yCcvf+L 6dE4VKrZDzB775onM9Dl0+1PSP1+0luvXi6tA=
Just a reminder that patches need +1 from another committer to go into
HEAD in RC1. See below.
---------- Forwarded message ----------
From: Darin Wright <Darin_Wright@xxxxxxxxxx>
Date: Fri, Apr 30, 2010 at 12:36 PM
Subject: [platform-releng-dev] Transition to RC1 fix pass
Please familiarize yourself with the 3.6 end game and the RC1 rules of
Focus:(1) P1 defects, (2) performance defects, (3) special "polish" items.
Fixing other defects has lower priority.
Fix approval: Another committer must +1 your bug report. All changes must
have their associated bug reports tagged 3.6RC1. (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.5, technically this is still an
API change, and thus it should be treated in the same way as any other API
Notification requirements: None.
Extra checking requirements: One additional committer must check all code
changes prior to release.
Hi floor. Make me a sammich! - GIR