Understanding documentation fixes

[Matthew East]

Hi,

On Jan 12, 2008 1:02 AM, Emma Jane Hogbin <emmajane at xtrinsic.com> wrote:
> What is the policy for fixing stable release documentation? Surely we
> don't leave it wrong in perpetuity...

The policy is essentially the same as for software bugs, which is
described here - https://wiki.ubuntu.com/StableReleaseUpdates

These are:

# Bugs which may, under realistic circumstances, directly cause a
security vulnerability
# Bugs which represent severe regressions from the previous release of Ubuntu
# Bugs which may, under realistic circumstances, directly cause a loss
of user data

In other situations, we fix the bug in the next release of Ubuntu.

There have often been discussions about relaxing these requirements
for documentation. However my personal view is that it's unlikely to
happen - the amount of work required to prepare a new package, test it
thoroughly to ensure that it won't cause breakage on the system, put
it through the StableReleaseUpdate process, and keep help.ubuntu.com
up to date as well is actually quite substantial. I'm happy to hear
alternative proposals though.

-- 
Matthew East
http://www.mdke.org
gnupg pub 1024D/0E6B06FF