emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Bastien Guerry <bzg@gnu.org>
Cc: Ihor Radchenko <yantar92@gmail.com>,
	Max Nikulin <manikulin@gmail.com>,
	emacs-orgmode@gnu.org
Subject: Re: [PATCH] Delete some Emacs 24 compat code
Date: Sun, 17 Jul 2022 18:23:16 -0700	[thread overview]
Message-ID: <CAJcAo8uL4C9GDJHGm9q3cFYDzU2MAq97MSHU6=bMGES0BEkFaQ@mail.gmail.com> (raw)
In-Reply-To: <874jzg5bg7.fsf@gnu.org>

great!  one of the things i like about org is the close attention to
user-oriented nature of maintenance.  everything on mailing list,
maint branch, compilation warnings few, etc.  this is more of the same
user-oriented goodness.

i have noticed an impressive amount of bug fixing, code improvement,
documentation improvement type of activity recently and it is greatly
appreciated.

it's a kind of user-openness attitude that i think improves the
software.  by analogy, kind of like including science-oriented
research subjects to get knowledge and noticing and priorities instead
of imposing an arbitrary wall.


On 7/17/22, Bastien Guerry <bzg@gnu.org> wrote:
> Hi Ihor and Samuel,
>
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> In addition, we might also announce the oldest supported Emacs version
>> in https://orgmode.org/Changes.html.
>
> The current release of Org is meant to be compatible with the last
> three major releases of Emacs.  That is, as of now, 28, 27, 26.
>
> See https://orgmode.org/worg/org-maintenance.html#emacs-compatibility
>
> If the current release is de facto compatible with older Emacsen and
> a new release will change this, yes, let's announce it in the release
> notes.
>
> We can also send an email to the list using the "X-Woof-Change" to
> announce this upcoming change for the upcoming release.
>
> For example, the current release of Org (9.5.4) is compatible with
> Emacs 25.1, as Ihor noted.  This is older than Emacs 26.  If for some
> reason Org 9.6 only supports Emacs >=26, let's announce it on the list
> and add an entry in etc/ORG-NEWS and orgmode.org/Changes.html.
>
> I think doing this manually is fine.
>
> Bug fixes from the maint branch should never change the compatibility
> status of Org.
>
> Evolutions on the master branch can change the compatibility, but not
> break the global promise of being compatible with the last three major
> releases of Emacs.
>
> --
>  Bastien
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com


  reply	other threads:[~2022-07-18  1:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 11:19 [PATCH] Delete some Emacs 24 compat code Stefan Kangas
2022-06-30 13:36 ` Ihor Radchenko
2022-06-30 13:39   ` Ihor Radchenko
2022-06-30 15:25   ` Stefan Kangas
2022-07-02  4:11     ` Ihor Radchenko
2022-06-30 15:25 ` Max Nikulin
2022-06-30 15:47   ` Ihor Radchenko
2022-06-30 22:46     ` Samuel Wales
2022-07-01  2:45       ` Ihor Radchenko
2022-07-01  3:11         ` Samuel Wales
2022-07-01  4:00           ` Tim Cross
2022-07-01  4:44             ` Samuel Wales
2022-07-17  9:35         ` Bastien Guerry
2022-07-18  1:23           ` Samuel Wales [this message]
2022-07-31 12:54           ` Ihor Radchenko
2022-08-08 15:46             ` Bastien
2022-08-08 22:12               ` Tim Cross
2022-08-09  0:41                 ` Bastien
2022-08-10 11:50                   ` Ihor Radchenko
2022-08-11 10:23                     ` Bastien
2022-08-11 11:53                       ` Ihor Radchenko
2022-08-12  6:30                         ` Bastien
2022-08-09 15:58               ` Max Nikulin
2022-08-10  0:06                 ` Tim Cross
2022-08-10  0:59                 ` Tom Gillespie
2022-08-10  1:13                   ` Tim Cross
2022-08-10  4:55                     ` Tom Gillespie
2022-08-10 14:18                       ` Tim Cross
2022-08-11  2:59                         ` Samuel Wales
2022-08-11  5:34                           ` Tim Cross
2022-08-11  5:56                           ` Tim Cross

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJcAo8uL4C9GDJHGm9q3cFYDzU2MAq97MSHU6=bMGES0BEkFaQ@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.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/org-mode.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).