haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated changelog

This commit is contained in:
Mitchell Hashimoto 2010-04-13 23:21:52 -07:00
parent a79eeb263d
commit 06d68605a0
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/changes/changes_02x_03x.md
View File

@ -9,10 +9,19 @@ and based on the feedback in `#vagrant`, the mailing list, and twitter, people h
using Vagrant quite successfully.
This stability allowed us to focus on refinement and new features for Vagrant `0.3.x`.
Best of all, there are **no backwards incompatible** changes in `0.3.x`
**TODO BEFORE 0.3.x RELASE: MUCH MORE TO COME**
## `vagrant` Command Changes
`vagrant down` is now `vagrant destroy`. A deprecation warning has been inserted
into `0.3.0` but will be removed completely for any subsequent release.
Additionally, the `vagrant` commands are no longer "git style" binaries. This means
that the `vagrant up` is no longer equivalent to `vagrant-up`. The space is now
mandatory. This was required to improve extensibility and functionality of the
specific commands.
## Improved Packaging
While Vagrant makes it easy to package (and repackage) environments for