Can we make a 1.930 official release?
okybaca opened this issue · 5 comments
"Official" release of YaCy hadn't been made for quite a while.
Latest release available on yacy.net is 1.924 while 1.930 is available on github and has plenty of improvements (and a new version on both solr and Java). People still download and use 1.924 and Mac and Windows folks are condemned to use the old version. Not everyone is able to compile own brew out of github sources.
How the official release can be made, @Orbiter?
I understand that making Windows and Mac release can be quite a process. But could you at least describe that and make a sort of checklist, so it becomes more easy? Or, if there is some trouble, ask for help of others?
I'm also not sure what are other "official" release packages. Docker? Debian package (as descried here)? Who admins that and how?
The best way would be to have a releasing process described in release.md or something, so anyone could be guided to do that and @Orbiter doesn't have so much overhead, while working on other projects.
There are also a lot of questions or bugs under releasing label in issues.
I have been testing Amazon Java, Linux and Windows.
With Windows You can possibly have a msi silently installed.
Has anyone else tested the Amazon java?
More info on. Java
I uploaded a 1.93 release here: https://download.yacy.net/yacy_v1.930_202405130205_59c0cb0f3.tar.gz
Meanwhile I moved on: latest release number is 1.94 containing a solr 9.0 update.
Releases become somehow "official" by using the corresponding download on the download page. The problem here is that I want to abandon this principle and make liquid CI/CD releases only in the future; this will cause publications automatically on
https://release.yacy.net/
and
Dockerhub.
This process is already in place. I actually make and increase these numbers mainly for a better handling but not doing things "official".
Yes, great, @Orbiter !
But what about Windows and Mac release? How to build them?
Only difference between automatic github build and official release is code signing by 'official' key, is that so?
(then, nodes using 'only accept signed files' in autoupdate won't be updated without that).
And, also, there is option to 'tag' releases on github, which was used in the past, but ended with 1.92. Some people call for that: #348 . For example for various solr versions, it may be useful to be able to go back for a tagged older release.
Tagging a Release is like 10 clicks on github.