[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Planning Meeting Discussion Topics - 13 June 2012

> ... a potential problem with continuing work before we used the annotated tags, but that was a misunderstanding on my part. ....

But, still, I think best to do "continuing work" in a "topic branch" or "feature branch" (e.g. named <committer_id>/<topic>). There is a chance,
though very very small, that some blocking problem might still be found that would require a respin next week. Or, perhaps others know more about how to get back to RC4 state for a rebuild ... but ... if it was me ... I'd take the easy way and use a feature branch between now and 6/27.





From:        Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
To:        "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>,
Date:        06/13/2012 01:21 PM
Subject:        Re: [eclipse-dev] Planning Meeting Discussion Topics - 13 June 2012
Sent by:        eclipse-dev-bounces@xxxxxxxxxxx




When we release, we need to tag our repos with both R3_8 and R4_2.  All component leads should CC themselves on this bug, but take no action yet:

Bug 382524 - Tag Juno Release

I had brought up a potential problem with continuing work before we used the annotated tags, but that was a misunderstanding on my part.

Annotated tags do not create a commit in the branch history so they won't interfere with any projects that are starting work on the next release.  They store the tag message and other information in an object associated with the tag.


--
Paul Webster
Hi floor.  Make me a sammich! - GIR
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev