Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [qvto-dev] Rampdown 
Hi
looking at my expected participation in the next months, there is really nothing I can promise at this point as long as my personal future career is uncertain.
Maybe the most reasonable role for me is to continue reporting/fixing legacy bugs. I still have some pending reports in petto. 


Regards
Christopher


----- Nachricht von ed@xxxxxxxxxxxxx ---------
     Datum: Fri, 31 May 2013 14:59:23 +0100
       Von: Ed Willink <ed@xxxxxxxxxxxxx>
   Betreff: Re: [qvto-dev] Rampdown
        An: Christopher Gerking <cgerking@xxxxxxxxxxxxx>



Hi Christopher
Welcome back. Perhaps you can give some indiction of your expected participation in the next few months so that the project can be co-ordinated.
You should be subscribed to the QVTo Buzilla Inbox so that you see all Bugzilla traffic. I leave it as an exercise for the student to search the QVTo RESOLVED's in the last two weeks to find the issue.
Since the code is now committed, reviewing is now a bit late to contribute to a change for Kepler, but reviewing is always good. 

    Regards

        Ed



On 31/05/2013 12:43, Christopher Gerking wrote:

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>


   Hi Sergey

We're now in RampDown.

 *  After RC1[1]: At least 1 PMC member (typically, the Project Lead)
must review and vote + using the Bugzilla flag feature (see below).
 *  After RC2[2]: 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[3]: 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


Links:
------
[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 -----





-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3343 / Virus Database: 3184/6370 - Release Date: 05/30/13








----- Ende der Nachricht von ed@xxxxxxxxxxxxx -----

Back to the top