[ANNOUNCE] upstart 0.5.2 released

[angus salkeld]

Hi Scott

We (Allied Telesis) use Upstart in some of our products and
this license change is going to cause concern, we are going
to have to go running off to the lawyers (and spend good 
money) to see if we can upgrade.

Very quickly someone will say "use a different init with a more 
friendly licence so we don't have to hassle with this".

We really like Upstart and where it is going.

Please change the license back to GPLv2.

Regards
Angus Salkeld


On Wed, 2009-06-17 at 11:33 -0700, Saravanan Shanmugham (sarvi) wrote:
> 
> Why the move to GPLv3. I am not sure how many in the community see this
> as a problem, but we do.
> As a policy many don't use GPLv3 software because its not viewed as
> industry friendly. 
> 
> I don't want to get into the discussion of whether GPLv3 is or is not
> industry friendly.
> 
> Moreover, if you plan on Upstart being truly widely used and a true
> replacement for SysV Init, it should match the Linux Kernel Licensing
> whatever that might be. So that it really is part of the base core Linux
> infrastructure that  it is convenient for everyone to use together.
> 
> I notice that Fedora, Redhat and quite a few other distros also package
> upstart as part of their distros and many of these distros as use by the
> industry.
> 
> The core set of components have so far been GPLv2. 
> 
> Sarvi    
> 
> -----Original Message-----
> From: upstart-devel-bounces at lists.ubuntu.com
> [mailto:upstart-devel-bounces at lists.ubuntu.com] On Behalf Of Scott James
> Remnant
> Sent: Wednesday, June 17, 2009 11:06 AM
> To: Upstart Development
> Subject: [ANNOUNCE] upstart 0.5.2 released
> 
> And positively frigidly far away from the heels of 0.3.10 comes the 0.5
> series release that includes the same bug fix, along with a whole heap
> of other changes - mostly D-Bus, but there's a few other bug fixes in
> there too.
> 
> 
> 0.5.2  2009-06-17  "Something, something, something, D-Bus"
> 
> 	* The licence for Upstart has been updated to GNU GPL v3.
> 
> 	* Overhaul of the automatically generated D-Bus bindings code,
> 	  fixing many issues with memory leaks, inconsistent return
> values
> 	  and loss of method returns after the method has taken place.
> 
> 	* D-Bus 1.2.4 is now required, and must be patched to fix
> 	  https://bugs.freedesktop.org/show_bug.cgi?id=22316
> 
> 	* D-Bus Job objects now have "name", "description", "author"
> 	  and "version" properties.
> 
> 	* D-Bus Instance object now have "name", "goal" and "state"
> 	  properties.
> 
> 	* initctl now obtains the name properties for display instead of
> 	  printing the mangled object path component.  (Bug: #299290)
> 
> 	* D-Bus configuration updated now that the daemon is fixed to be
> 	  deny-by-default, and updated to avoid bare "send_interface"
> 	  stanzas.  (Bug: #323021)
> 
> 	* Fixed assertion caused by the post-start or pre-stop scripts
>           exiting after the main process of a respawning job had exited
>           (Bug: #381048)
> 
> 	* The /proc filesystem need not be mounted if the "oom_adj"
> 	  configuration stanza is not used.  (Bug: #259801)
> 
> 	* Overly large values to configuration stanzas are now caught
> 	  and rejected.  (Bug: #340134)
> 
> 	* The --enable-compiler-warnings configure option has been
> 	  extended to add -Wextra, but turns off a few of the more
> extreme
> 	  warnings
> 
> 	* GNU C Library v2.4 (or backported inotify support) is required
> 
> 	* pkg-config 0.22 is now required, it probably was anyway but we
> 	  now explicitly check for it.
> 
> 	* Dependency on Python for the D-Bus binding tool has been
> dropped
> 	  and replaced with a dependency on expat 2.0.0
> 
> 
> 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?
> 

NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesis Labs Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesis Labs.