From: Ken Raeburn <raeburn@raeburn.org>
To: "emacs-devel@gnu.org discussions" <emacs-devel@gnu.org>
Subject: Re: next emacs version?
Date: Fri, 19 Mar 2010 22:35:54 -0400 [thread overview]
Message-ID: <5E984B3C-4B86-4FA6-8675-4C8501CC2285@raeburn.org> (raw)
In-Reply-To: <0E10B96B5C814EE8B95B57972F13E189@us.oracle.com>
On Mar 19, 2010, at 17:23, Drew Adams wrote:
>>> Won't some builds of 24.0.50.1 have the change and some not?
>>
>> No. The trunk was switched to 24.0.50 only after the 23.x release
>> branch was cut. So all development versions before that would have a
>> version 23.x.y, and all the versions after it will be 24.x.y. The
>> first officially released version that will have it will be 23.2.
>
> OK in this particular case, but the general question remains. If this change had
> been made in a 23.0.50.1 dev version (or whatever the nomenclature is), then
> some such dev versions would have the change and some would not.
Unless you want to start putting bzr revision numbers into the emacs version string (which I think is a bad idea), that's going to be the case. Version numbers like 23.0.50.1 apply to a long string of development revisions. If you need discrete points in time where you can distinguish "fixed before" from "fixed after", that's what releases are for. If you (=> users of your, Drew's, code) want to experiment with development versions, it shouldn't be too much to ask for you to keep fairly current, or at least update before complaining about bugs. (And if you want to ship non-released development versions to your friends or customers, you're on your own.)
Ken
next prev parent reply other threads:[~2010-03-20 2:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 11:23 next emacs version? Drew Adams
2010-03-19 13:22 ` Eli Zaretskii
2010-03-19 17:29 ` Drew Adams
2010-03-19 18:09 ` Eli Zaretskii
2010-03-19 18:46 ` Drew Adams
2010-03-19 19:02 ` Eli Zaretskii
2010-03-19 20:02 ` Drew Adams
2010-03-19 21:15 ` Eli Zaretskii
2010-03-19 21:23 ` Drew Adams
2010-03-20 2:35 ` Ken Raeburn [this message]
2010-03-20 2:39 ` Lennart Borgman
2010-03-20 3:42 ` Óscar Fuentes
2010-03-20 15:51 ` Lennart Borgman
2010-03-20 5:31 ` Ken Raeburn
2010-03-23 2:05 ` Stephen J. Turnbull
2010-03-20 3:38 ` Drew Adams
2010-03-20 5:31 ` Ken Raeburn
2010-03-20 6:51 ` Drew Adams
2010-03-20 5:31 ` Ken Raeburn
2010-03-20 6:51 ` Drew Adams
2010-03-23 2:34 ` Stephen J. Turnbull
2010-03-23 5:01 ` Miles Bader
2010-03-23 5:39 ` Drew Adams
2010-03-20 3:51 ` Jason Rumney
2010-03-20 6:47 ` Drew Adams
2010-03-20 8:39 ` Eli Zaretskii
2010-03-20 14:58 ` Drew Adams
2010-03-20 16:22 ` Eli Zaretskii
2010-03-20 8:11 ` Eli Zaretskii
2010-03-19 20:55 ` Stefan Monnier
2010-03-19 21:16 ` Drew Adams
2010-03-20 19:10 ` Stefan Monnier
2010-03-20 20:29 ` Drew Adams
2010-03-20 21:53 ` Stefan Monnier
2010-03-20 23:09 ` Drew Adams
2010-03-20 23:26 ` Drew Adams
2010-03-22 1:22 ` Stefan Monnier
2010-03-22 7:22 ` Drew Adams
2010-03-22 13:52 ` Stefan Monnier
2010-03-21 21:34 ` Thien-Thi Nguyen
2010-03-21 23:20 ` Drew Adams
2010-03-19 14:52 ` Chong Yidong
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=5E984B3C-4B86-4FA6-8675-4C8501CC2285@raeburn.org \
--to=raeburn@raeburn.org \
--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.