David Glasser 0eff9604fc use meteor --get-ready instead of --version in places where we're trying to make ...

sure a checkout is complete

2013-03-29 11:52:33 -07:00

..

publish-release

fixes for per-arch packages

2013-03-29 11:52:33 -07:00

upgrade-to-engine

use meteor --get-ready instead of --version in places where we're trying to make

2013-03-29 11:52:33 -07:00

banner.txt

Overhaul release blessing process.

2013-03-22 19:15:18 -07:00

bless-release.js

fixes for per-arch packages

2013-03-29 11:52:33 -07:00

build-package-tarballs.sh

build arch-specific packages, which contain NPM modules!

2013-03-29 11:52:33 -07:00

build-release.sh

build arch-specific packages, which contain NPM modules!

2013-03-29 11:52:33 -07:00

build-tools-tarballs.sh

build arch-specific packages, which contain NPM modules!

2013-03-29 11:52:33 -07:00

build-tools-tree.sh

build arch-specific packages, which contain NPM modules!

2013-03-29 11:52:33 -07:00

deploy-examples.sh

"tools" -> "scripts", "engine" -> "tools"

2013-03-19 18:19:31 -07:00

find-new-npm-versions.sh

"tools" -> "scripts", "engine" -> "tools"

2013-03-19 18:19:31 -07:00

install-engine.sh

Call "uname plus arch" the "platform".

2013-03-29 11:52:33 -07:00

launch-meteor

Call "uname plus arch" the "platform".

2013-03-29 11:52:33 -07:00

notices.json

changelog -> notices

2013-03-19 23:45:06 -07:00

publish-release.sh

publish-release now lets you specify the git rev to publish (from jenkins)

2013-03-22 16:01:21 -07:00

spark-standalone.sh

"tools" -> "scripts", "engine" -> "tools"

2013-03-19 18:19:31 -07:00