[qvto-dev] Rampdown

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[qvto-dev] Rampdown

From: Ed Willink <ed@xxxxxxxxxxxxx>
Date: Fri, 24 May 2013 13:44:45 +0100
Delivered-to: qvto-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/mailman/private/qvto-dev>
List-help: <mailto:qvto-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/qvto-dev>, <mailto:qvto-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/options/qvto-dev>, <mailto:qvto-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130509 Thunderbird/17.0.6

Hi Sergey

We're now in RampDown.

After RC1: At least 1 PMC member (typically, the Project Lead) must review and vote + using the Bugzilla flag feature (see below).
After RC2: Another Committer from the component or project and at least 1 PMC member must review and vote +1 after reviewing the bug for appropriateness and risk.
After RC3: Two additional Committers and at least 2 PMC members must review and vote +1 after reviewing the bug for appropriateness and risk.

The above applies to functional code. Documentation and examples are more relaxed; effectively use RC n-2 policies.

Even though I am/was a component co-lead, I'm not on the PMC, so you'll need to get Kenn/Ed/... to approve any more commits.

Your latest patch looks fairly substantial, so it would be good to get it reviewed.

Christopher: you were looking at trace issues; any chance?

Regards

Ed Willink

Follow-Ups:
- Re: [qvto-dev] Rampdown
  - From: Christopher Gerking

Prev by Date: [qvto-dev] Christopher Gerking has been declared to be an active committer
Next by Date: Re: [qvto-dev] Rampdown
Previous by thread: [qvto-dev] Christopher Gerking has been declared to be an active committer
Next by thread: Re: [qvto-dev] Rampdown
Index(es):
- Date
- Thread

Breadcrumbs