Releasing from Mercurial repo -- procedures?

Michael Sperber sperber at deinprogramm.de
Sun Feb 10 13:38:00 EST 2008


"Stephen J. Turnbull" <stephen at xemacs.org> writes:

> Michael Sperber writes:
>
>  > You could do all that at once in your local copy, and then push.
>
> I plan to do it that way, but it does require a freeze to avoid a
> concurrent commit AFAICS.
>
> In the case of a concurrent commit, that doesn't meet the desiderata
> of (a) tagged revision is in the tarballs, (b) all contents are
> documented in CHANGES-beta, and (c) tagged revision is not a merge.

I think it meets all of your desiderata, but as I said, no problem with
holding off.  It even works without a named branch: If you just pull the
version you want, make your changes, tag the version you want, make the
tarballs, pull again, merge, and push, then (a) (b) and (c) are all met.

>  > I guess I don't understand what your point is.  Weren't you asking how
>  > to avoid the "cease-fire"?
>
> No, I wanted to know if anybody objected to a normally short freeze on
> the xemacs-beta repo.  If so, yes, I'd like to know how to do this in
> a way that both meets my desiderata and avoids a freeze.

I don't object.

> I also wanted to know if I have commit access to it, which question
> has sorta been ignored. :-)

Sorry.  You do.

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla



More information about the XEmacs-Beta mailing list