Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and outlook for Indio M5

Dave,

EMF would like to request a respin to pick up our RAP contributions (I forgot to re-enable them after RAP made their contribution).

Thanks,

Kenn

On Thu, Feb 3, 2011 at 1:20 AM, David M Williams <david_williams@xxxxxxxxxx> wrote:
Technically, we should be done with M5, and I will assume we are, unless someone makes a case for a respin. The main reasons I think we _might_ want to consider a respin, are that a) I did have to disable some sequoyah features and the papyrus contribution at the last minute, to get a green build, and suspect we are in a different timezones, since I've not heard anything from them; and also that some features appear disabled that surprised me and I wonder if someone just forgot to re-enable them? Or ... maybe they meant to leave disabled? Should they be deleted from contribution files?. The following contribution files have one or more features disabled. Please check and comment if anything is amiss ... or, perhaps projects just wanted to wait for M6 before re-enabling?  

buckminster.b3aggrcon
dsdp-sequoyah.b3aggrcon
emf-emf.b3aggrcon
gmp-gmf-tooling.b3aggrcon
mdt-papyrus.b3aggrcon

In any case, since we are past the +3 deadline, I have disabled. the Indigo M5 aggregation builds, so please make a case if you have one (in particular,  please specify if anything is required for EPP packages?). I know Markus will be building the final EPP M5 packages today (Thursday) so a respin of repo may require a respin of EPP packages too?

I know it is a busy week ... with both M5 and SR2 RC2 ... which will be my next note. :)

Thanks,

 
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top