Hi, re below from Robie
> ask a Technical Board member for an exception please can I ask for an exception for our package budgie-extras https://bugs.launchpad.net/bugs/1881261 (microrelease from v1.0.1 to v1.0.2) The background here is that budgie-extras is a series of applets that the Ubuntu Budgie team have developed and and continue to maintain for budgie-desktop users. As we move forward to 20.10 we have backported a number of fixes that have been reported to us via different distros, github, our support forum etc. On the whole we don't use launchpad to track bugs. This v1.0.2 microrelease is in use by a number of distros for a couple of months now (https://repology.org/project/budgie-extras/versions). The manual test suite is described in the issue SRU template itself. These are fixed issues for GUI based applets to budgie-desktop and cannot have automatic type tests - hence the manual test steps in the SRU itself. Happy to clarify - or just ping me via IRC thx David (Project Lead Ubuntu Budgie) ---------- Forwarded message --------- From: Robie Basak <1881...@bugs.launchpad.net> Date: Wed, 15 Jul 2020 at 14:35 Subject: [Bug 1881261] Re: [SRU] v1.0.2 service release for budgie-extras To: <davidmoham...@gmail.com> Thank you for looking after budgie-extras in Focal! https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases says that "it is also acceptable to upload new microreleases with many bug fixes without individual Launchpad bugs for each of them" but subject to specific criteria that includes "a reliable and credible test suite for assuring the quality of every commit or release". I don't see any test suite apart from a code style checker, so don't think that's the case here? In that case, you either need individual SRU bugs for each individual fix, or alternatively "exceptions must still be approved by at least one member of the Ubuntu Technical Board". I appreciate that it perhaps makes sense to review these changes as a whole and accept them wholesale, especially as comprehensive test suites for GUIs are especially challenging. However I don't believe that as an SRU team member I have the authority to accept this approach; my understanding is that it has to be a member of the Technical Board. Is there a test suite I'm missing here? If not, then I suggest that you decide if you want to have individual bugs to be SRU-verified for each individual change you want to make, or if you want to ask a Technical Board member for an exception. I encourage you to do the latter if you think it makes sense. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1881261 Title: [SRU] v1.0.2 service release for budgie-extras Status in budgie-extras package in Ubuntu: Fix Released Status in budgie-extras source package in Focal: New Status in budgie-extras source package in Groovy: Fix Released Bug description: SRU for Focal - target 20.04.1 [Impact] The request falls under the microrelease criteria for an SRU - bump from v1.0.1 to v1.0.2. This release resolves a few crash issues, capability that broke due to GNOME 3.36 uplifts late in the development cycle and usability issues. These have been reported by users via our discourse forum / github issues Changelog Service Release incorporating: Previews - resolve refreshing when there are no windows such as showtime/weathershow on the desktop (useability) Previews - display previews for apps like libreoffice that change their class name after opening (useability) Previews - fix crash when windows are closed whilst displaying previews (crash) Layouts - fix potential crash condition when nemo is hiding its menu but the global menu was expecting it (crash) Countdown - display correctly on vertical panels (useability) Dropby - ensure dropby displays and works for two or more users on the same machine (crash) Brightness Controller - Brightness control slider now works under GNOME 3.36 (broken capability) Shuffler Control - fixed incorrect label display for CTRL+ALT+1 (useability) Network applet - sort VPN list in alphabetical order (useability) Latest translations (useability) [Test Case] * Install the following budgie-extras packages in proposed: sudo apt install budgie-previews budgie-extras-daemon budgie- countdown-applet budgie-dropby-applet budgie-brightness-controller- applet budgie-window-shuffler budgie-network-manager-applet budgie- extras-common * Logout and login after installation. If necessary add applets to the panel. N.B. Shuffler, layouts and previews are not applets * For previews (remember to enable through Menu - Preview Controls), use normally across a wide range of applications including Libreoffice * For Layouts use Menu - Budgie Layouts and select Cupertino / theOne layout. Open files and check that the menu is displayed in the panel. Switch to another layout and check that the files menu is not visible until you press Alt * For dropby - connect a usb stick and open the file contents from the popup on the screen. Login to a second user and repeat * For brightness - add the brightness applet to the panel and check the sliders visible on the applet popup work as expected * For shuffler control - open Menu Shuffler Control and check that the labels match the keyboard shortcuts actions * for Network applet - add multiple VPNs and see if they are displayed alphabetically. Known working VPNs should be selectable via the applet (this is normal behaviour and is a regression test to-do) * For countdown - switch the panel from horizontal to vertical (if necessary widen the panel size) [Regression Potential] * All the packages are specific to budgie desktop on Ubuntu and are not applicable to any other desktop environment thus in terms of regression potential is limited to users of budgie * All applets are optional - they are not key capabilities and can be removed from the panel if in the unlikely event there is a regression in any specific applet. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-extras/+bug/1881261/+subscriptions -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
