[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Updated Debian 8: 8.8 released



I'd like to suggest some changes to the standard template for point
release announcements.

> The Debian project is pleased to announce the eighth update of its
> stable distribution Debian 8 (codename "jessie"). This update mainly
> adds corrections for security problems to the stable release, along with
> a few adjustments for serious problems. Security advisories were already
> published separately and are referenced where available.

The only problem here is a negative: this template for announcing
Debian point releases never once uses the expression "point release"
(which readers are nonetheless expected to understand when it turns up
in bugfix "Reason" summaries).  Perhaps it should be:

  The Debian project is pleased to announce the eighth update of its
  stable distribution Debian <release> (codename "<codename>"). This
  point release mainly adds corrections for security issues, along
  with a few adjustments for serious problems. Security advisories
  have already been published separately and are referenced where
  available.

> Please note that this update does not constitute a new version of Debian
> 8 but only updates some of the packages included. There is no need to
> throw away old "jessie" CDs or DVDs but only to update via an up-to-date
> Debian mirror after an installation, to cause any out of date packages
> to be updated.

Nitpicks:
 * Many repetitions here and below of "update/up-to-date/out of date".
 * Also, awkward repetition of "but only".
 * "CDs or DVDs" doesn't really cover it (but maybe we shouldn't try).
 * "After an installation" is oddly placed (making it sound as if all
   systems running 8.7 need to first do a reinstall before updating).
 * An "update" from a mirror won't cause any packages to be updated -
   that's an "upgrade".
Perhaps we could turn it into something like:

  Please note that this does not constitute a new version of Debian
  <release> but only updates some of the packages included. There is
  no need to throw away old "<codename>" media; after an installation,
  packages can be upgraded to the current versions from an up-to-date
  Debian mirror.

> Those who frequently install updates from security.debian.org won't have
> to update many packages and most updates from security.debian.org are
> included in this update.

Some easily avoidable repetition:

  Those who frequently install updates from security.debian.org won't have
  to upgrade many packages, and most such updates are included in this
  point release.

> New installation media and CD and DVD images containing updated packages
> will be available soon at the regular locations.

Here maybe "and CD/DVD/BD/USB images"?

> Upgrading to this revision online is usually done by pointing the
> aptitude (or apt) package tool (see the sources.list(5) manual page) to
> one of Debian's many FTP or HTTP mirrors. A comprehensive list of
> mirrors is available at:

Nitpicks:
 * Does "online" here mean "over the Internet" or "without downtime"?
   (Fortunately I suppose it's true either way)
 * It makes it sound as if routine upgrades require me to edit my
   sources.list file each time.
 * For a simple upgrade like this don't we recommend apt before
   aptitude?  Or does it even make sense to specify?
 * Isn't "package tool" missing the word "management"?

And last but not least:
 * It's true that there still are FTP mirrors, but we shouldn't be
   recommending them.  Indeed, we should probably futureproof this
   text for the day when HTTPS becomes the default.

My suggestion:

  An upgrade to this revision can be performed online if the package
  management system is set up to point at one of Debian's many mirrors
  (see the sources.list(5) manual page). A comprehensive list of
  mirrors is available at:

-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package


Reply to: