all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Pretest and branch on Friday June 19
Date: Sat, 13 Jun 2009 16:50:16 -0400	[thread overview]
Message-ID: <ehk53fj1tj.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87k53h10vx.fsf@cyd.mit.edu

Chong Yidong wrote:

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

I think it depends on what Emacs version numbers are supposed to mean.

If a bump in the major version means "major new feature(s)" (eg
unicode, multi-tty), then yes, do what you said.

Personally, I like the convention Emacs 22 fell into:
Going from 22.1 to 22.2, only bug fixes or entirely self-contained new
features (eg a brand new package "foo-mode.el") were allowed. This
meant 22.2 could never be worse than 22.1 in any aspect.

I'd like the same thing to happen again for the 23 series.
I don't see it as a problem if there is only ever a 23.2, with very
few (bug-fix or entirely new packages) changes over 23.1, and if 24.1
comes along relatively quickly with no "huge" changes. Version numbers
are cheap.

If the trunk is used for 23.2, then I feel like I'd have to hold off
making non-bugfix changes to any existing feature, in case of
inadvertent breakage. The feature freeze is already almost a year old,
and it's rather disheartening not to be able to do development.

So I think I'd prefer "24.0.50".




  parent reply	other threads:[~2009-06-13 20:50 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
2009-06-13 19:09   ` Chong Yidong
2009-06-14 14:35     ` joakim
2009-06-13 20:50 ` Glenn Morris [this message]
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

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

  git send-email \
    --in-reply-to=ehk53fj1tj.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.