From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#70647: 30.0.50; When are :core packages released to GNU ELPA? Date: Mon, 29 Apr 2024 17:35:56 +0300 Message-ID: <86r0eoqlrn.fsf@gnu.org> References: <87mspcmj1g.fsf@gmail.com> <86wmogqper.fsf@gnu.org> <87y18wxoll.fsf@gmail.com> <86sez4qndc.fsf@gnu.org> <87cyq8dz4h.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37872"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, 70647@debbugs.gnu.org To: No Wayman Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Apr 29 16:37:03 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@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 ) id 1s1S7q-0009dN-SO for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 29 Apr 2024 16:37:02 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s1S7Y-0006tw-Vj; Mon, 29 Apr 2024 10:36:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s1S7X-0006tX-B3 for bug-gnu-emacs@gnu.org; Mon, 29 Apr 2024 10:36:43 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1s1S7X-0004lP-0S for bug-gnu-emacs@gnu.org; Mon, 29 Apr 2024 10:36:43 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1s1S7q-0003XJ-GA for bug-gnu-emacs@gnu.org; Mon, 29 Apr 2024 10:37:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 29 Apr 2024 14:37:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 70647 X-GNU-PR-Package: emacs Original-Received: via spool by 70647-submit@debbugs.gnu.org id=B70647.171440139113583 (code B ref 70647); Mon, 29 Apr 2024 14:37:02 +0000 Original-Received: (at 70647) by debbugs.gnu.org; 29 Apr 2024 14:36:31 +0000 Original-Received: from localhost ([127.0.0.1]:57572 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s1S7L-0003X1-5W for submit@debbugs.gnu.org; Mon, 29 Apr 2024 10:36:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34190) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s1S7G-0003Wr-34 for 70647@debbugs.gnu.org; Mon, 29 Apr 2024 10:36:29 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s1S6p-0004Xx-N4; Mon, 29 Apr 2024 10:35:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=6fklFXdGH5yCrHIq6NVsPaOEGf3lpXD2Vhg5m0kCmFA=; b=nUuvVU8f9dRP bbQUIZj2wMsqQNTPvp7xCi5Igyv+FAgLim+sy/VO1pWLfd2CrcCkXmGnaJL0QELjjqKLNfljczOQo llHquIJVtLmN8NSU7z6110lWUK+neohN5Iq1X/loDRWL/iRC62r+jbGzIV2WyHOuxKDtTlnKljhuM niSgSbiSNydRYSU7cb2QycCFv6jb4c0HJrpvjnMTcPoPgq7YtYVx71f81ffvfOvYy67fTrJHENWPk ntiHiSsT4O0yWPtjKE4EzwGKnOEOgBkiUbn6RQ8m0QShmAZOPJg1lHL356C8yx4l2HkEA5AZFuJp/ VqFz8emTa+JHqFfM+DPKQA==; In-Reply-To: <87cyq8dz4h.fsf@gmail.com> (message from No Wayman on Mon, 29 Apr 2024 10:25:50 -0400) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:284151 Archived-At: > From: No Wayman > Cc: Philip Kaludercic > Date: Mon, 29 Apr 2024 10:25:50 -0400 > > Eli Zaretskii writes: > > > [Why private email?] > > Apologies. Must've fat-fingered my reply key binding. Looks like you did it again. Please use Reply All, to have the bug tracker CC'ed. Resending to the bug tracker. > >> From: No Wayman Date: Mon, 29 > >> Apr 2024 09:52:54 -0400 Eli Zaretskii writes: > >> > >> > Are there any differences in the code between version 1.17 on > >> > ELPA and the Eglot code as of commit b014bca833a. > >> I would hope not. Otherwise the version information is > >> incorrect. > > > > Then why is this a problem? File time stamps are immaterial > > with modern VCSes. > > The problem is it's confusing. > When is the "release date" of eglot 1.17? > The date of the commit which bumped the Version header? > The date of some other action which triggered an ELPA build? > If file timestamps are indeed immaterial, than it would make the > most sense to stick with the commit date which bumped the Version > header. > That does not appear to be the case. > > >> > What would you like to be documented? > >> - What triggers a package build/release on GNU ELPA in all > >> cases > >> (:core or otherwise)? > > > > Philip will tell, but I'm not surprised, given that this is a > > volunteer project. > > > >> - What triggers a package build/release on GNU-devel ELPA. > > > > What is "GNU-devel ELPA"? > > Forgive me if I misspoke, but: https://elpa.gnu.org/devel/ > > >

GNU-devel ELPA Packages

> > If that's not what it's called, then the website should be updated > to reflect the preferred name. > > > I don't even understand the problem you see here. > > I've seen other package maintainers confused about what/when a > rebuild is triggered. I have reports on Elpaca's issue tracker > where users are confused by the release dates listed on GNU ELPA's > websites. I myself am not 100% sure I understand all cases that > trigger builds. The issue is I could not find a place where this > is all clearly documented. >