unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler <wohler@newt.com>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Continued development during release process
Date: Fri, 21 Apr 2006 14:37:13 -0700	[thread overview]
Message-ID: <2167.1145655433@olgas.newt.com> (raw)

I have some developers who have been sitting on some changes until MH-E
8.0 is released. Since this is looming (I'm putting out the first
release candidate today), it's time for me to find out how the Emacs
maintainers would like us to proceed.

First of all, if you're handling the release, including tagging and
stuff, please let me know who you are.

Second, once you add a pretest tag, will you make subsequent tags based
upon that tag, or will you simply tag the trunk? The implications for
the MH-E project is that in the former case, my developers can simply
check in their changes. In the latter case, we'll have to branch and
merge until 22.1 is released, which is a lot of extra work (so of
course I'm hoping for the former).

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.

             reply	other threads:[~2006-04-21 21:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 21:37 Bill Wohler [this message]
2006-04-22 10:35 ` Continued development during release process Eli Zaretskii
2006-04-23 16:01   ` Bill Wohler
2006-04-23 20:59     ` Kim F. Storm
2006-04-24  2:38       ` Bill Wohler
2006-04-22 22:32 ` Richard Stallman
2006-04-23 14:10   ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2167.1145655433@olgas.newt.com \
    --to=wohler@newt.com \
    --cc=mh-e-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).