Update CHANGELOG to be up to date

This commit is contained in:
Mitchell Hashimoto 2013-03-13 21:36:49 -07:00
parent 82d8285df6
commit f87ffc420d
1 changed files with 7 additions and 13 deletions

View File

@ -7,7 +7,7 @@ BACKWARDS INCOMPATIBILITIES:
to upgrading. The new plugin system in place will avoid this issue in to upgrading. The new plugin system in place will avoid this issue in
the future. the future.
- Lots of changes introduced in the form of a new configuration version and - Lots of changes introduced in the form of a new configuration version and
format, but this is opt-in. Old Vagrantfile format continues to be supported, format, but this is _opt-in_. Old Vagrantfile format continues to be supported,
as promised. To use the new features that will be introduced throughout as promised. To use the new features that will be introduced throughout
the 1.x series, you'll have to upgrade at some point. the 1.x series, you'll have to upgrade at some point.
@ -17,17 +17,14 @@ FEATURES:
allow Vagrant to power systems other than VirtualBox. Much improvement allow Vagrant to power systems other than VirtualBox. Much improvement
and change will come to this throughout the 1.x lifecycle. The API and change will come to this throughout the 1.x lifecycle. The API
will continue to change, features will be added, and more. Specifically, will continue to change, features will be added, and more. Specifically,
in this release, a robust system for handling shared folders and a revamped system for handling shared folders gracefully across providers
networks is not introduced, so new providers shouldn't yet support this. will be introduced in a future release.
A system will come into place in future releases.
- New plugin system which adds much more structure and stability to - New plugin system which adds much more structure and stability to
the overall API. The goal of this system is to make it easier to write the overall API. The goal of this system is to make it easier to write
powerful plugins for Vagrant while providing a backwards-compatible API powerful plugins for Vagrant while providing a backwards-compatible API
so that plugins will always _load_ (though they will almost certainly so that plugins will always _load_ (though they will almost certainly
not be _functional_ in future versions of Vagrant). not be _functional_ in future versions of Vagrant).
- Plugins installed as gems no longer "autoload". You must now explicitly - Plugins are now installed and managed using the `vagrant plugin` interface.
require plugins in the `~/.vagrantrc` file, using `Vagrant.require_plugin`.
This decreases Vagrant's initial startup time considerably.
- Allow "file://" URLs for box URLs. [GH-1087] - Allow "file://" URLs for box URLs. [GH-1087]
- Emit "vagrant-mount" upstart event when NFS shares are mounted. [GH-1118] - Emit "vagrant-mount" upstart event when NFS shares are mounted. [GH-1118]
- Add a VirtualBox provider config `auto_nat_dns_proxy` which when set to - Add a VirtualBox provider config `auto_nat_dns_proxy` which when set to
@ -43,28 +40,25 @@ FEATURES:
IMPROVEMENTS / BUG FIXES: IMPROVEMENTS / BUG FIXES:
- Improve the SSH "ready?" check. [GH-841] - Improve the SSH "ready?" check by more gracefully handling timeouts. [GH-841]
- Human friendly error if connection times out for HTTP downloads. [GH-849] - Human friendly error if connection times out for HTTP downloads. [GH-849]
- Detect when the VirtualBox installation is incomplete and error. [GH-846] - Detect when the VirtualBox installation is incomplete and error. [GH-846]
- Use `LogLevel QUIET` for SSH to suppress the known hosts warning. [GH-847]
- All `vagrant` commands that can take a target VM name can take one even - All `vagrant` commands that can take a target VM name can take one even
if you're not in a multi-VM environment. [GH-894] if you're not in a multi-VM environment. [GH-894]
- Hostname is set before networks are setup to avoid very slow `sudo` - Hostname is set before networks are setup to avoid very slow `sudo`
speeds on CentOS. [GH-922] speeds on CentOS. [GH-922]
- `config.ssh.shell` now includes the flags to pass to it, such as `-l` [GH-917] - `config.ssh.shell` now includes the flags to pass to it, such as `-l` [GH-917]
- The check for whether a port is open or not is more complete. [GH-948] - The check for whether a port is open or not is more complete by
catching ENETUNREACH errors. [GH-948]
- SSH uses LogLevel FATAL so that errors are still shown. - SSH uses LogLevel FATAL so that errors are still shown.
- Sending a SIGINT (Ctrl-C) very early on when executing `vagrant` no - Sending a SIGINT (Ctrl-C) very early on when executing `vagrant` no
longer results in an ugly stack trace. longer results in an ugly stack trace.
- Chef JSON configuration output is now pretty-printed to be - Chef JSON configuration output is now pretty-printed to be
human readable. [GH-1146] human readable. [GH-1146]
- SSH retries in the face of a `EHOSTUNREACH` error, improving the robustness
that SSHing succeeds when booting a machine. that SSHing succeeds when booting a machine.
- VMs in the "guru meditation" state can be destroyed now using - VMs in the "guru meditation" state can be destroyed now using
`vagrant destroy`. `vagrant destroy`.
- Fix issue where changing SSH key permissions didn't properly work. [GH-911] - Fix issue where changing SSH key permissions didn't properly work. [GH-911]
- Disable the NAT DNS proxy when the DNS server is already proxied to
localhost on Linux machines. This fixes issues with 12.04. [GH-909]
- Fix issue where Vagrant didn't properly detect VBoxManage on Windows - Fix issue where Vagrant didn't properly detect VBoxManage on Windows
if VBOX_INSTALL_PATH contained multiple paths. [GH-885] if VBOX_INSTALL_PATH contained multiple paths. [GH-885]
- Fix typo in setting host name for Gentoo guests. [GH-931] - Fix typo in setting host name for Gentoo guests. [GH-931]