Re: plasma-phone-components release process
Sensible enough, but the developers do need to follow Plasma's release schedule then. Changing name after repo freeze shouldn't happen. Nor should adding new dependencies or depending on versions of Frameworks newer than our release specifies https://invent.kde.org/plasma/plasma-mobile/-/commit/9b6ac61802825b0de4e9696fbe2fd511513fedab https://invent.kde.org/plasma/plasma-mobile/-/commit/35a73ba6bbeaaab461d002b5f3aa5ff528a10303 (now reverted) Jonathan
Re: plasma-phone-components release process
On Tue, Feb 8, 2022 at 3:21 PM Jonathan Riddell wrote: > > plasma-phone-components is released as part of Plasma which has an > established release process that we review at the start of each cycle. This > time it was renamed after the repo freeze and after the beta which causes > unpredictable problems in the packaging process. > > Should plasma-phone-components/plasma-mobile continue to be part of the > Plasma release? Or would it be better to move it to Plasma Mobile releases? plasma-mobile is what plasma-phone-components used to be, plasma-mobile should be released with plasma. plasma-mobile (and previously plasma-phone-components) is tightly coupled with certain changes in Plasma and they should go hand in hand. Aleix
plasma-phone-components release process
plasma-phone-components is released as part of Plasma which has an established release process that we review at the start of each cycle. This time it was renamed after the repo freeze and after the beta which causes unpredictable problems in the packaging process. Should plasma-phone-components/plasma-mobile continue to be part of the Plasma release? Or would it be better to move it to Plasma Mobile releases? Jonathan
