Once the bugfix is accepted¶

The acceptance email¶

You receive an email notification that the bugfix was accepted:

Accepted postfix into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/postfix/3.3.0-1ubuntu0.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: postfix (Ubuntu Bionic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

Follow the build link and make sure it’s publishing to the correct place (Bionic), and that the builds completed (green check marks).

Proposed Migration¶

The fixed package first lands in the “proposed” pocket for the given release. For more details on the proposed migration process, see Proposed migration.

Check the “excuses” or “migration” page, for Bionic in this case.

General page

Eventually, the package with your fixes appears there (search for postfix in this case). It shows the DEP-8 tests for postfix and anything that depends on it. Any tests that fail show in red.

Note

This page is generated every few minutes, and doesn’t update in real-time.

Bugs fixed in stable releases¶

The Stable Release Updates (SRU) bugfix requires a bug independently verified (preferably by the person who reported the bug), but if it sits idle too long (2 days or so), you can verify it yourself. Follow the instructions provided by the SRU team. In practice, this means replacing the verification-needed-<series> tag (for example, verification-needed-noble) with verification-done-<series> (for example, verification-done-noble).

Pending SRU shows which SRUs are pending and what their status is. Note that this includes DEP-8 test results; if these have failed then it’s unlikely the SRU team will release the update, so it’s wise to follow-up if this happens.

Once all of the SRU’s bugs have reached verification-done, a minimum 7-day aging period has elapsed, and autopkgtests pass, the SRU team moves the source and binary packages into the -updates pocket and marks the bug task(s) as “Fix Released”.