From: Bill Wohler <wohler@newt.com>
Cc: mh-e-devel@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: Continued development during release process
Date: Sun, 23 Apr 2006 19:38:27 -0700 [thread overview]
Message-ID: <10985.1145846307@olgas.newt.com> (raw)
In-Reply-To: <m3fyk4f1ob.fsf@kfs-l.imdomain.dk>
Kim F. Storm <storm@cua.dk> wrote:
> Bill Wohler <wohler@newt.com> writes:
>
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> >> When the pretest is under way, at some point a release-candidate
> >> branch is created. (I say ``at some point'' because I don't think
> >> there's an agreement whether this should happen right away when the
> >> pretest starts, or later, much closer to the release itself, i.e. at
> >> pretest end.) This branch is used for the initial release, in this
> >> case for version 22.1, and for all subsequent bug-fix releases that
> >> (at least ideally) fix bugs without introducing major features; these
> >> would be versions 22.2, 22.3, etc., until it is decided by The Powers
> >> That Be that it's time to make another release from the trunk.
> >
> > Thanks. We'll hold off until that branch is created.
>
> You can just create your own branch and continue post-22.x work on that
> until we branch for the 22.x release.
I am aware of that. I was hoping to avoid it.
--
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.
next prev parent reply other threads:[~2006-04-24 2:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 21:37 Continued development during release process Bill Wohler
2006-04-22 10:35 ` Eli Zaretskii
2006-04-23 16:01 ` Bill Wohler
2006-04-23 20:59 ` Kim F. Storm
2006-04-24 2:38 ` Bill Wohler [this message]
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=10985.1145846307@olgas.newt.com \
--to=wohler@newt.com \
--cc=emacs-devel@gnu.org \
--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).