>Bugs that I would like to have resolved: > >1291 some kickoff menu bugs > => patches look good, I'll push them soon >1424 kdegraphics-kfile-plugins-trinity: add ghostscript as >recommended package > => simple packaging issue >1488 kmix: Adjusting the volume (mono) microphone does not work > => I plan to examine this on Wednesday >1493 kio_man does not support XZ compressed manpages > => patch waiting for test > >Less important: > >1146 Build issue: fusion-icon does not install python module in >python_sitelib >1188 Build issue: tde-guidance can not work > => only when I'll find time to try the solutions proposed by >Fran�ois > >Besides, I need to include and update Debian / Ubuntu metapackages >for >v3.5.13-sru branch. > >I also plan to backport latest patches "Cleanup output clutter." >:) > >Any other suggestions? I don't have a dog in the fight. I am curious after having a discussion with another person about R14. The "priority" bug list for R14 is growing smaller. Originally we targeted an R14 release in late May, although I don't know whether that remains tenable. I am thinking that releasing 3.5.13.2 after R14 might seem a tad awkward, although hardly strange. Conversely, releasing R14 real soon after announcing 3.5.13.2 might seem a tad odd from a public relations perspective. I don't think 3.5.13.2 will ever be "perfect." In any project a "go live" moment is necessary. There always will be unresolved bugs in any large project. Theoretically, patches could be backported to 3.5.13.2 for years, but I suspect none of us want that and prefer to see 3.5.13.2 as the last of that branch. Even the KDE folks don't try to cram as many bug patches as possible into each point release. They stick to their monthly schedule. Seems the sooner we officially release 3.5.13.2 the sooner we get 3.5.13.x behind us and focus energies on R14. That all said, your list looks short and you wrote that patches already exist for some of them. I'm just chattering out loud --- you do what you think best. :-) Darrell