upstart 1.5 "Birdsong"

* Lots of "console log" improvements (and new tests).

* New 'early logging' facility which allows jobs that end before the log disk is writeable to have their output peristed to disk when the disk later becomes writeable.

* Upstart is now able to detect jobs which leak file descriptors: a message is generated when run with debug enabled ('--debug' / "initctl log-priority debug").

* New "usage" stanza which allows instance jobs to display a usage message explaining how job should be started. The usage is displayed when the user has not specified the correct variables to allow the job to be started, or when the user queries the usage using "initctl usage <job>".

Milestone information

Project:
upstart
Series:
1.x
Version:
1.5
Code name:
Birdsong
Released:
2012-03-22  
Registrant:
James Hunt
Release registered:
2012-03-22
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon upstart-1.5.tar.gz (md5, sig) Upstart 1.5 237
last downloaded 10 days ago
Total downloads: 237

Release notes 

This release does not have release notes.

Changelog 

View the full changelog

* Lots of "console log" improvements (and new tests).

* New 'early logging' facility which allows jobs that end before the
  log disk is writeable to have their output peristed to disk when the disk
  later becomes writeable.

* Upstart is now able to detect jobs which leak file
  descriptors: a message is generated when run with debug enabled
  ('--debug' / "initctl log-priority debug").

* New "usage" stanza which allows instance jobs to display a usage
  message explaining how job should be started. The usage is displayed
  when the user has not specified the correct variables to allow the job
  to be started, or when the user queries the usage using
  "initctl usage <job>".

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.