Re: 5.3 errata
On Thu, Apr 9, 2015 at 11:25 PM, Eike Hein wrote: > On 04/09/2015 11:01 PM, Vishesh Handa wrote: > >> KDE 4.9 - No errata >> KDE 4.10 - No errata >> KDE 4.11 - No errata >> > > https://community.kde.org/Plasma/5.0_Errata > https://community.kde.org/Plasma/5.1_Errata > https://community.kde.org/Plasma/5.2_Errata > > I was under the impression we were *specially* doing this for Plasma 5 since the initial releases had some issues. > > Just for the record, I'm not against highlighting missing features on > > the errata. I am, however, very against linking to bugs from 2010, which > > aren't solvable. > > Bugs that aren't solvable are excellent candidates for errata, > though. An example is the DND artifacting on nVidia bug in > Folder View I added to the 5.0 errata back then; this was solved > by switching to new Qt API that only became available in Qt 5.4, > and before that there was no good way to fix it. The errata were > a good way to make people aware of this and let them know what to > expect. > Okay. I'll update the list. My main gripe was that many of the current bugs shouldn't have been put there in the first place. -- Vishesh Handa ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: 5.3 errata
On 04/09/2015 11:01 PM, Vishesh Handa wrote: KDE 4.9 - No errata KDE 4.10 - No errata KDE 4.11 - No errata https://community.kde.org/Plasma/5.0_Errata https://community.kde.org/Plasma/5.1_Errata https://community.kde.org/Plasma/5.2_Errata > Just for the record, I'm not against highlighting missing features on > the errata. I am, however, very against linking to bugs from 2010, which > aren't solvable. Bugs that aren't solvable are excellent candidates for errata, though. An example is the DND artifacting on nVidia bug in Folder View I added to the 5.0 errata back then; this was solved by switching to new Qt API that only became available in Qt 5.4, and before that there was no good way to fix it. The errata were a good way to make people aware of this and let them know what to expect. Cheers, Eike ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: 5.3 errata
On Thu, Apr 9, 2015 at 10:46 PM, Jonathan Riddell wrote: > Really this is normal practice. > Can you please give me sources for this? KDE 4.9 - No errata KDE 4.10 - No errata KDE 4.11 - No errata The applications release has a 'This is a list of grave bugs and common pitfalls surfacing after the release was packaged' [1]. That doesn't seem like an errata. Just for the record, I'm not against highlighting missing features on the errata. I am, however, very against linking to bugs from 2010, which aren't solvable. -- Vishesh Handa [1] https://www.kde.org/info/applications-15.03.95.php ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: 5.3 errata
On Thu, Apr 09, 2015 at 10:43:00PM +0200, Vishesh Handa wrote: >The answer above doesn't specifically answer what I would like to know - >1. The stated reason is "so that people can see what bugs are known when >they are reporting bugs". This is what we have bugzilla for. Plasma has >over 100 bugs. It is to highlight the most important ones. >2. If, you think these bugs deserve mention because they are marked as >critical - Is it our policy to be highlighting 'critical' bugs in the >errata? Yes / No. That's the practice I'm following currently yes but I've asked the team to add other bugs they think are worth highlighting. Really this is normal practice. Jonathan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: 5.3 errata
On Thu, Apr 9, 2015 at 10:32 PM, Jonathan Riddell wrote: > On Thu, Apr 09, 2015 at 10:30:34PM +0200, Vishesh Handa wrote: > >On Thu, Apr 9, 2015 at 10:01 PM, Jonathan Riddell > wrote: > > > > On Thu, Apr 09, 2015 at 07:14:18PM +0200, Vishesh Handa wrote: > > >A A Hi Johnathan > > >A A Could you please tell me what is accomplished by creating > this > > errata > > >A A page? > > > > It means people can see what significant problems exist before they > > install.A It means people can see what bugs are known when they are > > reporting bugs.A It means people upgrading from Plasma 4 can see > what > > features are missing.A It's a very normal part of release notes. > > > >Great. That makes sense. > >However, the page currently also lists bugs -A > >Bugs > >https://bugs.kde.org/342631 user-manager overlaps Account Details KCM > >http://bugs.kde.org/338506 image wallpapers are blurry in scaled and > >scaled and cropped mode > >https://bugs.kde.org/346018 The default wallpaper has pixelated lines > >https://bugs.kde.org/233471 Baloo abuses Disk access for excessive > periods > >of time after startup > >https://bugs.kde.org/341581 baloo_file - using 100% cpu > >I'm confused as to why need to specifically duplicate these bugs when > they > >are already present in the bug tracker. I agree that these bugs have a > >'critical' flag set, but highlighting them doesn't help us in any way. > > I refer the honourable gentleman to the answer I gave some moments ago The answer above doesn't specifically answer what I would like to know - 1. The stated reason is "so that people can see what bugs are known when they are reporting bugs". This is what we have bugzilla for. Plasma has over 100 bugs. 2. If, you think these bugs deserve mention because they are marked as critical - Is it our policy to be highlighting 'critical' bugs in the errata? Yes / No. -- Vishesh Handa ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: 5.3 errata
On Thu, Apr 09, 2015 at 10:30:34PM +0200, Vishesh Handa wrote: >On Thu, Apr 9, 2015 at 10:01 PM, Jonathan Riddell > wrote: > > On Thu, Apr 09, 2015 at 07:14:18PM +0200, Vishesh Handa wrote: > >A A Hi Johnathan > >A A Could you please tell me what is accomplished by creating this > errata > >A A page? > > It means people can see what significant problems exist before they > install.A It means people can see what bugs are known when they are > reporting bugs.A It means people upgrading from Plasma 4 can see what > features are missing.A It's a very normal part of release notes. > >Great. That makes sense. >However, the page currently also lists bugs -A >Bugs >https://bugs.kde.org/342631 user-manager overlaps Account Details KCM >http://bugs.kde.org/338506 image wallpapers are blurry in scaled and >scaled and cropped mode >https://bugs.kde.org/346018 The default wallpaper has pixelated lines >https://bugs.kde.org/233471 Baloo abuses Disk access for excessive periods >of time after startup >https://bugs.kde.org/341581 baloo_file - using 100% cpu >I'm confused as to why need to specifically duplicate these bugs when they >are already present in the bug tracker. I agree that these bugs have a >'critical' flag set, but highlighting them doesn't help us in any way. I refer the honourable gentleman to the answer I gave some moments ago "It means people can see what significant problems exist before they install." Jonathan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: 5.3 errata
On Thu, Apr 9, 2015 at 10:01 PM, Jonathan Riddell wrote: > On Thu, Apr 09, 2015 at 07:14:18PM +0200, Vishesh Handa wrote: > >Hi Johnathan > >Could you please tell me what is accomplished by creating this errata > >page? > > It means people can see what significant problems exist before they > install. It means people can see what bugs are known when they are > reporting bugs. It means people upgrading from Plasma 4 can see what > features are missing. It's a very normal part of release notes. Great. That makes sense. However, the page currently also lists bugs - Bugs https://bugs.kde.org/342631 user-manager overlaps Account Details KCM http://bugs.kde.org/338506 image wallpapers are blurry in scaled and scaled and cropped mode https://bugs.kde.org/346018 The default wallpaper has pixelated lines https://bugs.kde.org/233471 Baloo abuses Disk access for excessive periods of time after startup https://bugs.kde.org/341581 baloo_file - using 100% cpu I'm confused as to why need to specifically duplicate these bugs when they are already present in the bug tracker. I agree that these bugs have a 'critical' flag set, but highlighting them doesn't help us in any way. -- Vishesh Handa ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: 5.3 errata
On Thursday 09 April 2015 21:01:13 Jonathan Riddell wrote: > On Thu, Apr 09, 2015 at 07:14:18PM +0200, Vishesh Handa wrote: > >Hi Johnathan > >Could you please tell me what is accomplished by creating this errata > >page? > > It means people can see what significant problems exist before they > install. It means people can see what bugs are known when they are > reporting bugs. It means people upgrading from Plasma 4 can see what > features are missing. It's a very normal part of release notes. For example I know that there are (very few) people considering window tabbing as a killer feature. For them a switch to Plasma 5 would be a major regression and a reason to stay on Plasma 4 - which is totally fine. Such a page puts out the warning and also tells away the screaming from disappointed users. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: 5.3 errata
On Thu, Apr 09, 2015 at 07:14:18PM +0200, Vishesh Handa wrote: >Hi Johnathan >Could you please tell me what is accomplished by creating this errata >page? It means people can see what significant problems exist before they install. It means people can see what bugs are known when they are reporting bugs. It means people upgrading from Plasma 4 can see what features are missing. It's a very normal part of release notes. Jonathan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: 5.3 errata
Hi Johnathan Could you please tell me what is accomplished by creating this errata page? -- Vishesh Handa ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
5.3 errata
5.3 beta tars are made, please add known bugs and features which have been removed to: (I've put bugs marked critical on it already) https://community.kde.org/Plasma/5.3_Errata There two seem kindae nasty, could someone confirm them? 345459 systemse kcm_desk unassigned-b...@kde.org UNCO --- Changing 'Downloads' default path attempts to move *ALL* files in $HOME to new location 345729 systemse kcm_desk unassigned-b...@kde.org UNCO --- Changing the directory of documents completely wipes out user's home folder Jonathan ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel