From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: jwiegley@gmail.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Getting start on Emacs 25.2
Date: Thu, 22 Sep 2016 18:15:59 +0300 [thread overview]
Message-ID: <83r38cdky8.fsf@gnu.org> (raw)
In-Reply-To: <87zin0149t.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Cc: John Wiegley <jwiegley@gmail.com>, rms@gnu.org, emacs-devel@gnu.org
> Date: Thu, 22 Sep 2016 13:57:02 +0100
>
> >> I think 25.2 should be a bugfix only release, happening very soon.
> >
> > Then we'd need a good definition of what changes constitute a
> > "bugfix".
>
> I don't think anyone has managed that for any form of software. A
> working rule of thumb is the best we are likely to get, but that should
> be enough.
There's no differences between the two, for our purposes in this
case. Rule of thumb is the same as definition in this context, and
both need to be good. Otherwise, we will either release 25.2 that
won't be an improvement wrt 25.1, or will waste a lot of time and
energy arguing just what changes to commit to the release branch.
next prev parent reply other threads:[~2016-09-22 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 2:45 Getting start on Emacs 25.2 John Wiegley
2016-09-18 14:37 ` Eli Zaretskii
2016-09-18 16:28 ` Stefan Monnier
2016-09-18 19:41 ` John Wiegley
2016-09-18 21:23 ` Nicolas Petton
2016-09-19 6:37 ` Andreas Röhler
2016-09-19 16:37 ` Eli Zaretskii
2016-09-22 12:57 ` Phillip Lord
2016-09-22 15:15 ` Eli Zaretskii [this message]
2016-09-18 20:48 ` Phillip Lord
2016-09-19 7:09 ` Michael Albinus
2016-09-19 8:52 ` Phillip Lord
2016-09-29 19:23 ` John Wiegley
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=83r38cdky8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=phillip.lord@russet.org.uk \
--cc=rms@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).