Updated Creating a new Wagtail release (markdown)

Matt Westcott 2016-08-26 11:30:40 +01:00
parent 1308e6e994
commit fad6ee1eb2
1 changed files with 12 additions and 12 deletions

@ -16,26 +16,26 @@ You will need the `wheel` and `twine` packages (`pip install wheel`, `pip instal
Create a fresh clone of the Wagtail repo, and check out the appropriate 'stable' branch.
git clone https://github.com/torchbox/wagtail.git
cd wagtail
git checkout stable/1.<x>.x
git clone https://github.com/torchbox/wagtail.git
cd wagtail
git checkout stable/1.<x>.x
(Using a Vagrant dev instance will not work: running the setup.py command within Vagrant will fail because it creates symlinks, which aren't supported by Virtualbox shared folders; and running it on the host machine will fail because it will try to run the copy of node-sass in node_modules, which is built for the VM's architecture. Also, by creating a fresh clone, we minimise the risk of having random development files floating around the codebase that screw up the package.)
From the root of the wagtail codebase, run:
npm install
python ./setup.py sdist
python ./setup.py bdist_wheel
npm install
python ./setup.py sdist
python ./setup.py bdist_wheel
This will create a .tar.gz package and a .whl package in the 'dist' directory. We now need to test that these installs successfully - from a location other than wagtail root (because the presence of the 'wagtail' directory confuses the installer), run:
mkvirtualenv wagtailinstalltest
pip install /path/to/wagtail-0.x.x.tar.gz
wagtail start myproject
cd myproject
./manage.py migrate
./manage.py runserver
mkvirtualenv wagtailinstalltest
pip install /path/to/wagtail-0.x.x.tar.gz
wagtail start myproject
cd myproject
./manage.py migrate
./manage.py runserver
and confirm that the site starts up successfully at http://localhost:8000/ . Repeat the test with the .whl package. (Note that bringing up a Vagrant VM will not work at this point, because the provisioning script will try to install a version of Wagtail that isn't on PyPI yet)