Skip to content

Commit

Permalink
Merge branch 'master' of github.com:mapbox/tilemill
Browse files Browse the repository at this point in the history
  • Loading branch information
Dane Springmeyer committed Oct 10, 2012
2 parents 9563670 + bfc8022 commit aa488e8
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions platforms/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,15 @@ They are a work in progress. Please ask questions to fill in holes.

## Overall workflow

1. Test, do dev builds, make sure all dependencies are tagged and stable versions are good

1. Increment the version in package.json

1. Tag tilemill:

VERSION="0.10.1"
git tag v$VERSION -m "tagging v$VERSION"

1. OSX builds: use mini build machine, simply tweak the [build script](https://github.com/mapbox/tilemill-builder-osx) to checkout a tilemill tag (instead of master) and run the tweaked script manually. Download .zip to local machine, upload to github downloads page, then go back into local source tilemill checkout, run `make sparkle` and then use that to update the `_posts/0100-01-01-CHANGELOG.md`.

1. Windows - only Dane has a working VM at this point. Steps to setup VM are hard, but based on [mapnik-packaging repo instructions](https://github.com/mapnik/mapnik-packaging) and visual studio 2010. Tested only on Windows 7 so far but any Windows version should work. Build mapnik and deps, then build tilemill by running the scripts in `platforms/windows` first `build.bat` then `package.bat` then `run-tilemill.bat`. Confirm things work, then go package the installer by running the nsis script in `platforms\windows\installer` after modifying the version # in the script. Then upload to github downloads.
Expand All @@ -16,3 +25,5 @@ They are a work in progress. Please ask questions to fill in holes.
1. Publish TileMill to npm (which is what windows and linux use to indicated update availability)

1. Write blog post, update download links, changelog and upgrade notes like #1702

1. Ensure key plugins are republished to support the new version

0 comments on commit aa488e8

Please sign in to comment.