| Summary: | manage R4E participation in Juno release train | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
| Component: | Mylyn | Assignee: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | lmcbout, sebastien.dubois, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 368836 | ||
|
Description
Alvaro Sanchez-Leon
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/ |