From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Delete some Emacs 24 compat code
Date: Fri, 01 Jul 2022 14:00:23 +1000 [thread overview]
Message-ID: <87r135xy65.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8v+M9fKYx06_bdpAGqst4KA6iD7k359_GR97BKXasrQWQ@mail.gmail.com>
Samuel Wales <samologist@gmail.com> writes:
> i use git version, not elpa, so for me, mailing list could tip me off
> as early as possible, but not too early, if it said in email subject
> header line that in a known upcoming release, it has been decided that
> a specified emacs version will no longer be supported [note: i presume
> and hope this would not occur in just a plain git update for such a
> thing but would get a release that gets noted in email and get that
> advance notice],
>
> then upon seeig such email i can stop pulling from git until i am able
> to upgrade emacs. [lots of stuff takes lots and lots of time for me
> in my case] idk if practical, but just saying what seems like it
> would be useful to me.
>
> i would then stay at something reasonably close to the first release
> that does not support that version fo emacs.
>
While what your asking for may sound reasonable, I don't think it is
practical. There is no sudden decision to stop supporting a version in
the sense that suddenly, at that point, the version is no longer
supported. We really only know that a past version is no longer
supported when it stops working and is more than 2 releases behind the
current Emacs version (any less and it is a bug which will get fixed).
The supported version policy has already been communicated on this
list. That policy will not change without notice, so you know exactly
what is supported at all times.
There is no precise point where we can send out a message saying a
version is no longer supported. Best that can be done is say that any
Emacs version older than two releases behind the current stable release
is no longer supported. That doesn't mean it won't work, it just means
if there are problems, they won't be fixed and there should be no
expectation it will work if your running an unsupported Emacs version.
Thing is, no testing is done against older versions, so it isn't always
clear precisely when org stops working with an older unsupported
version.
Current stable version is 28. Therefore, if your running Emacs 25 or
earlier, you *should not* pull updates from git as they may not be
compatible with your Emacs version. When Emacs 29 is released, stop
pulling from git if your running Emacs <= version 26.
Of course, none of this is a big issue as you do build from git. Should
you find your most recent pull is no longer compatible with the version
of Emacs your running, it is trivial to revert to the version you were
running before - you just need to do a checkout for the earlier
revision and rebuild. As pointed out elsewhere in this thread,
package.el has minimum version spec, so this isn't an issue for
package.el users.
next prev parent reply other threads:[~2022-07-01 4:19 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 [this message]
2022-07-01 4:44 ` Samuel Wales
2022-07-17 9:35 ` Bastien Guerry
2022-07-18 1:23 ` Samuel Wales
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=87r135xy65.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@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/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).