[modeling-pmc] EMF Services breakage (was Re: [cross-project-issues-dev]

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

Wayne. I think some level of build breakage is inevitable, but if the 
new team can at least create a new EMF Services repo, All-In-One or 
Core, soonish for M5, or just after M5 for M6, we can all change our 
references to consume the new repo. I doubt the team will have changes 
as a high priority so replicating the M2 contribution plugins should 
avoid more than this trivial break.

(It seems unreasonable for a new merged project to have to replicate the 
many old unmerged artefacts in the old locations.)

    Regards

        Ed Willink


On 19/12/2016 21:26, Wayne Beaton wrote:
> I've created review records and tracking bugs.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=509485
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=509487
>
> For the second bug report, I need a list of committers for the new 
> "EMF Services" project. Also, feel free to weigh in on any other 
> aspect of the new project (e.g. the name).
>
> Most of the work in these exercises will be done by EF staff. I 
> believe that, for the most-part everything (e.g. Git repos, downloads) 
> will stay in place with just new UNIX group assignments. I am a little 
> concerned that we may break the builds, so I'll need somebody to step 
> forward to take responsibility to test/fix issues like that.
>
> I've given us a month to get everything together (I've set the end of 
> the review period to Jan 18). I'm a bit concerned that if we break the 
> build in the process of transitioning, we'll put Oxygen M5 at risk. 
> We'll have to sort out timing for implementing the actual changes to 
> mitigate that risk.
>
> Thanks,
>
> Wayne


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus