Roadmap Goals for Parrot 3.6: Are we on track?

[James E Keenan]

Friends,

We're two days away from our monthly release, which means we're four 
weeks away from our quarterly supported release of Parrot 3.6 on July 
19.  So this is a good point to ask:  How well are we doing on the 
Release Map goals we set at our last online Parrot Developer Summit, 
which was held on May 14 
(http://lists.parrot.org/pipermail/parrot-dev/2011-May/005887.html)?

1. We set a policy that the Parrot project would "... collaborate with 
HLLs to develop ways of benchmarking the performance of the HLLs as 
targeted to monthly Parrot releases and the expressed needs of those HLLs."

Have we developed those ways of benchmarking the performance of HLLs 
built on top of our monthly releases?

2. whiteknight and cotto were named as the original members of a team to 
pursue the goal of better profiling.  By 3.6 we are to have "studied our 
existing profiling tools, determined their strengths and limitations and 
developed a plan for significant improvements in later supported releases."

Has that study of our existing profiling tools begun?  What progress 
have me made?

3. We recognized the need for Parrot and Rakudo to have relationship 
managers who would "... be each project's principal contact point for 
resolution of problems with regard to breakage or deterioration of 
performance."  I believe we spoke of cotto and whiteknight filling those 
roles from the Parrot side, but I don't know whether we formalized it. 
And my impression from backscrolling through #phasers is that Rakudo 
hasn't made formal assignments either.

Are my impressions correct?  If so, can we get moving on this?

Next week is YAPC::NA::2011 -- the point in the calendar year when 
Parrot developers are most likely to see each other face-to-face, and 
also one of the points where likely Parrot users are able to pose 
questions to us face-to-face.  It would be great to go into YAPC 
confident that we are meeting our current Roadmap Goals.

Thank you very much.

kid51