Ok, thanks. A convention we settled on (in the thousands of notes to this list) is that you can still enable your _contribution_ element and then set enabled=false on your repository or features. That way, it's clear you intend to participate ... and (eventually) I can start sending notes about disabled repositories and features :)
Thanks again, From: Miles Parker <[email protected]> To: Cross project issues <[email protected]>, Date: 10/03/2012 06:14 PM Subject: Re: [cross-project-issues-dev] Kepler M2 staging repository complete Sent by: [email protected] David, there are some feature dependency issues for help support for AMP so I'm having to leave it disabled until I can fix that. On 2012-10-03, at 2:13 PM, David M Williams <[email protected]> wrote: > I've been so busy these past few days, I've not even had time to send any nag notes! > > But here we are, Kepler M2 +3 day at 5 PM. > > I have just now promoted what I am assuming is the final M2 staging repo (unless some speaks up in next hour or two). > > Thanks to those two additional projects for enabling their contributions -- we might even get some EPP packages this time! > > Only 7 to go (to enable, or drop out?) > > amp.b3aggrcon - org.eclipse.simrel.build > emf-query2.b3aggrcon - org.eclipse.simrel.build > gyrex.b3aggrcon - org.eclipse.simrel.build > jwt.b3aggrcon - org.eclipse.simrel.build > mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build > soa-bpel.b3aggrcon - org.eclipse.simrel.build > soa-sca.b3aggrcon - org.eclipse.simrel.build > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
