Releasing from Mercurial repo -- procedures?
sperber at deinprogramm.de
Sun Feb 10 06:49:10 EST 2008
"Stephen J. Turnbull" <stephen at xemacs.org> writes:
> Michael Sperber writes:
> > Not the tagging: You create a named branch, make all the changes you
> > need to do, cut the beta release from that. *Then* you merge your
> > branch back into the mainline, and *then* tag on the mainline.
> This means that in the case in point (a concurrent commit to the
> mainline) the tagged revision *will* be a merge turd and *will*
> include code that is undocumented in the release (at best, and in the
> process you suggest, the tag *will* include code that is not in the
> No, thank you.
You could do all that at once in your local copy, and then push.
> I really don't understand what your point is. We have the free fire
> zone over on the xemacs branch. Why does it matter if the xemacs-beta
> branch has a ceasefire for a few hours? It only affects you and Vin.
I guess I don't understand what your point is. Weren't you asking how
to avoid the "cease-fire"? I have no objection to not doing anything
with xemacs-beta while you're cutting the release---I'm currently
stalled anyway because of the search crash.
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
More information about the XEmacs-Beta