<blockquote> <p><strong><span class="caps">NOTE</span></strong>: The instructions on this page are useful only to developers who have been given permission to release gems on behalf of the SproutCore project.</p> </blockquote> <p>Before you can do a release, you will need to get your machine configured.</p> <p>After <a href="http://rubyforge.org/projects/sproutcore/">verifying that you are a SproutCore Project Admin at rubyforge</a>, install the <strong>hoe</strong> rubygem:</p> <pre class="console"><code>sudo gem install hoe --include-dependencies </code></pre> <p>Then do the required <strong>rubyforge</strong> setup:</p> <pre class="console"><code>rubyforge setup rubyforge config rubyforge login # cache a cookie for further operations </code></pre> <p>Then install the <strong>sproutcore</strong> rubygem:</p> <pre class="console"><code>sudo gem install merb-core -v 0.9.4 sudo gem install sproutcore </code></pre> <p>Now clone <strong>sproutcore-buildtools</strong> and <strong>sproutcore-samples</strong>:</p> <pre class="console"><code>cd /path/to/work-directory git clone git@github.com:sproutit/sproutcore-buildtools.git sproutcore-buildtools git clone git@github.com:sproutit/sproutcore-samples.git sproutcore-samples </code></pre> <p>Next, obtain the submodules of <strong>sproutcore-buildtools</strong> and configure them to use the correct origin repository and the <em>master</em> branch:</p> <pre class="console"><code>cd /path/to/work-directory/sproutcore-buildtools git submodule init git submodule update cd frameworks/sproutcore git remote add origin git@github.com:sproutit/sproutcore.git git checkout master cd ../prototype git remote add origin git@github.com:sproutit/sproutcore-prototype.git git checkout master cd ../../clients/sc_docs git remote add origin git@github.com:sproutit/sproutcore-doctool.git git checkout master cd ../sc_test_runner git remote add origin git@github.com:sproutit/sproutcore-testrunner.git git checkout master </code></pre> <p>Finally, remove the (empty) <strong>prototype</strong> and <strong>sproutcore</strong> frameworks in <strong>sproutcore-samples</strong>:</p> <pre class="console"><code>cd /path/to/work-directory/sproutcore-samples rm -R frameworks/prototype frameworks/sproutcore </code></pre> <h2>Preparing for the Release</h2> <ul> <li>Merge any required changes into the <strong>sproutcore-buildtools</strong> or <strong>sproutcore</strong> projects, or any of the other projects (<strong>sc_docs</strong>, <strong>sc_test_runner</strong>, <strong>prototype</strong>, and <strong>sproutcore-samples</strong>).</li> <li>Make sure you update the <code>HISTORY</code> and <code>History.txt</code> files in those projects to list any changes for the new release.</li> <li>Make sure that all your code is committed in git, including any added files.</li> <li>Make sure you&#8217;ve done a quick test of any affected areas.</li> <li><strong>Run all unit tests on all supported browsers to make sure they pass.</strong></li> </ul> <h2>Doing the Release</h2> <p>Update the ruby source code to the latest version number:</p> <pre class="console"><code>cd /path/to/work-directory/sproutcore-buildtools mate lib/sproutcore/version.rb # edit file in TextMate </code></pre> <p>Then, create the gem and deploy it locally (only):</p> <pre class="console"><code>cd /path/to/work-directory/sproutcore-buildtools rake manifest:refresh git commit -a -m 'Update support files for release 0.9.X' git push rake local_deploy </code></pre> <p>You should now have the new gem deployed locally on your machine. Run the samples:</p> <pre class="console"><code>cd /path/to/work-directory/sproutcore-samples sc-server </code></pre> <p>Do a quick check of the functionality for all of the demo apps to make sure none of your changes introduced any regressions. Depending on what code was changed, you may also need to try generating new apps, etc.</p> <p>Once you have completed a quicklook, you can proceed with the actual deployment:</p> <pre class="console"><code>cd /path/to/work-directory/sproutcore-buildtools rake release VERSION=0.9.X </code></pre> <p>You will need to enter the RubyForge password several times. Finally, you will need to tag <strong>sproutcore</strong>:</p> <pre class="console"><code>cd /path/to/work-directory/sproutcore-buildtools git tag REL-0.9.X git push --tags cd frameworks/sproutcore git tag REL-0.9.X git push --tags </code></pre> <h2>Announcing the Release</h2> <p>At this point you should have SproutCore deployed. You now need to notify everyone. The best thing is to do the following:</p> <ul> <li>Prepare a blog entry that highlights the major points and includes the full list of changes for both the framework and the build tools (copied directly from the <code>HISTORY</code> files.) Post to the <a href="http://www.sproutcore.com/blog">sproutcore.com</a> blog.</li> <li>Post an email to the sproutcore mailing list notifying everyone of the release, with a link to the blog entry. Begin the subject line with <code>[ANN]</code>.</li> <li>Update the topic on the <span class="caps">IRC</span> channel (you must be a channel admin to do so).</li> </ul> 2008-08-27T21:03:25-07:00 49984 releasing-a-sproutcore-gem 18944 2008-09-21T15:37:22-07:00 11814