[Bug 962124] Re: Feature Freeze Exception request for Upstart in Precise

[Steve Langasek]

Thanks, Martin.  James, I've merged your branch onto lp:ubuntu/upstart
and tacked on a few changelog fixes (documenting bug numbers).  Once
you're satisfied with the regression testing, we can get this uploaded.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/962124

Title:
  Feature Freeze Exception request for Upstart in Precise

Status in “upstart” package in Ubuntu:
  Triaged

Bug description:
  I have just made an upstream Upstart release (1.5) and wish to get
  this added to Precise.

  = Rationale =

  == Bug Fixes ==

  Upstart 1.5 includes fixes for two important bugs seen in Ubuntu:

  * bug 936667
  * bug 940290

  == New Features ==

  === Usage stanza ===

  Upstart 1.5 also includes a new "usage" feature, developed by Redhat.

  I believe adding this new feature is low-risk but does introduce a new
  initctl command ("initctl usage <job>") and a new job stanza ("usage
  <string>").

  CONTINGENCY: There are currently no users of this feature as it is
  new, however if this feature proved problematic, The usage stanzas
  could simply be commented out of the relevant /etc/init/*.conf files.

  == Code Changes ==

  Facilities relating to the early job logging code -- which is already in the Ubuntu version of Upstart -- has been renamed. The early job logging facility ensures that jobs which *end* before the disk becomes writeable are cached until Upstart is notified of writeable disks by calling a new initctl command. When the feature was first introduced into Ubuntu, that command was called "flush-early-job-log", but now that the code is in Upstream Upstart, it has been renamed to the more descriptive
  "notify-disk-writeable".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/962124/+subscriptions