From: No Wayman <iarchivedmywholelife@gmail.com>
To: 70647@debbugs.gnu.org
Cc: Jim Porter <jporterbugs@gmail.com>,
Philip Kaludercic <philipk@posteo.net>,
Eli Zaretskii <eliz@gnu.org>
Subject: bug#70647: 30.0.50; When are :core packages released to GNU ELPA?
Date: Tue, 30 Apr 2024 10:39:38 -0400 [thread overview]
Message-ID: <871q6map91.fsf@gmail.com> (raw)
In-Reply-To: <87mspcmj1g.fsf@gmail.com> (No Wayman's message of "Mon, 29 Apr 2024 08:48:27 -0400")
PK> When a commit modifies the Version header in the main file,
then the PK> state of that commit is used to trigger a new
release, both for core and PK> otherwise.
Where is this documented?
JP> I believe the reason that Eglot's release date is March 31 is
because that's the JP> day that ELPA itself was updated to include
Atom feeds for package updates, JP> which re-published all the
existing packages. See here: JP>
<https://lists.gnu.org/archive/html/emacs-devel/2024-03/msg00777.html>.
PK> There were issues related to some recent changes that re-build
the PK> package tarballs, but the content should have been the
same. But that PK> was a mistake, and not something that should
happen on a regular basis.
Thanks to both of you for the clarification.
This still begs the question of why the publication date is listed
rather than the commit date for the tarball.
Imagine if when searching for a film on IMDB the results presented
the date the IMDB page was last updated rather than the year the
film was released. e.g. "Ghostbusters (2024-04-15)" for the 1984
film. Not a perfect analogy, but it makes the point:
The tarball publishing date, if displayed at all, should be secondary to the commit date.
next prev parent reply other threads:[~2024-04-30 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 12:48 bug#70647: 30.0.50; When are :core packages released to GNU ELPA? No Wayman
2024-04-29 13:17 ` Eli Zaretskii
[not found] ` <87y18wxoll.fsf@gmail.com>
[not found] ` <86sez4qndc.fsf@gnu.org>
[not found] ` <87cyq8dz4h.fsf@gmail.com>
2024-04-29 14:35 ` Eli Zaretskii
2024-04-29 17:55 ` Philip Kaludercic
2024-04-29 18:16 ` Jim Porter
2024-04-30 14:39 ` No Wayman [this message]
2024-05-01 7:29 ` Philip Kaludercic
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=871q6map91.fsf@gmail.com \
--to=iarchivedmywholelife@gmail.com \
--cc=70647@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=philipk@posteo.net \
/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).