Re: Releasing from Mercurial repo -- procedures?
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
Michael Sperber writes:
> "Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
>
> > Here's the current procedure[1]: [...]
>
> I suggest simply doing all this in a named branch on xemacs-beta.
> (That's how I do release engineering, for Scheme 48.)
Do all what? The tagging and ChangeLogs? If I do that, they won't be
part of the mainline, which defeats one of the main purposes of having
beta releases: providing a timeline for people who are following the
mainline that they can see in the various ways we present history.
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. (If you
tag in the branch, the tag won't be visible on the mainline.)
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta