From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: No Wayman <iarchivedmywholelife@gmail.com>, 70647@debbugs.gnu.org
Subject: bug#70647: 30.0.50; When are :core packages released to GNU ELPA?
Date: Mon, 29 Apr 2024 17:55:55 +0000 [thread overview]
Message-ID: <87y18wkq8k.fsf@posteo.net> (raw)
In-Reply-To: <86r0eoqlrn.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 29 Apr 2024 17:35:56 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: No Wayman <iarchivedmywholelife@gmail.com>
>> Cc: Philip Kaludercic <philipk@posteo.net>
>> Date: Mon, 29 Apr 2024 10:25:50 -0400
>>
>> Eli Zaretskii <eliz@gnu.org> 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 <iarchivedmywholelife@gmail.com> Date: Mon, 29
>> >> Apr 2024 09:52:54 -0400 Eli Zaretskii <eliz@gnu.org> 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.
When a commit modifies the Version header in the main file, then the
state of that commit is used to trigger a new release, both for core and
otherwise.
>> >> - 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/
These are rebuilt on every commit. The intended audience IMO are
developers here though, so that they can easily preview the state of
packages.
>> > <h1> GNU-devel ELPA Packages </h1>
>>
>> If that's not what it's called, then the website should be updated
>> to reflect the preferred name.
The name is fine. I am just guessing that it is not something that Eli
has to deal with that often.
>> > 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.
There were issues related to some recent changes that re-build the
package tarballs, but the content should have been the same. But that
was a mistake, and not something that should happen on a regular basis.
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-04-29 17:55 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 [this message]
2024-04-29 18:16 ` Jim Porter
2024-04-30 14:39 ` No Wayman
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=87y18wkq8k.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=70647@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=iarchivedmywholelife@gmail.com \
/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).