The release process for Vagrant requires executing a script anyways, so perhaps I can hook something up in there to post something somewhere...
I'll see what I can do to make this better. On Thu, May 8, 2014 at 12:13 AM, Mitchell Hashimoto <[email protected]> wrote: > Christian, > > You're right, we forgot to send 1.6.0 out. Patch releases we don't > immediately notify, we might in a few days. > > The best way to know right away for major releases actually is > probably our blog RSS feed or GitHub tag feed. > > We'll likely start a vagrant-announce mailing list at some point, but > there isn't a big value for us right now to do this and its extra > work. > > Best, > Mitchell > > On Thu, May 8, 2014 at 12:01 AM, Christian Berendt > <[email protected]> wrote: >> On 05/08/2014 02:22 AM, Mitchell Hashimoto wrote: >>> >>> We do send release notifications prefixed with [ANN] that you can filter >>> out. >> >> >> Can't find notificatiosn for 1.6.1 or 1.5.3 or 1.6.0 on this mailinglist. >> >> >> Christian. >> >> -- >> Christian Berendt >> Cloud Computing Solution Architect >> Mail: [email protected] >> >> B1 Systems GmbH >> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de >> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
