Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 418395

Summary: no 2.9.1 tag in the repo
Product: [Tools] GEF Reporter: Krzysztof Daniel <krzysztof.daniel>
Component: RelEngAssignee: gef-inbox <gef-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: krzysztof.daniel, nyssen
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Krzysztof Daniel CLA 2013-10-01 04:25:13 EDT 
it would be good to have gef repo tagged after each release.
Comment 1 Alexander Nyßen CLA 2013-10-01 04:48:00 EDT 
That's correct, but: our releases are published from the gef-master (for development stream builds) or gef-maintenance (for maintenance stream) builds on hudson.eclipse.org (that is, we do not re-build especially for a release but promote an already existing and tested build). Our download page (http://www.eclipse.org/gef/downloads/index.php) provides a link from each build (build details) to the hudson job that was promoted. Following that link you can directly infer the Git branch and revision that was taken for the build, here 71034a324fe44fd1be29529b712bed3808105033, origin/origin/R3_9_maintenance. Thus, the git repo state that was taken for each of our builds can easily be reproduced. 

As the builds are not re-spinned for a release, an automatic build tagging of releases is not reasonable. We could add this to our publish shell script, but that seems to be quite cumbersome to me. Resolving thus as WORKSFORME.
Comment 2 Krzysztof Daniel CLA 2013-10-01 05:34:29 EDT 
Thanks for all the explanations - it makes a lot of sense.

Just for the reference - platform tags repository after a release (bug 410747).