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

Bug 336289

Summary: How to tag milestone builds
Product: [ECD] Orion Reporter: Andrew Niefer <aniefer>
Component: ClientAssignee: Project Inbox <e4.orion-inbox>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: dj.houghton, eclipse.felipe
Version: 0.2   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Andrew Niefer CLA 2011-02-03 16:43:46 EST 
It is a good idea to tag the repos whenever we do a milestone.

Generally in Eclipse SDK CVS, the builder tags the map files and then the releng tool can be used to get those specific versions of each project.  Or, individual projects can choose to tag a milestone.


In Git, we can't really tag all the project with a common tag like "R0_2M5" because the tag affects the entire repo and different projects may not necessarily all line up.

We could tag the releng map files with the milestone even though there is no releng tool to ease getting individual projects from the map file.  However, the map files share the org.eclipse.orion.server repo and it may be confusing to have a milestone tag showing up on projects when it really only applies to the map file.


One possibility, would be to somehow create a branch that contains each project at the specific commit that was in the milestone.  I don't really know if this is possible.
Comment 1 John Arthorne CLA 2011-06-28 13:36:13 EDT 
I have been thinking about this. I think it is sufficient to tag the final commit at the time of the build. Since our build process tags all projects that have changed, we know this commit contains:
 - For each project that has changed in that build, the tag obviously matches the source that went into the build
 - For each project that has not changed, we know it has identical contents to its state the last time it was tagged (because otherwise our builder's tagging step would have applied a new tag). 

For repositories that contain map files, the commit made by the builder to update the map files is the right commit to represent that build/milestone/release. We can easily do this after the fact because the builder adds a tag for that build id. For example the 0.2 release is represented by the commit with tag "v20110627-0200", which was our final build. We can add the "R0.2" tag to that same commit once we are officially ready to release.
Comment 2 John Arthorne CLA 2011-07-28 11:51:52 EDT 
Nothing to do here.