unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Pretest and branch on Friday June 19
Date: Fri, 12 Jun 2009 21:19:08 -0700 (PDT)	[thread overview]
Message-ID: <200906130419.n5D4J8a3014569@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87k53h10vx.fsf@cyd.mit.edu> (Chong Yidong's message of "Fri, 12 Jun 2009 19:35:30 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:

  > Following discussion with Stefan, I plan to make the next pretest,
  > 23.0.95, next Friday (June 19).  At that time, I will also cut the
  > EMACS_23_BASE branch and open the trunk for development.  If we need a
  > 23.0.96 pretest, it will be made from the branch.
  > 
  > I'm not certain what version number to assign the trunk after branching.
  > I'm inclined to use 23.1.50, which assumes we'll use the trunk for
  > developing 23.2.  Maybe this is optimistic; as many will recall, what
  > ended up as Emacs 22 was originally slated for 21.3.  Opinions welcome.

Shouldn't the numbering depend on the plan for the release after 23.1?
Is lexical binding going to be added?  (or some similar major feature)?
Or just incremental work? (bug fixing/adding packages/etc)?

(Well, actually the numbering is much less important than the plan... )




  parent reply	other threads:[~2009-06-13  4:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 23:35 Pretest and branch on Friday June 19 Chong Yidong
2009-06-13  1:36 ` Jason Rumney
2009-06-14 21:11   ` Stefan Monnier
2009-06-13  4:19 ` Dan Nicolaescu [this message]
2009-06-13 19:09   ` Chong Yidong
2009-06-14 14:35     ` joakim
2009-06-13 20:50 ` Glenn Morris
2009-06-13 21:18   ` Chong Yidong
2009-06-14  1:50     ` Glenn Morris

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=200906130419.n5D4J8a3014569@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    /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).