unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bastien <bzg@gnu.org>
Cc: 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 18:45:29 +0200	[thread overview]
Message-ID: <83pmdmg85y.fsf@gnu.org> (raw)
In-Reply-To: <87fsejlzln.fsf@gnu.org> (message from Bastien on Wed, 16 Nov 2022 15:53:56 +0100)

> From: Bastien <bzg@gnu.org>
> Cc: larsi@gnus.org,  emacs-devel@gnu.org,  yantar92@gmail.com,  kyle@kyleam.com
> Date: Wed, 16 Nov 2022 15:53:56 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > From the Emacs POV, what matters is that you
> > don't add new features to Org that is part of the branch after the
> > branching point.  
> 
> Okay, thanks.
> 
> Org 9.6 comes with new features compared to Org 9.5.5.  We will do 
> our best to release 9.6 before the end of this month, and then fix
> bugs from 9.6 to 9.6.1 in the release branch.

SGTM, thanks.



      reply	other threads:[~2022-11-16 16:45 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
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 [this message]

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=83pmdmg85y.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=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).