Re: [mylyn-pmc] EGit move

[Mik Kersten <mik@xxxxxxxxxxx>]

Hi Wayne,

I'm wondering how it's best to proceed around that limitation, as I think
that it would be beneficial to have things like common build
infrastructure coordinated in time for Indigo.  Also, I was thinking that
having EGit graduate out of incubation within Mylyn would be a good path
to get EGit into the Eclipse distros, as the "matured" Mylyn sub-projects
are included in all distros other than Eclipse classic.  And this would in
turn give us a good forcing function to make sure that the UIs are nicely
meshed together across tasks, SCM, CI, etc.

How about we schedule our first PMC call to discuss this and other Indigo
related planning?

Mik

--
Dr. Mik Kersten
Tasktop CEO, Mylyn Lead, http://twitter.com/mik_kersten
Assistant: zoe.jong@xxxxxxxxxxx, +1-778-588-6896, Skype: zoe.e.jong


> -----Original Message-----
> From: mylyn-pmc-bounces@xxxxxxxxxxx [mailto:mylyn-pmc-
> bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
> Sent: January-20-11 7:05 PM
> To: mylyn-pmc@xxxxxxxxxxx
> Subject: Re: [mylyn-pmc] EGit move
>
> EMO IP Team has asked that we not schedule any moves until post Indigo.
> They are a little understaffed at the moment.
>
> Wayne
>
> On 01/20/2011 08:42 PM, Steffen Pingel wrote:
> > On today's Mylyn call the question came up when EGit was moving to the
> > Mylyn top-level project but I don't think we have settled on anything,
> > yet. We are planning to do the Mylyn 3.5 on March 16th which coincides
> > with the EGit 0.11 release. Would that tentatively be a good time?
> >
> > Steffen
> >
> _______________________________________________
> mylyn-pmc mailing list
> mylyn-pmc@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/mylyn-pmc