Everything is on track to make Juno SR1 available tomorrow. 
Thanks for that!

And before we all get excited tomorrow and bask in that glow, I wanted to 
send a reminder that Kepler M2 is due next week. So, you have until 
Wednesday to make (or enable) your contribution for M2. 

There are still 9 _contributions_ disabled, and until they enable their 
contribution, many others have to disabled features or repositories that 
depend on them which in turn eliminates many EPP packages. As a reminder, 
you can contribute the same content for Kepler, as you do for Juno, if it 
still fits and you have not started new Kepler work yet ... but ... as a 
reminder ... the requirement was to get a positive confirmation from 
everyone they intend to be "in" and not have me make that assumption and 
enable contributions automatically. 

amp.b3aggrcon - org.eclipse.simrel.build
cdt.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
rap.b3aggrcon - org.eclipse.simrel.build
soa-bpel.b3aggrcon - org.eclipse.simrel.build
soa-sca.b3aggrcon - org.eclipse.simrel.build

Open a cross-project bug or ask a question here on this list if you need 
help. 

Thanks all, 
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to