Re: Synchronized release schedule for Plasma
On Tue, Nov 24, 2020 at 5:10 PM David Edmundson wrote: > As distribution package maintainers, we would like Plasma developers to >> slightly alter the release schedule to align releases with a more >> distribution friendly cycle. You could consider shortening one release >> cycle (and then keep the 6 month schedule) to align releases. >> > > We have in the past shuffled things slightly to line up things up with > distros on request, particularly LTS releases. We can certainly explore > that on a one-off basis. > > >With this schedule in place, we would also benefit from more beta > releases over a slightly longer period. They would be packaged into the > beta and RC releases of those distributions thus enabling more pre-release > testing. > > We did have 6 month release cycles in the past. > > The rationale for moving at the time was twofold: > - people rushed in changes towards the feature freeze as otherwise it > would be aages till their changes reached users > - the more changes we have in a release, the more testing and inevitable > regression fixes we need to do, spreading that out should result in things > being more stable > > Initially we did every 3 months (which arguably still aligns) then it > slowly slipped to 4. > > My personal impression is that releases have gotten better as a result of > those changes, so I'm hesitant about reverting that decision. > > Makes sense. With Qt being less of a moving target though, it could make sense to reevaluate our cadence though, both because we might start looking into the future and because the system we support should not be changing as much. Aleix
Re: Synchronized release schedule for Plasma
On Thu, Nov 26, 2020 at 10:25 AM Aleix Pol wrote: > > On Tue, Nov 24, 2020 at 5:10 PM David Edmundson > wrote: >>> >>> As distribution package maintainers, we would like Plasma developers to >>> slightly alter the release schedule to align releases with a more >>> distribution friendly cycle. You could consider shortening one release >>> cycle (and then keep the 6 month schedule) to align releases. >> >> >> We have in the past shuffled things slightly to line up things up with >> distros on request, particularly LTS releases. We can certainly explore that >> on a one-off basis. >> >> >With this schedule in place, we would also benefit from more beta releases >> >over a slightly longer period. They would be packaged into the beta and RC >> >releases of those distributions thus enabling more pre-release testing. >> >> We did have 6 month release cycles in the past. >> >> The rationale for moving at the time was twofold: >> - people rushed in changes towards the feature freeze as otherwise it would >> be aages till their changes reached users >> - the more changes we have in a release, the more testing and inevitable >> regression fixes we need to do, spreading that out should result in things >> being more stable >> >> Initially we did every 3 months (which arguably still aligns) then it slowly >> slipped to 4. >> >> My personal impression is that releases have gotten better as a result of >> those changes, so I'm hesitant about reverting that decision. >> > > > Makes sense. With Qt being less of a moving target though, it could make > sense to reevaluate our cadence though, both because we might start looking > into the future and because the system we support should not be changing as > much. > If we don't want to move to 6 months, pulling back from 4 months to 3 months would make it easier for us to not miss Plasma releases. That being said, with Qt6 now being a thing, wouldn't that mean Qt is more of a moving target again? -- 真実はいつも一つ！/ Always, there's only one truth!
Re: Synchronized release schedule for Plasma
On Thu, Nov 26, 2020 at 10:38 PM Neal Gompa wrote: > > On Thu, Nov 26, 2020 at 10:25 AM Aleix Pol wrote: > > > > On Tue, Nov 24, 2020 at 5:10 PM David Edmundson > > wrote: > >>> > >>> As distribution package maintainers, we would like Plasma developers to > >>> slightly alter the release schedule to align releases with a more > >>> distribution friendly cycle. You could consider shortening one release > >>> cycle (and then keep the 6 month schedule) to align releases. > >> > >> > >> We have in the past shuffled things slightly to line up things up with > >> distros on request, particularly LTS releases. We can certainly explore > >> that on a one-off basis. > >> > >> >With this schedule in place, we would also benefit from more beta > >> >releases over a slightly longer period. They would be packaged into the > >> >beta and RC releases of those distributions thus enabling more > >> >pre-release testing. > >> > >> We did have 6 month release cycles in the past. > >> > >> The rationale for moving at the time was twofold: > >> - people rushed in changes towards the feature freeze as otherwise it > >> would be aages till their changes reached users > >> - the more changes we have in a release, the more testing and inevitable > >> regression fixes we need to do, spreading that out should result in things > >> being more stable > >> > >> Initially we did every 3 months (which arguably still aligns) then it > >> slowly slipped to 4. > >> > >> My personal impression is that releases have gotten better as a result of > >> those changes, so I'm hesitant about reverting that decision. > >> > > > > > > Makes sense. With Qt being less of a moving target though, it could make > > sense to reevaluate our cadence though, both because we might start looking > > into the future and because the system we support should not be changing as > > much. > > > > If we don't want to move to 6 months, pulling back from 4 months to 3 > months would make it easier for us to not miss Plasma releases. > > That being said, with Qt6 now being a thing, wouldn't that mean Qt is > more of a moving target again? It will take some time to be able to put together a release that's fully tested against Qt 6. Aleix
[Powerdevil] [Bug 348882] KDE cannot set backlight anymore, kernel can
https://bugs.kde.org/show_bug.cgi?id=348882 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 347138] Secondary display never turns off
https://bugs.kde.org/show_bug.cgi?id=347138 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 353356] Powerdevil does not respect the critical level configuration
https://bugs.kde.org/show_bug.cgi?id=353356 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 354781] On AC Power state is not recognized
https://bugs.kde.org/show_bug.cgi?id=354781 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 359142] powerdevil ignores "even when external monitor connected" option
https://bugs.kde.org/show_bug.cgi?id=359142 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 361864] System doesn't resume from a "suspend to ram" command after an update with Kubuntu backports 15.10
https://bugs.kde.org/show_bug.cgi?id=361864 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 367698] only one screen is dimmed
https://bugs.kde.org/show_bug.cgi?id=367698 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 368221] Unable to adjust display brightness on Dell laptop, powerdevil messages in journalctl
https://bugs.kde.org/show_bug.cgi?id=368221 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 371522] Hard system freeze at kde startup on battery mode
https://bugs.kde.org/show_bug.cgi?id=371522 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 376121] Backlight is not keeping OFF when laptop lid is closed
https://bugs.kde.org/show_bug.cgi?id=376121 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 377566] powerdevil crashes on boot
https://bugs.kde.org/show_bug.cgi?id=377566 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[Powerdevil] [Bug 378545] Disabling power management does not prevent suspend on lid close
https://bugs.kde.org/show_bug.cgi?id=378545 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
