On Mon, 2021-01-18 at 09:56 +0100, John Paul Adrian Glaubitz wrote:
Hello!
On 1/18/21 5:40 AM, Lubos Kocman wrote:
As you might recall Tomas Chvatal did a complete refresh of python in openSUSE Leap 15.2. This was done out of his initiative and I recall that it took him at least two months to get that done.
Does "refresh" refer to the Python packages, the interpretor or both?
However, SLE 15 SP4 will be a different story as it's the feature release (Tick-tock model). I do expect to have a slightly lower volume of changes compared to SP2 since we're further in the product lifecycle. I'd still appreciate if we could update as much of the Python ecosystem as we can.
Closing the Leap Gap (CtLG) will require that some packages have to be accepted first in SLE, so because of that, the rebuild cycle will be longer. And SLE submission will have to reference some feature tracker.
Isn't that going to delay updates in Leap considerably longer? My personal experience with SLE submissions is that they tend to take much longer than Leap submissions due to the necessary QA steps involved.
Well keep in mind that even in Leap 15.2 updates to packages with SLE origin had to be submitted from SLE-side. So I don't see much of a change to be honest. We used SLE workarounds for temporary forks and such approach would be doable even today while keeping packages forked in openSUSE:Leap:15.3 project, but in general we should avoid it.
Adrian
-- Lubos Kocman Release Manager openSUSE Leap SUSE LINUX, s.r.o. Krizikova 148/34 tel: +49 173 5876850 186 00 Praha 8 http://www.suse.com Czech Republic