unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: emacs-devel@gnu.org
Subject: Re: Stability of project.el
Date: Tue, 11 Jul 2023 05:26:35 +0000	[thread overview]
Message-ID: <87wmz7auic.fsf@posteo.net> (raw)
In-Reply-To: <1b2546a1-f0e5-7f6f-4853-21bdf746d6c9@gutov.dev> (Dmitry Gutov's message of "Tue, 11 Jul 2023 04:27:51 +0300")

Dmitry Gutov <dmitry@gutov.dev> writes:

> Hi Philip,
>
> On 10/07/2023 21:53, Philip Kaludercic wrote:
>> The commentary section for project.el still begins with
>> --8<---------------cut here---------------start------------->8---
>> ;; NOTE: The project API is still experimental and can change in major,
>> ;; backward-incompatible ways.  Everyone is encouraged to try it, and
>> ;; report to us any problems or use cases we hadn't anticipated, by
>> ;; sending an email to emacs-devel, or `M-x report-emacs-bug'.
>> --8<---------------cut here---------------end--------------->8---
>> Is this still true, or would it be warranted to remove it just like
>> we
>> did for Xref a few years ago (9a15694a45), perhaps even in time for
>> Emacs 29?
>
> I think that's a good idea. Even if there still some less-than-ideal
> bits, we need to maintain it backward-compatibly, given the age.

Great.  Should the major version number also be bumped?

> And documentation-only changes should still be good for Emacs 29.

Eli, what do you say?



  reply	other threads:[~2023-07-11  5:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 18:53 Stability of project.el Philip Kaludercic
2023-07-11  1:27 ` Dmitry Gutov
2023-07-11  5:26   ` Philip Kaludercic [this message]
2023-07-11 12:02     ` Eli Zaretskii
2023-07-12  1:59     ` Dmitry Gutov
2023-08-04 10:35   ` Stefan Kangas
2023-08-04 15:42     ` Dmitry Gutov

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=87wmz7auic.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=dmitry@gutov.dev \
    --cc=emacs-devel@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.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).