unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: bzg@gnu.org, larsi@gnus.org, emacs-devel@gnu.org,
	yantar92@gmail.com, kyle@kyleam.com
Subject: Re: Tentative release schedule for Emacs 29.1
Date: Wed, 16 Nov 2022 15:12:23 +0200	[thread overview]
Message-ID: <83iljfgi14.fsf@gnu.org> (raw)
In-Reply-To: <87a64rfqm6.fsf@yahoo.com> (message from Po Lu on Wed, 16 Nov 2022 12:52:17 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>,  emacs-devel@gnu.org,  Ihor
>  Radchenko <yantar92@gmail.com>,  Kyle Meyer <kyle@kyleam.com>
> Date: Wed, 16 Nov 2022 12:52:17 +0800
> 
> I think we should not cut the branch until bug#59183 is fixed.  I run
> into that serious crash every few days.

We will not release Emacs 29.1 with that bug, that's for sure.  But I
don't want to wait for its solution before cutting the release branch,
since we can continue working on it after the branching.

If your crashes are like the one reported there, how about if you
disable mouse-highlight as a temporary workaround?



  reply	other threads:[~2022-11-16 13:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 15:03 Tentative release schedule for Emacs 29.1 Lars Ingebrigtsen
2022-09-24  6:44 ` Bastien
2022-09-24 10:32   ` Lars Ingebrigtsen
2022-09-24 16:24     ` Bastien
2022-11-16  4:43     ` Bastien
2022-11-16  4:52       ` Po Lu
2022-11-16 13:12         ` Eli Zaretskii [this message]
2022-11-16 13:26           ` Po Lu
2022-11-16 13:52             ` Eli Zaretskii
2022-11-16 13:51           ` Stefan Monnier
2022-11-16 13:59             ` Eli Zaretskii
2022-11-16 13:09       ` Eli Zaretskii
2022-11-16 13:23         ` Bastien
2022-11-16 13:50           ` Eli Zaretskii
2022-11-16 14:53             ` Bastien
2022-11-16 16:45               ` Eli Zaretskii

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=83iljfgi14.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bzg@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --cc=yantar92@gmail.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 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).