Your message dated Wed, 19 Dec 2018 12:05:28 +1030 with message-id <[email protected]> and subject line Re: Bug#914286: new stable upstream version 1.3 available has caused the Debian Bug report #914286, regarding new stable upstream version 1.3 available to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 914286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914286 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: opus Version: 1.3~beta+20180518-1 Hey there, There is a new upstream version available http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html It would be nice to update the Debian beta snapshot to the stable releease
--- End Message ---
--- Begin Message ---On Tue, Dec 18, 2018 at 02:29:08PM -0500, Kevin Otte wrote: > I just saw the news post about the Installer Buster Alpha 4 release. > Does this mean the freeze is coming soon? Do we need an NMU of this > package to make sure we don't have yet another Debian release with an > alpha/beta version of Opus in it? Why would we need that? The 1.3 package hit unstable yesterday, I just hadn't triaged this bug report yet - and it's not RC to block migration. And that is still absolutely no guarantee that we won't release Buster with some other alpha/beta/rc/whatever snapshot at the point the freeze deadline does roll around. What we've released with for every release has been decided on in consultation with the upstream maintainers. The version numbers aren't important - only what important fixes we might need, or what "risky" new changes we want to avoid freezing with. And we can't decide that until just before the freeze because we don't know what Unknown things will become Known between now and then ... So please, for future reference, when reporting "new upstream" bugs, especially if you're going to be somewhat {in,per}sistant about them, please say *exactly* what it is that you want or need from the newer release. "I want a nice round version number" - is not very helpful, and sometimes can even be the exact opposite of helpful - nice round version number releases can have bugs just as terrible as any other. "I need/want feature/fix X (because Y)" OTOH is helpful and actionable. And helps prioritise sometimes conflicting goals about what to release when and to whom. Needs like that are why we had the "beta" snapshot we did in the first place instead of the nice round 1.2.1 release. Thanks! Ron
--- End Message ---
