| Summary: | No release tag for GEF 3.9.100 | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Mat Booth <mat.booth> |
| Component: | RelEng | Assignee: | gef-inbox <gef-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | nyssen |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Mat Booth
Well, the revision that was released can be easily observed on https://hudson.eclipse.org/hudson/job/gef-master/1130/. It is actually ab961d4c1c913a4f9f58cb666d709ba3b66c56dc. b63ec56b20b75fc5af90fbb1e85911bed35997dc is the last commit before creating the R3_9_100_maintenance branch. Up to then I updated the target to Luna and added the 3.9.100 baseline. (In reply to Alexander Nyssen from comment #1) > Well, the revision that was released can be easily observed on > https://hudson.eclipse.org/hudson/job/gef-master/1130/. It is actually > ab961d4c1c913a4f9f58cb666d709ba3b66c56dc. > b63ec56b20b75fc5af90fbb1e85911bed35997dc is the last commit before creating > the R3_9_100_maintenance branch. Up to then I updated the target to Luna and > added the 3.9.100 baseline. Aha, as a downstream consumer I did not know about that hudson job, which in itself seems like a good reason for also tagging the release in git :-) Tagged ab961d4c1c913a4f9f58cb666d709ba3b66c56dc as R3_9_100 and pushed tag to origin. Resolving as fixed. |