Jump to content

Akademy/2023/KDE Frameworks 6 BoF

From KDE Community Wiki

Meeting Notes

KF6 API docs

  • what to do with @since tags?
    • remove 4.x
    • keep 5.x
    • add 6.0 for new stuff
  • find out how API docs are build, and do the same for kf6
    • can Thiago help with that?
    • can we just duplicate the Gitlab job and adjust it?
  • we only want major versions alongside each other, not a more fine-grained version selector

Release Schedule

  • KDE Gear can move up to two months in case of short schedule delays
    • for longer delays this doesn't make sense anymore, move to the next cycle
  • Meeting in September to decide whether we want to commit to the December deadline
  • Gear must not switch master to 6 before the decision point
  • release tooling is in frameworks/5.0 branch of the release-tools repo
  • this needs to be reviewed, possibly modernized and switch to standard tooling and adapted to KF6
    • pre-releases are also there to test all this
    • release process is slightly non-standard for the tagging for release candidates and respins due to missing branching
  • we should have multiple people involved with the release decisions, for better redundancy
    • Gear has a small team cycling through this
  • the actual release process should be more automated
    • for tarball signing we could use Ingo's work for APK signing?
  • Volunteers for the release team: Nico, Alex, David, Harald
    • and Harald looks into the automation
  • first pre-relase will be 5.241.0 to test version bumping, this does not mean any API guarantees
    • we however would want this to be co-installabilty

Major remaining work with impact on external interfaces

  • Kirigami:
    • rework of list items
    • splitting into smaller modules
  • this poses challenges for apps half-way on kf6
  • porting away from KWayland
    • single KF use, so moving that for Plasma is an option, where we can drop it later
  • KWindowSystem
    • there's X11 specific API that might need to be moved away to KX11Extras?

Overlaoded signals

  • clazy warnings are more aggressive than the problem we tried to address
  • should we port those as well or can we ignore those? -> yes, as this behavior is difficult for QML

New Frameworks for KF6

  • KUserFeedback
    • approved for KF6
    • needs to be converted to KF standards
  • KColorScheme, KTextTemplates, KSvg done
  • KMoreStuff is currently still a non-KF library - can this be folded into the few remaining users?
  • QtKeychain can be added later
Retrieved from "https://community.kde.org/index.php?title=Akademy/2023/KDE_Frameworks_6_BoF&oldid=97405"