From: Glenn Morris <rgm@gnu.org>
To: Bill Wohler <wohler@newt.com>
Cc: emacs-devel@gnu.org
Subject: Re: Status of trunk
Date: Wed, 23 Jul 2014 00:42:07 -0400 [thread overview]
Message-ID: <8ofvhs7kkg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87tx68lo4u.fsf@olgas.newt.com> (Bill Wohler's message of "Tue, 22 Jul 2014 21:01:21 -0700")
Bill Wohler wrote:
> I'm guessing that the current policy is that emacs-24 is used for 24.4
> fixes,
Yes.
> which are later merged to trunk by Glenn,
(By anyone who feels like it, but often no-one seems to feel like it.)
> and that trunk is open for business.
Yes.
> Also, we have a couple of MH-E bugs on SourceForge related to
> compatibility with new nmh releases (1.5 and more recently 1.6). Would
> these qualify for checking in on the emacs-24 branch?
Not up to me, but showing the diff (it is not huge) would help to answer that.
Technically speaking, no; ref:
http://lists.gnu.org/archive/html/emacs-devel/2014-05/msg00309.html
but if the changes are simple, probably yes. (But again, not up to me.)
> Are we still targeting a winter release?
Ha. There is no "target" AFAIK.
(Some people expressed a desire for more frequent releases, and I think
the phrase "every 6 months" was mentioned. The 24.4 feature freeze began
7 months ago...
There's no visible progress with any of the outstanding important bugs,
and no-one doing any serious documentation improvements.
Bug reports show that many people are using trunk rather than emacs-24.
So in summary I don't know when the release will be.
I hope it is a bit sooner than winter.)
next prev parent reply other threads:[~2014-07-23 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 4:01 Status of trunk Bill Wohler
2014-07-23 4:42 ` Glenn Morris [this message]
2014-07-23 4:53 ` Bill Wohler
2014-07-23 4:58 ` Glenn Morris
2014-07-23 5:45 ` Bill Wohler
2014-08-09 17:11 ` Stefan Monnier
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=8ofvhs7kkg.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wohler@newt.com \
/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.