Akademy 2021 BoF Notes

[Jonathan Riddell]

https://invent.kde.org/teams/neon/-/wikis/Akademy2021

* i18n for ktuberling etc broken
  * broken in translations in websvn and hacked around to disable on
release tars
  * talk to sr translators and release dudes about fixing not hacking
* 21.04 LTS transition
  * Go to UDS (or whatever it is now) to work out what's new
  * Follow same process as move to 20.04 LTS
  * Move to QA faster
  * Smoother process for hardware enablement linux builds?
  * unlikely to change release update tool to use offline updates
* digikam snap dozens of builds?
  * it's watching the KDE repo because that was a trigger before
  * solution: remove job history and reset country in jenkins
* snap back to release builds
  * consider putting snapcraft.yaml files in their repo - consistent with
flatpak and makes it easier for app devs to care
  * https://invent.kde.org/packaging/snapcraft-kde-applications
* Move to invent gitlab?
  * Blocked on jobs depending on another job being able to block it.
Consider filing a but with Gitlab folks to request.
* KDE gear releases break KDE git?
  * Our builds overloaded invent one time.  It hasn't been a problem before
or since.  Solution would be to constrain invent so it doesn't overload the
server and constrain other services so they don't overload invent.
* Qt 6 build
  * Update the monolithic build to 6.1 and blog
  * Get testers https://build.neon.kde.org/job/focal_unstable_sitter_qt6/
(ping Mêven to test)
* KF6 builds
  * Consider making Neon/unstable_kf6 branches with updates packaging for
kf6 branches and updating packaging and building.
  * Try to coordinate with Debian to minimise merging
* why not full automated release building?
  * jobs for jenkins_retry.rb for frameworks, plasma, gear, plamo
  * More retry mechanism needed for watchers
  * More checking of product build jobs until timeout
* review breakage incidents? qt? pulseaudio?
  * A library package must not ever have a transitional when updating
soversion
  * KDE's Qt branches are not treated as a cohesive release product, we are
concerned this might break in future with Qt's tight ABI coupling.  It's
unclear if or when KDE's Qt branches will update soversion.  It's unclear
how they will sync with Qt LTS releases.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/neon/attachments/20210622/f5bebab6/attachment.htm>