The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Scott James Remnant <scott@netsplit.com>
To: upstart-devel@lists.ubuntu.com
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] upstart 0.6.3 released
Date: Sun, 02 Aug 2009 20:46:38 +0100	[thread overview]
Message-ID: <1249242398.32323.9.camel@wing-commander> (raw)

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

The biggest disadvantage to people actually using your software is that
they find bugs, this one's a doozy because it looks like it affects
older 0.3 releases as well.  Now seems as good a time as any to repeat
my recommendation that distributions, mobile and embedded appliance
developers using Upstart consider using 0.6 in their next release rather
than sticking with 0.3

I've also today created the 0.6 stable branch in bzr, those following
stable releases with bzr will want to update their trees to
lp:~scott/upstart/0.6.  New stable releases will be made off this branch
while trunk receives more exciting developments.


0.6.3  2009-08-02  "Our last, best hope for peace"

	* Fixed an assertion when a job's main process is terminated
	  while in the stopping state.  (Bug: #406408)

	* Fixed compilation on ia64.

	* nih-dbus-tool(1) manpage will not be installed, since the binary
	  is not.  (Bug: #403103)


The tarball can be found here:

	http://upstart.ubuntu.com/download/

For more information on upstart:

	http://upstart.ubuntu.com/


Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-08-02 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-02 19:46 Scott James Remnant [this message]
2009-08-02 20:02 ` [ANNOUNCE] upstart 0.6.3 released Garrett Cooper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1249242398.32323.9.camel@wing-commander \
    --to=scott@netsplit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=upstart-devel@lists.ubuntu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox