From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Obtaining a database of new functionality per Emacs version
Date: Mon, 07 Dec 2020 17:34:31 +0200
Message-ID: <83360haauw.fsf@gnu.org>
References: <X84ewTWkQRrdHJhK@odonien.localdomain>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="2318"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: emacs-devel@gnu.org
To: Vasilij Schneidermann <mail@vasilij.de>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 07 16:37:37 2020
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1kmIa0-0000VZ-TB
	for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Dec 2020 16:37:36 +0100
Original-Received: from localhost ([::1]:60610 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1kmIa0-0000Ss-01
	for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Dec 2020 10:37:36 -0500
Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43260)
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1kmIXE-0006IV-4j
 for emacs-devel@gnu.org; Mon, 07 Dec 2020 10:34:44 -0500
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57297)
 by eggs.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <eliz@gnu.org>)
 id 1kmIXD-0007RE-26; Mon, 07 Dec 2020 10:34:43 -0500
Original-Received: from [176.228.60.248] (port=4834 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@gnu.org>)
 id 1kmIXA-0005zz-5i; Mon, 07 Dec 2020 10:34:42 -0500
In-Reply-To: <X84ewTWkQRrdHJhK@odonien.localdomain> (message from Vasilij
 Schneidermann on Mon, 7 Dec 2020 13:23:29 +0100)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: "Emacs-devel"
 <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Xref: news.gmane.io gmane.emacs.devel:260488
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/260488>

> Date: Mon, 7 Dec 2020 13:23:29 +0100
> From: Vasilij Schneidermann <mail@vasilij.de>
> 
> - Relying on metadata from custom.el: Works on customizables only.
> - Combing through NEWS files: Not machine-readable, tedious, prone to
>   mistakes (not all new functionality is marked as such, for example
>   there's renames like `with-connection-local-profiles` to
>   `with-connection-local-variables`).

Renames without leaving an alias behind can only be legitimately done
if the original variable was not yet released in any version;
otherwise it's a bug that should be reported and fixed ASAP.

> - Combing through CHANGELOG: Not machine-readable either, tedious, not
>   cleanly separated by versions, seemingly the wrong data source to
>   consult.
> - Launching an Emacs process, loading up all functionality, dumping all
>   symbols, diffing against the output of an Emacs process of an older
>   version, filtering out symbols introduced by our own code: This might
>   just work (loading up functionality has side effects), but surely
>   there's a better way, right?
> 
> Anything obvious I'm overlooking?

Did you try "make TAGS" in the top-level directory, followed by
searching the TAGS files?

> Should there perhaps be an effort towards documenting versioned
> public API?

Manually or automatically?  If manually, the result will be as
accurate and comprehensive as NEWS.  If automatically, please tell
what kind of implementation you have in mind.