Re: Q: Can we follow LibO upstream releases in stable (not backports repo)?
Am 28. Oktober 2019 07:05:51 MEZ schrieb Hideki Yamane <henrich@iijmio-mail.jp>:
>Hi,
>
> LibreOffice upstream based on time-based release model(*) and always
> releases two versions for users, one is newest release and older one
> is more stable one.
>
> *) https://wiki.documentfoundation.org/ReleasePlan
>
> It seems that is better to follow it in stable, IMHO.
>
>
>Pros)
> - Users are forced to use obsolete version if they don't have
> enough technical knowledge&skill. We can improve it, deliver
> more value to users.
> - Better reputation for Debian stable :)
> - 6.1.x is EOLed, so backporting security fix becomes more harder
> than based on 6.3.x
>
>Cons)
> - It introduces UI/feature changes into stable (but it's acceptable
> as well as firefox-esr, IMO).
>
>
> Is there any blocker for it?
Hi,
I obviously know about the time based release model.
There is no big burden for security always. Often it just works with minor tweaks.
oldstable is different and wasting time and s totally obsolete 4.3.3 as in oldoldstable for LTS is a different story, though..
So you want 6.3 there? It already will be eol next may.
What if you get new library dependencies? Use internal version? Package them newly in stable with SONAME changes? What if a new version requires a newer gcc (happens, here with gcc = 9 due to c++20 etc) or Java (happens)?
What if you need NEW like in 6.4?
What if you have API changes? LO is not only desktop but also API/scriptable.
This comes up all the time, and my answer is and will be no.
Adding backports and installing from there is trivial.
That firefox-esr opened Pandora's box for this is already bad.
See e.g.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820350 abd
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914619
where this ended up in the BTS already...
Regards
Rene
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Reply to: