Hi Chris, Thanks for the info, that's useful. Could you monitor these logs to have a rough estimate per month? Are we around 10, 100, 1000? Cheers, Jonathan Le mar. 7 nov. 2023 à 22:26, Chris Cormack via Koha-devel < koha-devel@lists.koha-community.org> a écrit :

Morning

People are still downloading them, looking at the access logs on the server

From this morning there are a few downloads, for example

[07/Nov/2023:04:17:18 +0000] "GET /koha-22.11.10.tar.gz HTTP/1.1" 200 99643874 "https://download.koha-community.org/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36"

[07/Nov/2023:04:46:02 +0000] "GET /koha-latest.tar.gz HTTP/1.1" 200 100758420 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 Edg/119.0.0.0"

I think it is worth keeping the. I doubt anyone who is using them will be on the koha-devel list though, or maybe even the main list, so download statistics is probably the best metric we have.

Chris

On 8/11/23 09:22, Jonathan Druart via Koha-devel wrote:

...

Hi,

I am suggesting removing the tarball from our release process. I don't think anybody is using it anyway. It's extra work for RMaints, and it does not seem necessary. I am going to suggest removing the po files from the Koha src code starting from November releases, and that will require yet an extra (unnecessary?) step to embed the po files to generate the tarball.

What do you think?

Cheers, Jonathan

_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/

-- Kaihuawaere Matihiko (he/him) Kāi Tahu, Kāti Māmoe, Waitaha Catalyst.Net Limited - Expert Open Source Solutions 027 4500789 chrisc@catalyst.net.nz _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/

Hi :) To still provide tarballs without release process steps to maintain and perform every time there is still this: https://git.koha-community.org/Koha-community/Koha/tags No files for signature though. Though, where can people find the rmaint public keys anyway? So I'm not sure anyone uses this to get Koha. Hum, after trying, the forge is a bit weird about the tarball feature, it seems the link doesn't work. But after like 30 sec of processing it works. (might need to click again) And subsequent clicks work directly. Direct link still work though: https://git.koha-community.org/Koha-community/Koha/archive/v23.05.05.tar.gz Oh no when using the direct link the 1st time, it ends up in a 500 error and next try it works. (timeout?) So having the release process get the tarball URL to trigger the generation would work. Still a bit wack but could be an alternative to keep tarballs without much work. (same behavior on Forgejo, tested on codeberg.org but it's likely with a fast enough server the request doesn't timeout or something) Cheers, -- Victor Grousset/tuxayo

On 23-11-10 08:50, Jonathan Druart wrote:

You missed the original request, Victor. The .po files will be missing from the src and so the git extract won't be enough.

Indeed! Read it and forgot it when looking at how to get them from the forge...

I think we better need to have a job triggered on tags pushed that will build and push the .tar.gz files.

If there isn't much usage maybe it's ok to have one tarball for Koha itself and one for the .po files. And if there are requests for a complete tarball then maybe do a job. Not sure about the tarball usage but if it's for manual installs then having a step to extract the .po tarball in the directory of koha could be okay for users. Cheers, -- Victor Grousset/tuxayo

Yes, you're correct. We need to spend some time reviewing our build pipeline process and distribution mechanisms. I can spend time on that right after the release. Have a great weekend, and enjoy your holiday, US people. El vie, 10 nov 2023 a las 12:15, Jonathan Druart (< jonathan.druart@bugs.koha-community.org>) escribió:

But it won't embed po files. Please see my reply to Victor.

...

Gitlab allows you to download a tar.gz, and commits are GPG signed already. Maybe we can change the workflow. We should take some time to think about it next cycle. El mar, 7 nov 2023 a las 17:22, Jonathan Druart via Koha-devel (< koha-devel@lists.koha-community.org>) escribió:

...

Hi, I am suggesting removing the tarball from our release process. I don't

Le vendredi 10 novembre 2023, Tomas Cohen Arazi <tomascohen@gmail.com> a écrit : think anybody is using it anyway.

...

...

It's extra work for RMaints, and it does not seem necessary. I am going to suggest removing the po files from the Koha src code starting from November releases, and that will require yet an extra (unnecessary?) step to embed the po files to generate the tarball. What do you think? Cheers, Jonathan _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/

-- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

-- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F