I updated the EPP build jobs, the configurations, etc. and I am now able to build the EPP p2 repository... but (and that's the important message here!):
With the current status I don't see a chance to create a single Kepler M1 package, because too many required project contributions are missing! Regards, Markus On Wed, Aug 22, 2012 at 7:09 AM, David M Williams <david_willi...@us.ibm.com > wrote: > Still 26 projects not enabled for Kepler M1. > > Can some one explain to me what this is about? Some passive aggressive > protest? Too many people take vacation all summer and don't even check > Eclipse mailing lists? > Are projects just indecisive and think a commitment now means it is a > written in stone promise (which is never the case). > I know one or two people have mentioned they have special problems that > will likely prevent participation in M1, but, > If I hear nothing, I'll assume the remaining 24 or so are dropping out, > and will remove those files from the 'master' branch. > For those projects to rejoin later will take an exception since there's a > requirement for those participating to "keep participating" or else inform > us all you no longer plan to. > The M4 deadline only applies to branch new projects, others (in previous > release) expected to be in M1. > > http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Integrate_Early_and_Often > > I should emphasize, if people do not want to be in sim. release, that's > fine. It is a voluntary choice, and does take some amount of extra work. > So, it doesn't mean you are a "bad project" or anything if you decide not > to. > But, it is only common courtesy to keep us informed explicitly. > > Thanks, > > > > amp.b3aggrcon - org.eclipse.simrel.build > cdt.b3aggrcon - org.eclipse.simrel.build > dltk.b3aggrcon - org.eclipse.simrel.build > emf-query2.b3aggrcon - org.eclipse.simrel.build > emft-ecoretools.b3aggrcon - org.eclipse.simrel.build > emft-eef.b3aggrcon - org.eclipse.simrel.build > emft-egf.b3aggrcon - org.eclipse.simrel.build > emft-emffacet.b3aggrcon - org.eclipse.simrel.build > epp-mpc.b3aggrcon - org.eclipse.simrel.build > gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build > gyrex.b3aggrcon - org.eclipse.simrel.build > jwt.b3aggrcon - org.eclipse.simrel.build > mat.b3aggrcon - org.eclipse.simrel.build > mdt-modisco.b3aggrcon - org.eclipse.simrel.build > mdt-papyrus.b3aggrcon - org.eclipse.simrel.build > mft.b3aggrcon - org.eclipse.simrel.build > mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build > pdt.b3aggrcon - org.eclipse.simrel.build > rap.b3aggrcon - org.eclipse.simrel.build > recommenders.b3aggrcon - org.eclipse.simrel.build > rtp.b3aggrcon - org.eclipse.simrel.build > scout.b3aggrcon - org.eclipse.simrel.build > soa-bpel.b3aggrcon - org.eclipse.simrel.build > soa-sca.b3aggrcon - org.eclipse.simrel.build > tcf.b3aggrcon - org.eclipse.simrel.build > tm.b3aggrcon - org.eclipse.simrel.build > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > >
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
