unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jason Rumney <jasonr@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: Pretest and branch on Friday June 19
Date: Sun, 14 Jun 2009 17:11:16 -0400	[thread overview]
Message-ID: <jwvab4ah6f7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4A3302B8.1050704@gnu.org> (Jason Rumney's message of "Sat, 13 Jun 2009 09:36:56 +0800")

>> 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.

It's indeed possible that we end up releasing a 23.2 that's
bug-fix only.  But I wouldn't worry too much about version numbers in
this respect.

> I don't think there are major changes like multi-tty or unicode
> pending, but there are a lot of minor features being held back, so
> 23.1.50 seems appropriate to me.

Indeed, the plan for 23.2 is to add various non-disruptive features
(packages, ...).  If we start with the safest ones, we can minimize the
risk of having to release 23.2 from the 23.1 branch.

> When someone comes up with a major new feature (collaborative editing,
> or bidi becoming close to usable), we can develop that on a branch
> like was done with unicode and multi-tty (hopefully by then we will be
> using bzr).

AFAIK the major upcoming features for 24 would be lexical scoping
and bidi.  Collaborative editing might be doable without major changes.

This said, I'd like to know what's the Bzr story.  We're pretty much
at the point where we'd be happy to do the switch, so we should get
read"y for it.  But if there are still things missing, it'll have to wait
for "post release".


        Stefan




  reply	other threads:[~2009-06-14 21:11 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 [this message]
2009-06-13  4:19 ` Dan Nicolaescu
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=jwvab4ah6f7.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@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).