| Re: [qvto-dev] Rampdown |
Hi all,
I've finished my studies, creating maybe one of the most complex QVTo transformations ever.
@Ed: can you point me to the exact issue that is to be reviewed?
@Sergey: if you'd like to access my transformation for performance analysis: it is going to be publicly released in a few weeks.
Regards
Christopher
----- Nachricht von ed@xxxxxxxxxxxxx ---------
Datum: Fri, 24 May 2013 13:44:45 +0100
Von: Ed Willink <ed@xxxxxxxxxxxxx>
Antwort an: QVTOML developer mailing list <qvto-dev@xxxxxxxxxxx>
Betreff: [qvto-dev] Rampdown
An: QVTOML developer mailing list <qvto-dev@xxxxxxxxxxx>* After RC1[1]: At least 1 PMC member (typically, the Project Lead)
Hi Sergey
We're now in RampDown.
* After RC2[2]: Another Committer from the component or project and
must review and vote + using the Bugzilla flag feature (see below).* After RC3[3]: Two additional Committers and at least 2 PMC
at least 1 PMC member must review and vote +1 after reviewing the bug
for appropriateness and risk.Links:
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
------
[1] http://wiki.eclipse.org/Helios#Milestones_and_Release_Candidates
[2] http://wiki.eclipse.org/Helios#Milestones_and_Release_Candidates
[3] http://wiki.eclipse.org/Helios#Milestones_and_Release_Candidates
----- Ende der Nachricht von ed@xxxxxxxxxxxxx -----
_______________________________________________
qvto-dev mailing list
qvto-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/qvto-dev