Community
Participate
Working Groups
This task is to keep track of the overall activities needed to join the Juno release train. see http://dev.eclipse.org/mhonarc/lists/mylyn-dev/msg01433.html As per message above: * The Hudson Job has been requested, see Bug 360898 * Sign Artifacts: Steffen, please provide the reference to the maven plug-in mentioned over the phone * publish to a separate directory: Steffen, please create folder and give write permissions to Hudson * Once we have the build working, we can then request committer rights into the Callisto project.
Some information about the maven-signing-plugin are here: http://aniszczyk.org/2011/05/18/eclipse-org-signing-support-for-maven-tycho/. I would assume that quite a bit has changed since and the EGit build (or the build of any other project that uses the plug-in) is probably a good place to look for an example. I have created /home/data/httpd/download.eclipse.org/reviews/r4e/ as a download location.
I have moved this bug under the R4E restructuring. If R4E still intends to participate in Juno you would probably need to request an exception through the planning council since the M4 milestone has already passed and R4E is now technically speaking a new project that would be joining train.
Lets revisit this when the tycho build is fully functional on the new repository. If not possible we can follow the release train.
Not officially partcipating on Juno, The release plan is available under http://www.eclipse.org/r4e/documentation/
