[pdm-devel] [RFC PATCH datacenter-manager 0/2] use streaming content api

[Thomas Lamprecht]

Am 09.10.25 um 11:32 schrieb Dominik Csapak:
> one thing i forgot to ask here is:
> 
> how should we handle pbs3/4 compatibility?
> We have IMHO the following options:
> 
> * Implement a fallback in the UI for pbs3
>    can be ok, we could duplicate the panel and drop
>    the old one when pbs3 is not supported anymore?

Hmm, the pdm CLI client got not much love recently, but it is there,
so IMO it would be a bit nicer if the PDM backend abstracts such things
away, at least if doing so is relatively easy (as in, same response
can be generated without much extra work).

> * Implement a fallback in the API for pbs3
>    most robust solution IMO, gui can stay mostly the same, code
>    should not be that much, can also be dropped if we don't
>    want to support pbs3 anymore

That would be an OK option to do.

> * don't support pbs3 at all
>    not really an option i think

No, IMO we really should try very hard to provide at least one version
of backward compat and one version of forward compat (based off Debian
releases).

I.e. PDM released for a Debian release X should support X, X-1 and X+1.
As otherwise upgrades will get a real PITA fast for users, as they would
need to upgrade all in a lockstep.

> * also commit the changes to pbs stable-3 branch
>    maybe the easiest way, but here's the question
>    where we draw the line for older products
>    regarding features/bugs/etc.

The good thing is that we're relatively free to chose and can do so
differently on a case by case basis.

Here I'd find it OK to backport the whole thing, as it can also be
nice for the PBS CLI client (when it actually uses this in the
future). But that only covers latest 3.4, which is fine, but naturally
not _that_ great. So maybe either do both (as of now the master and the
stable-3 branch did not diverge too much, so might be justifiable) or
just do the fallback in the API, which then will also work for even older
PBS releases (not that I want to support these EOL versions actively,
but it's a slight benefit for UX).