1. Is this a targeted bug fix release, and how does that show? GStreamer 1.26.2 is a bug fix release; it is the 2nd bug fix release on the 1.26.x series. Once a new major release has been done, the 2nd number (26) only includes bugfixes while the active development will (git main branch) will lead to 1.28.0. This is not expected soon. New feature, API changes (if any) or new modules are in main and can only be part of the next major release (in this case 1.28.0)
2. What are the risks of the changes for the quality of the Debian release? Including this release should improve the overall stability, as mentioned, it only includes targeted bug fixes. Furthermore, upstream recommends to keep the patch version in sync for all GStreamer packages. Considering that the core library (gstreamer1.0 where all other plugin collections depend upon is 1.26.2-1, it does not make sense to keep good on 1.26.1. In fact, if gst-plugins-good1.0 is marked as a key package, so should gstreamer1.0 and gst-plugins-base1.0. 3. Is there a policy that describes what upstream considers acceptable for this upstream release? Quoting the upstream release manager and core developer here: point releases on the stable branch usually only include bug fixes and things that aren't "invasive" (we wouldn't include a big refactoring of some component in a stable release even if it fixes bugs); same for API additions, they would only go into main (and the next stable release then) we also don't add new elements/plugins in stable releases (Rust plugins are an exception, but debian/ubuntu aren't really packaging those anyway apart from one or two) 4. Does that policy align with our bug severity important or higher? The policy to include into point releases seems very much in line with severity > important 5. Does upstream test thoroughly? On every merge request, unit tests and integration tests are running that need to succeed before a MR is merged. 6. Has this package seen new upstream version uploads to stable in the past to facilitate security support? Yes, there are semi regular uploads to stable, done by the security team; assisted by upstream. Most of the time, the uploads include backported patches from these stable bugfix releases. In the case of bookworm, this is still 1.22.0. We have suggested to upload 1.22.12; but this was not yet accepted. 7. Look at the diff. If it's long (TODO should we put a number here?), you probably need a targeted fix. The changes in good can be inspected at https://gstreamer.freedesktop.org/releases/1.26/#1.26.2 These contain 26 fixes, going from edge cases, race conditions to even fixes for logic in streaming encoded formats. Considering the extensive code base, this is very selective. 8. Look at the diff. If there's a number of changes not relevant for Debian, you probably need a targeted fix. Since it is a bugfix/patch release; these are relevant: working on this myself; a lot of these changes require dedicated knowledge where, to the user, a crash, lockup or 'green video' is hard to understand. 9. Look at the diff. If there something in there that is difficult to explain, but not directly related to the (RC or important) bugs you are fixing, you probably need a targeted fix. I refer back to the answer of upstream On Thu, 26 Jun 2025 at 19:05, Paul Gevers <[email protected]> wrote: > > Control: tags -1 moreinfo > > > Bugfix release of the GStreamer project. > > > Can you please go over the questions in our FAQ [1] in the new-upstream > section and answer them? I note that gst-plugins-good is a key package. > > > Additional, the d/changelog > > file has been converted to DEP-5 format. > > > This isn't really appropriate now. > > Paul > > [1] https://release.debian.org/testing/FAQ.html > -- g. Marc GPG: 827C FD74 BA46 8152 A041 F3A0 7A6A 4F17 5995 A65B
