<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 21, 2015 at 1:58 PM, Jonathan Riddell <span dir="ltr"><<a href="mailto:jr@jriddell.org" target="_blank">jr@jriddell.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Thanks for this. I have a script in the releaseme branch to open<br>
firefox with tabs for each product to manually add the new version<br>
numbers, I've searched far and wide for a way to script it and it<br>
doesn't seem to be possible, suggestions welcome.<br>
<br>
I propose the following changes:<br>
<br>
- make bluedevil product, move relevant<br>
solid bugs over. The other parts of solid are the libraries which now<br>
has frameworks-solid product and powerdevil which Kai is looking at.<br>
<br>
- kill kstart, move bugs to kde-cli-tools<br>
<br></blockquote><div>++</div><div><br></div><div>I'll take care of that.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- kill kded-appmenu move bugs to plasma-workspace<br>
<br>
- kill kfontview move bugs to plasma-desktop<br>
<br></blockquote><div>we don't have bugzilla components for plasma-workspace and plasma-desktop? </div><div><br></div><div>Certainly I don't want to end up with a catchall for all plasma bugs. The plasma4 bugzilla turned into that and it just became useless.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- on muon make apol the default assignee<br>
<br>
Jonathan<br>
<div><div><br>
<br>
On Tue, Jan 20, 2015 at 10:34:18PM +0100, David Edmundson wrote:<br>
> I was trying to triage some of the wider Plasma bugs and realised that I<br>
> didn't have a full list of bugzilla components for everything we're<br>
> actually releasing. Some are quite obscure, like kfontviewer.<br>
> I spent some time making a comprehensive list<br>
> plasmashell<br>
> Breeze<br>
> Powerdevil<br>
> systemsettings<br>
> kde-gtk-config<br>
> kde-cli-tools<br>
> kded-appmenu<br>
> kstart<br>
> kio-extras<br>
> kwin<br>
> kscreen<br>
> ksplash<br>
> ksmserver<br>
> ksshaskpass<br>
> plasma-nm<br>
> oxygen<br>
> muon<br>
> Plasma Workspace Wallpapers<br>
> policykit-kde<br>
> khelpcenter<br>
> khotkeys<br>
> kinfocenter<br>
> kmenuedit<br>
> ksysguard<br>
> kwrited<br>
> krunner<br>
> drkonqui<br>
> klipper<br>
> knetattach<br>
> kdeplasma-addons<br>
> solid<br>
> kwayland<br>
> kfontview<br>
> *<br>
> A lot of these have inactive maintainers, even critical bugs could be<br>
</div></div>> accidentally being ignored here.A<br>
<span>> We need to make sure together we actually go through the entirety of this<br>
> list not just plasmashell. We also need to make sure they all have 5.x<br>
> version numbers. Some do not which makes searching even harder, especially<br>
> against the massive noise of KDE 4 issues.<br>
> Attached is a spreadsheet which has a mapping <----> repositories and<br>
> folders, plus some other rambling.<br>
> David<br>
> *I've deliberately not counted kfilemetadata and baloo, they have an<br>
> active maintainer and they'll soon be frameworks' problem not mine.<br>
<br>
<br>
</span><div><div>> _______________________________________________<br>
> Plasma-devel mailing list<br>
> <a href="mailto:Plasma-devel@kde.org" target="_blank">Plasma-devel@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
<br>
_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org" target="_blank">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
</div></div></blockquote></div><br></div></div>