StableReleaseUpdates page (Was: Re: Fw: [scite] Fixed Lua dynamic library loading in Ubuntu 18.04 proposed updates)

Julian Andres Klode julian.klode at canonical.com
Mon Aug 19 20:05:15 UTC 2019


On Mon, Aug 19, 2019 at 09:34:07AM -0700, Bryan Quigley wrote:
> Nope, that's not the standard, expected procedure.  It is always better to
> have someone else verify a fix, it's sometimes not feasible though.
> 
> "While not ideal it is also possible for the uploader of the fix to perform
> the verification of the package in *-proposed"
>  - https://wiki.ubuntu.com/StableReleaseUpdates#Verification
> 

OK, first of all - he SRUed that package in May.

And re the The wiki page: It might say that, but it's _not_ realistic:

- I've uploaded quite a few SRUs by now, and maybe a handful have been (partially)
  verified by someone else. Partially because these people only test their
  favorite release (and then forget to do some tagging changes, or mention
  version numbers), so you still have to do it anyway.

  In practice, people report bugs, and when you push a fix they are gone.

  Waiting days, weeks, or even months so that maybe hopefully someone else
  might review it does not work.

Other random things the wiki page says and people do wrong all the time:

- Basically everyone sets their tasks to "In Progress" when working
  on it, despite "In Progress" being reserved for "fix uploaded to queue".

- People set "Fix committed" when/before an upload, despite it being
  reserved for "fix in -proposed"


-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en



More information about the ubuntu-devel mailing list