Properly pass return codes back to shell in release builds

2 files changed, 39 insertions, 38 deletions

diff --git a/scripts/RELEASE.txt b/scripts/RELEASE.txt
index 476d8da..cf99eed 100644
--- a/scripts/RELEASE.txt
+++ b/scripts/RELEASE.txt
@@ -20,4 +20,38 @@ PREP
 
  * Commit all changes to premake-stable
 
- * Tag premake-stable with the version number
+ * Tag premake-stable with the version number and push
+
+ * Pull changes to premake-dev
+
+
+BUILD
+
+ * On each platform, run `premake4 release {version} binary`
+
+ * On one platform, run `premake4 release {version} source`
+
+ * If desired, copy binary to local path
+
+ * Upload packages (in release/) to SourceForge
+
+
+RELEASE
+
+ * On SourceForge, set package properties (platform, etc.)
+
+ * Update the download page
+   http://industriousone.com/premake/download
+
+ * Post release announcement to the forums
+
+ * Update the Latest News on the project home page
+
+ * Post annoucement to @industrious on Twitter
+
+ * Post announcement to email list
+
+ * Post announcement to Industrious Facebook group
+
+ * Add release to Freshmeat
+   http://freshmeat.net/projects/premake
diff --git a/scripts/release.lua b/scripts/release.lua
index c486753..e11757a 100644
--- a/scripts/release.lua
+++ b/scripts/release.lua
@@ -1,31 +1,8 @@
 --
 -- Prepare a new Premake release. This is still incomplete and some manual
--- work is needed to get everything packaged up.
---
--- BEFORE RUNNING THIS SCRIPT:
---  * Make sure all tests pass on Windows AND Posix systems
---  * Update CHANGELOG.txt
---  * Run `premake4 embed`
---  * Commit all changes to premake-stable
---  * Tag premake-stable with the version number
---  * Prepare release news item
---
--- RUN THE SCRIPT:
---  On each platform, run `premake4 release x.x binary`
---     (and copy binary to /usr/local/bin if desired)
---  On one platform, run `premake4 release x.x source`
+-- work is needed to get everything packaged up. See RELEASE.txt in this
+-- folder for the full checklist.
 --  
--- AFTER RUNNING THIS SCRIPT:
---  * Upload release files to SourceForge
---  * On SourceForge, set file platforms and release changelog
---  * Update the download page on Industrious One
---  * Post the news item to the forums
---  * Update the Premake project page on Industrious One
---  * Post to Twitter
---  * Send to email list
---  * Add release to Freshmeat (http://freshmeat.net/projects/premake)
---  * Push changes to repositories on BitBucket
---
 -- Info on using Mercurial to manage releases:
 --  http://hgbook.red-bean.com/read/managing-releases-and-branchy-development.html
 --  http://stevelosh.com/blog/2009/08/a-guide-to-branching-in-mercurial/
@@ -84,14 +61,7 @@ function dorelease()
 --
 
    print( "")
-   print( "BEFORE RUNNING THIS SCRIPT you should..." )
-   print( "* Pass all tests on Windows AND Posix systems" )
-   print( "* Update CHANGELOG.txt")
-   print( "* Run `premake4 embed`")
-   print( "* Commit all changes to premake-stable" )
-   print( "* Tag premake-stable with the version number" )
-   print( "* Prepare release news item")
-
+   print( "BEFORE RUNNING THIS SCRIPT follow the checklist in RELEASE.txt" )
    print( "")
    print( "Press [Enter] to begin.")
    io .read()
@@ -236,11 +206,8 @@ function dorelease()
 -- Clean up
 --
 	
+	os.rmdir(pkgname)
 	
---
--- Remind me of required next steps
---
-
 	print("")
 	print( "Finished.")