Re: [rt-pmc] Planning Council

[Glyn Normington <gnormington@xxxxxxxxxx>]

Yes, that's partly why I brought it up.

Regards,
Glyn

On 22 Jul 2011, at 17:03, Jesse McConnell wrote:

> Based on what Wayne said I am wondering if this is within the purview
> of the Planning Council at all now :/
> 
> jesse
> 
> --
> jesse mcconnell
> jesse.mcconnell@xxxxxxxxx
> 
> 
> 
> On Fri, Jul 22, 2011 at 10:57, Glyn Normington <gnormington@xxxxxxxxxx> wrote:
>> On 22 Jul 2011, at 16:29, Jesse McConnell wrote:
>> 
>>> I know that Glyn is hot on the topic of tracking down specific release
>>> requirements as they relate to rt projects..
>> 
>> Yes, if that includes release train requirements. I'd like the RT PMC and the Planning Council to agree the minimum requirements for a RT project to participate in the Eclipse release train. There's just too much in the current set of "must dos" for Virgo to be able to justify the cost.
>> 
>> I am not aware of anything that would prevent Virgo from having joined the Indigo release train if we had wanted to, apart from the stipulated requirements. ;-) You see if we'd plopped Virgo 2.1.1 in the Indigo deliverables, I don't think a single user would have blinked. Yes, some may have whinged about the lack of a p2 repo, but they'd soon see that as a missing feature to be added later (Virgo 3.5 as it turns out).
>> 
>> Glyn
>> _______________________________________________
>> rt-pmc mailing list
>> rt-pmc@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>> 
> _______________________________________________
> rt-pmc mailing list
> rt-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/rt-pmc