Le 14/05/2022 à 16:44, Romain Beauxis a écrit :
[snip Rolling releases]
OK Romain… This looks like a mess to me.
I understand the logic behind your choice, and I'm all for clarifying
the maintained "current" branch, and the dev one, and I don't mind at
all you specifying clever ways of putting it in our hands (and I'm quite
thankful for all your work in general).
I do mind that with every "major" release, URL pattern changes, naming
changes, and every time, instead on focusing on making sure I got the
latest craze from new operators, language specs… I'm kinda stuck on
automating the upgrade process. Cool url don't changes, someone once
said, and once again (it happened with 1.3, 1.4, and now 2.x, twice…), I
need to understand how you release the binary packages, and make sure
that my ansible scripts (that I'd be willing to share, if they didn't
break every release ;)) fetch the 1) correct/latest stable version,
related to my scripts, 2) don't hit a 404…
I don't mind adapting, but this is getting on my nerve, and I'm afraid
you'll play the same trick on us next time now… Chat échaudé craint
l'eau froide ;)
So now, I need to track a git hash, for a stable release, that's it? So
if I run CI / tests against my scripts / live setups, I can add a
variable setting the hash, and be "assured" it will still be there 2
months later? ;)
It's OK for me to add that on my side, but could we please stop changing
the rules every now and then? I mean, I may not have engineered it the
best way, but this is where I was at:
deb: "https://github.com/savonet/liquidsoap/releases/download/v{{
liq_version }}/liquidsoap{{ liq_github_version }}-{{
ansible_distribution | lower }}-{{ (ansible_distribution_release ==
'buster' ) | ternary('stable', ansible_distribution_release) }}-{{
liq_arch_version }}.deb"
And even then, I had liq_github_version format that changed between v1
and v2, as well as arch_version… or horrible hacks like that that
followed all releases… (happily enough, I love the stable branch, so I
don't track that many versions at once ;))
Anyway, that was a rant longer than I wanted it to be… But my main
problem is: I need a way to url-target a release (at a given time, not a
rolling one), so I can run my tests, make sure things run smoothly, and
gradually upgrade my scripts from v(n-1) to v(n), which may occur months
after the first tests, weeks (hopefully, at most) after a release. And
I'm fine with targetting a v x.y.z-hash but I'd be grateful if with 3.x
we didn't need to once again adapt to a new release / url / tag scheme...
Cheers,
Gilou
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
