| Summary: | Oomph in Neon Stream point to wrong repository | ||
|---|---|---|---|
| Product: | Community | Reporter: | David Williams <david_williams> |
| Component: | Cross-Project | Assignee: | David Williams <david_williams> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | stepper |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| See Also: |
https://git.eclipse.org/r/81114 https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=b7ffb9d25b927039b20cf55afd78aaaa7e1f8928 |
||
| Whiteboard: | |||
|
Description
David Williams
New Gerrit change created: https://git.eclipse.org/r/81114 Gerrit change https://git.eclipse.org/r/81114 was merged to [Neon_maintenance]. Commit: http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=b7ffb9d25b927039b20cf55afd78aaaa7e1f8928 For those trying to submit, and getting a failed build you may have to "rebase", but can then (I think) re-trigger a build. Darned, I forgot that a new mechanism in our promotion system removes the milestones preceeding a release, and that the simrel contribution still refers to one such milestone. I apologize for the hazzle that I caused to the release train! David's fix is correct. Thank you David. Thinking again about our new milestone-removal mechanism, it was probably a bad idea altogether. Tomorrow, I'll rework it or remove it... |