Skip to content
This repository
Browse code

Regen'd website.

  • Loading branch information...
commit 7ae451a14edb64edda765a8bb30dce47d33838ac 1 parent 24758b4
Brian Shirai brixen authored

Showing 50 changed files with 641 additions and 45 deletions. Show diff stats Hide diff stats

  1. +263 0 web/_site/2011/06/07/inside-rubinius-20-preview/index.html
  2. +166 0 web/_site/blog/index.html
  3. +9 0 web/_site/blog/posts_index/index.html
  4. +1 1  web/_site/doc/de/getting-started/building/index.html
  5. +1 1  web/_site/doc/de/how-to/fix-a-failing-spec/index.html
  6. +1 1  web/_site/doc/de/how-to/write-a-ruby-spec/index.html
  7. +1 1  web/_site/doc/de/how-to/write-a-ticket/index.html
  8. +1 1  web/_site/doc/de/what-is-rubinius/index.html
  9. +1 1  web/_site/doc/en/garbage-collector/large-objects/index.html
  10. +1 1  web/_site/doc/en/garbage-collector/mature-generation/index.html
  11. +1 1  web/_site/doc/en/getting-started/building/index.html
  12. +1 1  web/_site/doc/en/how-to/fix-a-failing-spec/index.html
  13. +1 1  web/_site/doc/en/how-to/write-a-blog-post/index.html
  14. +1 1  web/_site/doc/en/how-to/write-a-ruby-spec/index.html
  15. +1 1  web/_site/doc/en/how-to/write-a-ticket/index.html
  16. +1 1  web/_site/doc/en/what-is-rubinius/index.html
  17. +1 1  web/_site/doc/es/getting-started/building/index.html
  18. +1 1  web/_site/doc/es/how-to/fix-a-failing-spec/index.html
  19. +1 1  web/_site/doc/es/how-to/write-a-ruby-spec/index.html
  20. +1 1  web/_site/doc/es/how-to/write-a-ticket/index.html
  21. +1 1  web/_site/doc/es/what-is-rubinius/index.html
  22. +1 1  web/_site/doc/fr/getting-started/building/index.html
  23. +1 1  web/_site/doc/fr/how-to/fix-a-failing-spec/index.html
  24. +1 1  web/_site/doc/fr/how-to/write-a-blog-post/index.html
  25. +1 1  web/_site/doc/fr/how-to/write-a-ruby-spec/index.html
  26. +1 1  web/_site/doc/fr/how-to/write-a-ticket/index.html
  27. +1 1  web/_site/doc/fr/what-is-rubinius/index.html
  28. +1 1  web/_site/doc/ja/getting-started/building/index.html
  29. +1 1  web/_site/doc/ja/how-to/fix-a-failing-spec/index.html
  30. +1 1  web/_site/doc/ja/how-to/write-a-ruby-spec/index.html
  31. +1 1  web/_site/doc/ja/how-to/write-a-ticket/index.html
  32. +1 1  web/_site/doc/ja/what-is-rubinius/index.html
  33. +1 1  web/_site/doc/pl/getting-started/building/index.html
  34. +1 1  web/_site/doc/pl/how-to/fix-a-failing-spec/index.html
  35. +1 1  web/_site/doc/pl/how-to/write-a-ruby-spec/index.html
  36. +1 1  web/_site/doc/pl/how-to/write-a-ticket/index.html
  37. +1 1  web/_site/doc/pl/what-is-rubinius/index.html
  38. +1 1  web/_site/doc/pt-br/getting-started/building/index.html
  39. +1 1  web/_site/doc/pt-br/how-to/fix-a-failing-spec/index.html
  40. +1 1  web/_site/doc/pt-br/how-to/write-a-blog-post/index.html
  41. +1 1  web/_site/doc/pt-br/how-to/write-a-ruby-spec/index.html
  42. +1 1  web/_site/doc/pt-br/how-to/write-a-ticket/index.html
  43. +1 1  web/_site/doc/pt-br/what-is-rubinius/index.html
  44. +1 1  web/_site/doc/ru/getting-started/building/index.html
  45. +1 1  web/_site/doc/ru/how-to/fix-a-failing-spec/index.html
  46. +1 1  web/_site/doc/ru/how-to/write-a-ruby-spec/index.html
  47. +1 1  web/_site/doc/ru/how-to/write-a-ticket/index.html
  48. +1 1  web/_site/doc/ru/what-is-rubinius/index.html
  49. +158 0 web/_site/feed/atom.xml
  50. BIN  web/_site/images/rubinius-2-0-developer-preview-blog-post.png
263 web/_site/2011/06/07/inside-rubinius-20-preview/index.html
... ... @@ -0,0 +1,263 @@
  1 +<!DOCTYPE html>
  2 +<html>
  3 + <head>
  4 + <title>Inside the Rubinius 2.0 Preview Release - Rubinius</title>
  5 + <meta content='text/html;charset=utf-8' http-equiv='content-type'>
  6 + <meta content='en' http-equiv='content-language'>
  7 + <meta content='Rubinius is an implementation of the Ruby programming language. The Rubinius bytecode virtual machine is written in C++. The bytecode compiler is written in pure Ruby. The vast majority of the core library is also written in Ruby, with some supporting primitives that interact with the VM directly.' name='description'>
  8 + <meta content='Less Than Three. &lt;3. http://less.thanthree.com' name='author'>
  9 + <link href='/' rel='home'>
  10 + <link href='/' rel='start'>
  11 +
  12 +
  13 + <link href='/feed/atom.xml' rel='alternate' type='application/atom+xml' title='Rubinius Blog' />
  14 + <!--[if IE]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js" type="text/javascript"></script><![endif]-->
  15 + <script src="/javascripts/jquery-1.3.2.js" type="text/javascript"></script>
  16 + <script src="/javascripts/paging_keys.js" type="text/javascript"></script>
  17 +
  18 + <script src="/javascripts/application.js" type="text/javascript"></script>
  19 + <style>article, aside, dialog, figure, footer, header, hgroup, menu, nav, section { display: block; }</style>
  20 +
  21 + <link href="/stylesheets/blueprint/screen.css" media="screen" rel="stylesheet" type="text/css" />
  22 + <link href="/stylesheets/application.css" media="screen" rel="stylesheet" type="text/css" />
  23 + <link href="/stylesheets/blueprint/print.css" media="print" rel="stylesheet" type="text/css" />
  24 + <!--[if IE]><link href="/stylesheets/blueprint/ie.css" media="screen" rel="stylesheet" type="text/css" /><![endif]-->
  25 + <!--[if IE]><link href="/stylesheets/ie.css" media="screen" rel="stylesheet" type="text/css" /><![endif]-->
  26 + <link href="/stylesheets/pygments.css" media="screen" rel="stylesheet" type="text/css" />
  27 + </head>
  28 + <body>
  29 + <div class='container'>
  30 + <div class='span-21 blog_menu'>
  31 + <header>
  32 + <nav>
  33 + <ul>
  34 + <li><a href="/">Home</a></li>
  35 + <li><a id="blog" href="/blog/">Blog</a></li>
  36 + <li><a id="documentation" href="/doc/en/">Documentation</a></li>
  37 + <li><a href="/projects/">Projects</a></li>
  38 + <li><a href="/roadmap/">Roadmap</a></li>
  39 + <li><a href="/releases/">Releases</a></li>
  40 + </ul>
  41 + </nav>
  42 +
  43 + </header>
  44 + </div>
  45 + <div class='span-3 last'>
  46 + <div id='version'>
  47 + <a href="/releases/1.2.3">1.2.3</a>
  48 + </div>
  49 + </div>
  50 +
  51 + </div>
  52 +
  53 + <div class="container posts_nav">
  54 + <nav>
  55 + <a href="/blog/posts_index/">Index of Posts</a>
  56 + <a id="feed_icon" href="/feed/atom.xml"><img alt="subscribe" src="/images/feed-icon16x16.png" /></a>
  57 + </nav>
  58 + </div>
  59 +
  60 +
  61 + <div class="container blog_posts">
  62 + <h2 class="post_title">Inside the Rubinius 2.0 Preview Release</h2>
  63 +
  64 + <div class="by_line">
  65 + <p><span class="author">Brian Ford</span>
  66 + <span class="date">07 June 2011</span>
  67 +
  68 + </p>
  69 + </div>
  70 +
  71 + <p>Houston, we have a problem. Complex projects are difficult to transition
  72 +forward and Rubinius is a complex project. Rubinius is at the point of a major
  73 +transition and we need your help to move forward.</p>
  74 +
  75 +<p>Just over a year ago, Rubinius released version 1.0. Since then, dozens of
  76 +contributors have added over 2,200 commits to the master branch and we have
  77 +released seven new versions. At the same time, we have added nearly 450
  78 +commits on a development branch to remove the global interpreter lock (GIL)
  79 +and begin adding Ruby 1.9 and Windows support.</p>
  80 +
  81 +<p><img src="/images/rubinius-2-0-developer-preview-blog-post.png" alt="Rubinius 2.0 Developer Preview" /></p>
  82 +
  83 +<p>Today we are releasing <em>Rubinius 2.0 Developer Preview</em>. The primary focus of
  84 +this release is true Ruby multi-threaded concurrency. Additionally, it
  85 +contains the beginnings of Ruby 1.9 and Microsoft Windows support.</p>
  86 +
  87 +<h3 id="rubinius-20-developer-preview">Rubinius 2.0 Developer Preview</h3>
  88 +
  89 +<p>We are seeking developers interested in running their Ruby and Rails projects
  90 +on Rubinius to help us iron out issues as we work toward the final 2.0
  91 +release. Let&rsquo;s look at the details of the 2.0 developer preview.</p>
  92 +
  93 +<p>One of the central features of Rubinius 2.0 is a fundamental change in the
  94 +threading architecture. In Rubinius 2.0, Ruby threads will run with true
  95 +concurrency. This means that if multi-core or multi-CPU hardware is available,
  96 +Ruby code on different threads will actually run in parallel.</p>
  97 +
  98 +<p>Another central feature of Rubinius 2.0 is support for both Ruby 1.8.7 and
  99 +Ruby 1.9.2 syntax. The Rubinius 2.0 support for Ruby 1.8.7 should be 100%
  100 +backward compatible with the support in the Rubinius master branch. The full
  101 +Ruby concurrency is enabled regardless of what language syntax mode is active.</p>
  102 +
  103 +<h3 id="repository-migration">Repository Migration</h3>
  104 +
  105 +<p>We are migrating the main Rubinius repository to the <a href="https://github.com/rubinius">Rubinius</a> organization.</p>
  106 +
  107 +<p>The RVM project has already been updated to work with the new repository. So
  108 +<code>rvm install rbx</code> will use the new repository. If you have an existing clone
  109 +of Rubinius, update and run <code>rake github</code> to point your existing repository to
  110 +the new one.</p>
  111 +
  112 +<p>You can clone directly from the <a href="https://github.com/rubinius/rubinius">new repository</a>.</p>
  113 +
  114 +<h3 id="installation">Installation</h3>
  115 +
  116 +<p>For testing Rubinius with your application, installing with RVM is probably
  117 +the easiest. To install the 2.0 developer preview, ensure that RVM is updated:</p>
  118 +
  119 +<pre><code>rvm get head
  120 +rvm reload
  121 +</code></pre>
  122 +
  123 +<p>Then, install the Rubinius 2.0.0pre branch:</p>
  124 +
  125 +<pre><code>rvm install rbx-2.0.0pre
  126 +</code></pre>
  127 +
  128 +<p>If you are interested in helping develop Rubinius, we suggest you clone the
  129 +repository directly and build. Rubinius runs fine from the source directory so
  130 +you don&rsquo;t need to install it. For more details about building from a clone,
  131 +see <a href="http://rubini.us/doc/en/getting-started/">Getting Started</a>.</p>
  132 +
  133 +<h3 id="configuration">Configuration</h3>
  134 +
  135 +<p>The goal of Rubinius 2.0 is to fully support both Ruby 1.8.7 and 1.9.2 in a
  136 +single executable. When running Rubinius, you can select which version to use.
  137 +There are configuration options to change which versions are supported and
  138 +which version is the default.</p>
  139 +
  140 +<p>The first configure option is <code>--enable-version=X[,Y]</code>. This option sets which
  141 +language versions will be supported. An example is:</p>
  142 +
  143 +<pre><code>./configure --enable-version=1.8,1.9
  144 +</code></pre>
  145 +
  146 +<p>The language versions can be specified as <code>18</code> or <code>1.8</code>. Multiple versions are
  147 +separated by a comma and no space.</p>
  148 +
  149 +<p>The second configure option is <code>--default-version=X</code>. This option sets which
  150 +language version is the default when running Rubinius. An example is:</p>
  151 +
  152 +<pre><code>./configure --default-version=1.9
  153 +</code></pre>
  154 +
  155 +<p>These options are intended to be used together. You must enable a version to
  156 +select it as the default, so the options must come in the following order:</p>
  157 +
  158 +<pre><code>./configure --enable-version=X,Y --default-version=Y
  159 +</code></pre>
  160 +
  161 +<p>Once you have enabled support for a language version, to select that mode when
  162 +running Rubinius, use the <code>-X18</code> or <code>-X19</code> command line switches. For example:</p>
  163 +
  164 +<pre><code>rbx -X19 -v
  165 +</code></pre>
  166 +
  167 +<p>This command will run Rubinius with the 1.9 language mode enabled.</p>
  168 +
  169 +<p>You may also use the <code>RBXOPT</code> environment variable to select the lanugage
  170 +mode. Assuming that 1.8 is the default mode, the following command would run
  171 +Rubinius with the 1.9 language mode enabled:</p>
  172 +
  173 +<pre><code>RBXOPT=-X19 rbx -v
  174 +</code></pre>
  175 +
  176 +<p>Right now, only the 1.8 language mode is enabled in the 2.0.0pre branch.
  177 +However, we will be enabling the 1.9 mode in the very near future. The default
  178 +mode will continue to be 1.8 unless you configure Rubinius to run in 1.9 mode.</p>
  179 +
  180 +<h3 id="building-on-windows">Building on Windows</h3>
  181 +
  182 +<p>On Windows, Rubinius uses the <a href="http://mingw-w64.sourceforge.net/">MinGW-w64</a>
  183 +compiler to build a native application. There remains a lot of work to do for
  184 +Windows support but the Rubinius VM is currently compiling on Windows 7.</p>
  185 +
  186 +<p>If you are a bleeding-edge Windows developer interested in diving into
  187 +Rubinius, here&rsquo;s how to get started:</p>
  188 +
  189 +<ol>
  190 + <li>Install <em>MRI 1.9</em> using <a href="http://rubyinstaller.org/">RubyInstaller</a>.</li>
  191 + <li>Install <a href="http://code.google.com/p/msysgit/">MSysGit</a>.</li>
  192 + <li>Install the 32bit or 64bit MinGW-w64 toolchain.</li>
  193 + <li>Clone the Rubinius repository.</li>
  194 + <li>In CMD, run <code>ruby configure</code>.</li>
  195 + <li>Run <code>rake</code>.</li>
  196 +</ol>
  197 +
  198 +<h3 id="moving-forward">Moving Forward</h3>
  199 +
  200 +<p>In the near future, we will release another version of Rubinius from the
  201 +current master branch. We hope to merge 2.0.0pre into master as soon as
  202 +possible and continue working toward the 2.0 final release. We&rsquo;ll make that
  203 +decision based on your reports about how the 2.0.0pre branch is working with
  204 +existing 1.8.7 applications.</p>
  205 +
  206 +<p>We greatly appreciate your help polishing up the Rubinius 2.0 release! Follow
  207 +us on <a href="http://twitter.com/rubinius">Twitter</a> for updates and stop by #rubinius
  208 +on freenode.net to chat about anything on your mind.</p>
  209 +
  210 +<h3 id="rubinius-support-on-engineyard-appcloud">Rubinius Support on EngineYard AppCloud</h3>
  211 +
  212 +<p>Rubinius 1.2.3 is currently in beta on Engine Yard AppCloud, and we encourage
  213 +users to <a href="http://docs.engineyard.com/rubinius.html">give it a try</a>. Engine
  214 +Yard will support Rubinius 2.0.0 after it’s officially released.</p>
  215 +
  216 +<p>To learn more about Rubinius, join Engine Yard for a <a href="http://pages.engineyard.com/RubyPlatformOptionsWebinarJuly212011.html">Platform Options Webinar</a> in July.</p>
  217 +
  218 +
  219 + <div id="disqus_thread"></div>
  220 +<script type="text/javascript">
  221 + var disqus_shortname = 'rubinius';
  222 + var disqus_identifier = '/2011/06/07/inside-rubinius-20-preview/';
  223 + var disqus_url = 'http://rubini.us/2011/06/07/inside-rubinius-20-preview/';
  224 +
  225 + (function() {
  226 + var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
  227 + dsq.src = 'http://' + disqus_shortname + '.disqus.com/embed.js';
  228 + (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
  229 + })();
  230 +</script>
  231 +<noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
  232 +
  233 + </div>
  234 + <footer>
  235 + <div class='container'>
  236 + <nav>
  237 + <ul>
  238 + <li><a href="http://twitter.com/rubinius">Follow Rubinius on Twitter</a></li>
  239 + <li><a href="http://github.com/evanphx/rubinius">Fork Rubinius on github</a></li>
  240 + <li><a href="http://engineyard.com">An Engine Yard project</a></li>
  241 +
  242 + <li id='credit'>
  243 + Site design by
  244 + <a href="http://less.thanthree.com">Less Than Three</a>
  245 + </li>
  246 + </ul>
  247 + </nav>
  248 + </div>
  249 + </footer>
  250 + <script type="text/javascript">
  251 + var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
  252 + document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
  253 + </script>
  254 +
  255 + <script type="text/javascript">
  256 + try {
  257 + var pageTracker = _gat._getTracker("UA-12328521-1");
  258 + pageTracker._trackPageview();
  259 + } catch(err) {}</script>
  260 +
  261 + </body>
  262 +
  263 +</html>
166 web/_site/blog/index.html
@@ -62,6 +62,172 @@
62 62
63 63 <div class="post">
64 64 <h2 class="post_title">
  65 + <a href="/2011/06/07/inside-rubinius-20-preview/" title="Inside the Rubinius 2.0 Preview Release" class="post_title">
  66 + Inside the Rubinius 2.0 Preview Release
  67 + </a>
  68 + </h2>
  69 + <div class="by_line">
  70 + <p><span class="author">Brian Ford</span>
  71 + <span class="date">07 June 2011</span>
  72 +
  73 + <a href="http://rubini.us/2011/06/07/inside-rubinius-20-preview/#disqus_thread"
  74 + data-disqus-identifier="/2011/06/07/inside-rubinius-20-preview/"></a>
  75 +
  76 +
  77 + </p>
  78 + </div>
  79 +
  80 + <p>Houston, we have a problem. Complex projects are difficult to transition
  81 +forward and Rubinius is a complex project. Rubinius is at the point of a major
  82 +transition and we need your help to move forward.</p>
  83 +
  84 +<p>Just over a year ago, Rubinius released version 1.0. Since then, dozens of
  85 +contributors have added over 2,200 commits to the master branch and we have
  86 +released seven new versions. At the same time, we have added nearly 450
  87 +commits on a development branch to remove the global interpreter lock (GIL)
  88 +and begin adding Ruby 1.9 and Windows support.</p>
  89 +
  90 +<p><img src="/images/rubinius-2-0-developer-preview-blog-post.png" alt="Rubinius 2.0 Developer Preview" /></p>
  91 +
  92 +<p>Today we are releasing <em>Rubinius 2.0 Developer Preview</em>. The primary focus of
  93 +this release is true Ruby multi-threaded concurrency. Additionally, it
  94 +contains the beginnings of Ruby 1.9 and Microsoft Windows support.</p>
  95 +
  96 +<h3 id="rubinius-20-developer-preview">Rubinius 2.0 Developer Preview</h3>
  97 +
  98 +<p>We are seeking developers interested in running their Ruby and Rails projects
  99 +on Rubinius to help us iron out issues as we work toward the final 2.0
  100 +release. Let&rsquo;s look at the details of the 2.0 developer preview.</p>
  101 +
  102 +<p>One of the central features of Rubinius 2.0 is a fundamental change in the
  103 +threading architecture. In Rubinius 2.0, Ruby threads will run with true
  104 +concurrency. This means that if multi-core or multi-CPU hardware is available,
  105 +Ruby code on different threads will actually run in parallel.</p>
  106 +
  107 +<p>Another central feature of Rubinius 2.0 is support for both Ruby 1.8.7 and
  108 +Ruby 1.9.2 syntax. The Rubinius 2.0 support for Ruby 1.8.7 should be 100%
  109 +backward compatible with the support in the Rubinius master branch. The full
  110 +Ruby concurrency is enabled regardless of what language syntax mode is active.</p>
  111 +
  112 +<h3 id="repository-migration">Repository Migration</h3>
  113 +
  114 +<p>We are migrating the main Rubinius repository to the <a href="https://github.com/rubinius">Rubinius</a> organization.</p>
  115 +
  116 +<p>The RVM project has already been updated to work with the new repository. So
  117 +<code>rvm install rbx</code> will use the new repository. If you have an existing clone
  118 +of Rubinius, update and run <code>rake github</code> to point your existing repository to
  119 +the new one.</p>
  120 +
  121 +<p>You can clone directly from the <a href="https://github.com/rubinius/rubinius">new repository</a>.</p>
  122 +
  123 +<h3 id="installation">Installation</h3>
  124 +
  125 +<p>For testing Rubinius with your application, installing with RVM is probably
  126 +the easiest. To install the 2.0 developer preview, ensure that RVM is updated:</p>
  127 +
  128 +<pre><code>rvm get head
  129 +rvm reload
  130 +</code></pre>
  131 +
  132 +<p>Then, install the Rubinius 2.0.0pre branch:</p>
  133 +
  134 +<pre><code>rvm install rbx-2.0.0pre
  135 +</code></pre>
  136 +
  137 +<p>If you are interested in helping develop Rubinius, we suggest you clone the
  138 +repository directly and build. Rubinius runs fine from the source directory so
  139 +you don&rsquo;t need to install it. For more details about building from a clone,
  140 +see <a href="http://rubini.us/doc/en/getting-started/">Getting Started</a>.</p>
  141 +
  142 +<h3 id="configuration">Configuration</h3>
  143 +
  144 +<p>The goal of Rubinius 2.0 is to fully support both Ruby 1.8.7 and 1.9.2 in a
  145 +single executable. When running Rubinius, you can select which version to use.
  146 +There are configuration options to change which versions are supported and
  147 +which version is the default.</p>
  148 +
  149 +<p>The first configure option is <code>--enable-version=X[,Y]</code>. This option sets which
  150 +language versions will be supported. An example is:</p>
  151 +
  152 +<pre><code>./configure --enable-version=1.8,1.9
  153 +</code></pre>
  154 +
  155 +<p>The language versions can be specified as <code>18</code> or <code>1.8</code>. Multiple versions are
  156 +separated by a comma and no space.</p>
  157 +
  158 +<p>The second configure option is <code>--default-version=X</code>. This option sets which
  159 +language version is the default when running Rubinius. An example is:</p>
  160 +
  161 +<pre><code>./configure --default-version=1.9
  162 +</code></pre>
  163 +
  164 +<p>These options are intended to be used together. You must enable a version to
  165 +select it as the default, so the options must come in the following order:</p>
  166 +
  167 +<pre><code>./configure --enable-version=X,Y --default-version=Y
  168 +</code></pre>
  169 +
  170 +<p>Once you have enabled support for a language version, to select that mode when
  171 +running Rubinius, use the <code>-X18</code> or <code>-X19</code> command line switches. For example:</p>
  172 +
  173 +<pre><code>rbx -X19 -v
  174 +</code></pre>
  175 +
  176 +<p>This command will run Rubinius with the 1.9 language mode enabled.</p>
  177 +
  178 +<p>You may also use the <code>RBXOPT</code> environment variable to select the lanugage
  179 +mode. Assuming that 1.8 is the default mode, the following command would run
  180 +Rubinius with the 1.9 language mode enabled:</p>
  181 +
  182 +<pre><code>RBXOPT=-X19 rbx -v
  183 +</code></pre>
  184 +
  185 +<p>Right now, only the 1.8 language mode is enabled in the 2.0.0pre branch.
  186 +However, we will be enabling the 1.9 mode in the very near future. The default
  187 +mode will continue to be 1.8 unless you configure Rubinius to run in 1.9 mode.</p>
  188 +
  189 +<h3 id="building-on-windows">Building on Windows</h3>
  190 +
  191 +<p>On Windows, Rubinius uses the <a href="http://mingw-w64.sourceforge.net/">MinGW-w64</a>
  192 +compiler to build a native application. There remains a lot of work to do for
  193 +Windows support but the Rubinius VM is currently compiling on Windows 7.</p>
  194 +
  195 +<p>If you are a bleeding-edge Windows developer interested in diving into
  196 +Rubinius, here&rsquo;s how to get started:</p>
  197 +
  198 +<ol>
  199 + <li>Install <em>MRI 1.9</em> using <a href="http://rubyinstaller.org/">RubyInstaller</a>.</li>
  200 + <li>Install <a href="http://code.google.com/p/msysgit/">MSysGit</a>.</li>
  201 + <li>Install the 32bit or 64bit MinGW-w64 toolchain.</li>
  202 + <li>Clone the Rubinius repository.</li>
  203 + <li>In CMD, run <code>ruby configure</code>.</li>
  204 + <li>Run <code>rake</code>.</li>
  205 +</ol>
  206 +
  207 +<h3 id="moving-forward">Moving Forward</h3>
  208 +
  209 +<p>In the near future, we will release another version of Rubinius from the
  210 +current master branch. We hope to merge 2.0.0pre into master as soon as
  211 +possible and continue working toward the 2.0 final release. We&rsquo;ll make that
  212 +decision based on your reports about how the 2.0.0pre branch is working with
  213 +existing 1.8.7 applications.</p>
  214 +
  215 +<p>We greatly appreciate your help polishing up the Rubinius 2.0 release! Follow
  216 +us on <a href="http://twitter.com/rubinius">Twitter</a> for updates and stop by #rubinius
  217 +on freenode.net to chat about anything on your mind.</p>
  218 +
  219 +<h3 id="rubinius-support-on-engineyard-appcloud">Rubinius Support on EngineYard AppCloud</h3>
  220 +
  221 +<p>Rubinius 1.2.3 is currently in beta on Engine Yard AppCloud, and we encourage
  222 +users to <a href="http://docs.engineyard.com/rubinius.html">give it a try</a>. Engine
  223 +Yard will support Rubinius 2.0.0 after it’s officially released.</p>
  224 +
  225 +<p>To learn more about Rubinius, join Engine Yard for a <a href="http://pages.engineyard.com/RubyPlatformOptionsWebinarJuly212011.html">Platform Options Webinar</a> in July.</p>
  226 +
  227 + </div>
  228 +
  229 + <div class="post">
  230 + <h2 class="post_title">
65 231 <a href="/2011/05/26/rubinius-rewards/" title="Announcing Rubinius Rewards" class="post_title">
66 232 Announcing Rubinius Rewards
67 233 </a>
9 web/_site/blog/posts_index/index.html
@@ -55,6 +55,15 @@
55 55 <ul>
56 56
57 57 <li>
  58 + <a href="/2011/06/07/inside-rubinius-20-preview/" title="Inside the Rubinius 2.0 Preview Release" class="post_title"> Inside the Rubinius 2.0 Preview Release </a>
  59 + <span class="author">Brian Ford</span>
  60 + <span class="date">07 June 2011</span>
  61 + <a href="http://rubini.us/2011/06/07/inside-rubinius-20-preview/#disqus_thread"
  62 + data-disqus-identifier="/2011/06/07/inside-rubinius-20-preview/"></a>
  63 +
  64 + </li>
  65 +
  66 + <li>
58 67 <a href="/2011/05/26/rubinius-rewards/" title="Announcing Rubinius Rewards" class="post_title"> Announcing Rubinius Rewards </a>
59 68 <span class="author">Shane Becker</span>
60 69 <span class="date">26 May 2011</span>
2  web/_site/doc/de/getting-started/building/index.html
@@ -164,7 +164,7 @@ <h3 id="beschaffen-des-quellcodes">Beschaffen des Quellcodes</h3>
164 164
165 165 <ol>
166 166 <li>Wechsle in dein Entwicklungsverzeichnis</li>
167   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  167 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
168 168 </ol>
169 169
170 170 <h3 id="rubinius-installieren">Rubinius installieren</h3>
2  web/_site/doc/de/how-to/fix-a-failing-spec/index.html
@@ -170,7 +170,7 @@
170 170 willst.</li>
171 171 <li>Erstelle ein Gist (auf http://gist.github.com) mit deinem Patch und
172 172 verlinke es in einem neuen Ticket im Issuetracker auf Github:
173   -http://github.com/evanphx/rubinius/issues Es können mehrere Patches pro
  173 +http://github.com/rubinius/rubinius/issues Es können mehrere Patches pro
174 174 Ticket hinzugefügt werden.</li>
175 175 </ol>
176 176
2  web/_site/doc/de/how-to/write-a-ruby-spec/index.html
@@ -155,7 +155,7 @@
155 155 <li>Führe <code>git format-patch</code> aus</li>
156 156 <li>Erstelle ein Gist (auf http://gist.github.com) mit deinem Patch und
157 157 verlinke diesen in einem Ticket auf dem Issuetracker:
158   -<a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a></li>
  158 +<a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a></li>
159 159 </ol>
160 160
161 161
2  web/_site/doc/de/how-to/write-a-ticket/index.html
@@ -137,7 +137,7 @@
137 137
138 138
139 139 <p>Den Rubinius Issuetracker findest du hier:
140   -<a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
  140 +<a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
141 141
142 142 <p>Damit ein Ticket nützlich ist, sollte es prägnant, fokussiert und umsetzbar
143 143 sein. Falls es diese Kriterien nicht erfüllt, wird es vermutlich nur den
2  web/_site/doc/de/what-is-rubinius/index.html
@@ -157,7 +157,7 @@ <h2 id="installation">Installation</h2>
157 157 Informationen siehe auch: <a href="/doc/de/getting-started/">Erste Schritte</a>.</p>
158 158
159 159 <ol>
160   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  160 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
161 161 <li><code>cd rubinius</code></li>
162 162 <li><code>./configure --prefix=/pfad/zum/installations/verzeichnis</code></li>
163 163 <li><code>rake install</code></li>
2  web/_site/doc/en/garbage-collector/large-objects/index.html
@@ -158,7 +158,7 @@
158 158 </code></pre>
159 159
160 160 <p>For more information on configuration variables available read the
161   -<a href="https://github.com/evanphx/rubinius/blob/master/vm/configuration.hpp">vm configuration source file </a></p>
  161 +<a href="https://github.com/rubinius/rubinius/blob/master/vm/configuration.hpp">vm configuration source file </a></p>
162 162
163 163
164 164
2  web/_site/doc/en/garbage-collector/mature-generation/index.html
@@ -153,7 +153,7 @@
153 153 via gc.lifetime. gc.lifetime is used by autotune which sets the initial value.</p>
154 154
155 155 <p>For more information on configuration variables available read the
156   -<a href="https://github.com/evanphx/rubinius/blob/master/vm/configuration.hpp">vm configuration source file </a></p>
  156 +<a href="https://github.com/rubinius/rubinius/blob/master/vm/configuration.hpp">vm configuration source file </a></p>
157 157
158 158
159 159
2  web/_site/doc/en/getting-started/building/index.html
@@ -156,7 +156,7 @@ <h3 id="getting-the-source">Getting the Source</h3>
156 156
157 157 <ol>
158 158 <li>Change your current working directory to your development directory</li>
159   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  159 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
160 160 </ol>
161 161
162 162 <h3 id="installing-rubinius">Installing Rubinius</h3>
2  web/_site/doc/en/how-to/fix-a-failing-spec/index.html
@@ -163,7 +163,7 @@
163 163 -N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
164 164 generate patches.</li>
165 165 <li>Create a gist with your patch and link to it in a ticket on the issue
166   -tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
  166 +tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
167 167 patches to one ticket.</li>
168 168 </ol>
169 169
2  web/_site/doc/en/how-to/write-a-blog-post/index.html
@@ -145,7 +145,7 @@
145 145
146 146 <p>Clone Rubinius repository as that is where the website and posts are stored.</p>
147 147
148   -<pre><code>git clone https://github.com/evanphx/rubinius.git
  148 +<pre><code>git clone https://github.com/rubinius/rubinius.git
149 149 </code></pre>
150 150
151 151 <p>To get started, ensure you have the <code>kramdown</code> and <code>jekyll</code> gems installed.</p>
2  web/_site/doc/en/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
152 152 <li>Commit your changes</li>
153 153 <li>Use <code>git format-patch</code></li>
154 154 <li>Create a gist with your patch and link to it in a ticket on the issue
155   -tracker at <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</li>
  155 +tracker at <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</li>
156 156 </ol>
157 157
158 158
2  web/_site/doc/en/how-to/write-a-ticket/index.html
@@ -136,7 +136,7 @@
136 136
137 137
138 138
139   - <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
  139 + <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
140 140
141 141 <p>To be useful, tickets must be concise, focused, and actionable. If not, the
142 142 ticket will languish and become clutter. Accordingly, tickets must fall into
2  web/_site/doc/en/what-is-rubinius/index.html
@@ -157,7 +157,7 @@ <h2 id="installing">Installing</h2>
157 157 see <a href="/doc/en/getting-started/">Getting Started</a>.</p>
158 158
159 159 <ol>
160   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  160 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
161 161 <li><code>cd rubinius</code></li>
162 162 <li><code>./configure --prefix=/path/to/install/dir</code></li>
163 163 <li><code>rake install</code></li>
2  web/_site/doc/es/getting-started/building/index.html
@@ -157,7 +157,7 @@ <h3 id="obtencin-del-cdigo-fuente">Obtención del Código Fuente</h3>
157 157 <ol>
158 158 <li>Utilice la linea de comandos para entrar a su directorio de
159 159 desarrollo.</li>
160   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  160 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
161 161 </ol>
162 162
163 163 <h3 id="instalacin-de-rubinius">Instalación de Rubinius</h3>
2  web/_site/doc/es/how-to/fix-a-failing-spec/index.html
@@ -171,7 +171,7 @@
171 171 -N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
172 172 generate patches.</li>
173 173 <li>Create a gist with your patch and link to it in a ticket on the issue
174   -tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
  174 +tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
175 175 patches to one ticket.</li>
176 176 </ol>
177 177
2  web/_site/doc/es/how-to/write-a-ruby-spec/index.html
@@ -160,7 +160,7 @@
160 160 <li>Commit your changes</li>
161 161 <li>Use <code>git format-patch</code></li>
162 162 <li>Create a gist with your patch and link to it in a ticket on the issue
163   -tracker at http://github.com/evanphx/rubinius/issues.</li>
  163 +tracker at http://github.com/rubinius/rubinius/issues.</li>
164 164 </ol>
165 165
166 166
2  web/_site/doc/es/how-to/write-a-ticket/index.html
@@ -144,7 +144,7 @@
144 144
145 145
146 146
147   - <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
  147 + <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
148 148
149 149 <p>Para ser útiles, los boletos deben ser concisas, específicas y acciones
150 150 concretas. Si no, el boleto languidecen y se convierten en el desorden. En
2  web/_site/doc/es/what-is-rubinius/index.html
@@ -157,7 +157,7 @@ <h2 id="instalacin">Instalación</h2>
157 157 más detallada, vea <a href="/doc/es/getting-started/">Primeros pasos</a>.</p>
158 158
159 159 <ol>
160   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  160 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
161 161 <li><code>cd rubinius</code></li>
162 162 <li><code>./configure --prefix=/path/to/install/dir</code></li>
163 163 <li><code>rake install</code></li>
2  web/_site/doc/fr/getting-started/building/index.html
@@ -159,7 +159,7 @@ <h3 id="rcuprer-les-sources">Récupérer les sources</h3>
159 159
160 160 <ol>
161 161 <li>Changez de répertoire courant vers votre répertoire de développement</li>
162   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  162 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
163 163 </ol>
164 164
165 165 <h3 id="installer-rubinius">Installer Rubinius</h3>
2  web/_site/doc/fr/how-to/fix-a-failing-spec/index.html
@@ -157,7 +157,7 @@
157 157 <li>Exécutez <code>git status, git add, git commit</code>, etc. Tout changement apporté aux fichiers de tests sous le dossier
158 158 spec/ruby doit être dans un commit différent de celui utilisé pour corriger le code source.</li>
159 159 <li>Exécutez <code>git format-patch origin</code>, ce qui extraira les commits accumulés dans la branche en cours depuis sa dernière mise à jour depuis origin, ou `git format-patch -N&rsquo;, ou N (un entier, 1, 2,&hellip;) est le nombre de commits que vous souhaitez extraire afin de génerer le patch</li>
160   - <li>Créez un gist avec votre patch et liez-le dans un ticket sur le gestionnaire de ticket du projet http://github.com/evanphx/rubinius/issues. Vous pouvez ajoutez plusieurs patchs à un seul ticket.</li>
  160 + <li>Créez un gist avec votre patch et liez-le dans un ticket sur le gestionnaire de ticket du projet http://github.com/rubinius/rubinius/issues. Vous pouvez ajoutez plusieurs patchs à un seul ticket.</li>
161 161 </ol>
162 162
163 163 <p>Quand votre patch est accepté par le project Rubinius, vous aurez un
2  web/_site/doc/fr/how-to/write-a-blog-post/index.html
@@ -147,7 +147,7 @@
147 147
148 148 <p>Clonez le dépôt Rubinius afin de récupérer le site web et les billets.</p>
149 149
150   -<pre><code>git clone https://github.com/evanphx/rubinius.git
  150 +<pre><code>git clone https://github.com/rubinius/rubinius.git
151 151 </code></pre>
152 152
153 153 <p>Pour démarrer, assurez-vous d&rsquo;avoir installé les gems <code>kramdown</code> et <code>jekyll</code>.</p>
2  web/_site/doc/fr/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
152 152 historique MRI (aussi connue sous le nom de MatzRuby)</li>
153 153 <li>Committez vos changements</li>
154 154 <li>Utilisez <code>git format-patch</code></li>
155   - <li>Créez un gist avec votre patch et faites référence à ce ticket sur notre gestionnaire de ticket <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</li>
  155 + <li>Créez un gist avec votre patch et faites référence à ce ticket sur notre gestionnaire de ticket <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</li>
156 156 </ol>
157 157
158 158
2  web/_site/doc/fr/how-to/write-a-ticket/index.html
@@ -136,7 +136,7 @@
136 136
137 137
138 138
139   - <p>Le gestionnaire de ticket Rubinius se trouve à l&rsquo;adresse <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
  139 + <p>Le gestionnaire de ticket Rubinius se trouve à l&rsquo;adresse <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
140 140
141 141 <p>Pour être utile, un ticket doit être concis, précis et permettre d&rsquo;agir.
142 142 S&rsquo;il ne l&rsquo;est pas, le ticket va engendrer des aller-tours, des
2  web/_site/doc/fr/what-is-rubinius/index.html
@@ -156,7 +156,7 @@ <h2 id="installer">Installer</h2>
156 156 lisez le chapitre <a href="/doc/fr/getting-started/">Démarrage</a>.</p>
157 157
158 158 <ol>
159   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  159 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
160 160 <li><code>cd rubinius</code></li>
161 161 <li><code>./configure --prefix=/path/to/install/dir</code></li>
162 162 <li><code>rake install</code></li>
2  web/_site/doc/ja/getting-started/building/index.html
@@ -163,7 +163,7 @@ <h3 id="getting-the-source">Getting the Source</h3>
163 163
164 164 <ol>
165 165 <li>Change your current working directory to your development directory</li>
166   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  166 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
167 167 </ol>
168 168
169 169 <h3 id="installing-rubinius">Installing Rubinius</h3>
2  web/_site/doc/ja/how-to/fix-a-failing-spec/index.html
@@ -171,7 +171,7 @@
171 171 -N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
172 172 generate patches.</li>
173 173 <li>Create a gist with your patch and link to it in a ticket on the issue
174   -tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
  174 +tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
175 175 patches to one ticket.</li>
176 176 </ol>
177 177
2  web/_site/doc/ja/how-to/write-a-ruby-spec/index.html
@@ -160,7 +160,7 @@
160 160 <li>Commit your changes</li>
161 161 <li>Use <code>git format-patch</code></li>
162 162 <li>Create a gist with your patch and link to it in a ticket on the issue
163   -tracker at <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</li>
  163 +tracker at <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</li>
164 164 </ol>
165 165
166 166
2  web/_site/doc/ja/how-to/write-a-ticket/index.html
@@ -144,7 +144,7 @@
144 144
145 145
146 146
147   - <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
  147 + <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
148 148
149 149 <p>To be useful, tickets must be concise, focused, and actionable. If not, the
150 150 ticket will languish and become clutter. Accordingly, tickets must fall into
2  web/_site/doc/ja/what-is-rubinius/index.html
@@ -165,7 +165,7 @@ <h2 id="section-1">インストール</h2>
165 165 <a href="/doc/ja/getting-started/">はじめに</a>を参照してください。</p>
166 166
167 167 <ol>
168   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  168 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
169 169 <li><code>cd rubinius</code></li>
170 170 <li><code>./configure --prefix=/path/to/install/dir</code></li>
171 171 <li><code>rake install</code></li>
2  web/_site/doc/pl/getting-started/building/index.html
@@ -161,7 +161,7 @@ <h3 id="pobieranie-kodu-rdowego">Pobieranie kodu źródłowego</h3>
161 161
162 162 <ol>
163 163 <li><code>cd docelowy_katalog</code></li>
164   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  164 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
165 165 </ol>
166 166
167 167 <h3 id="instalacja-rubiniusa">Instalacja Rubiniusa</h3>
2  web/_site/doc/pl/how-to/fix-a-failing-spec/index.html
@@ -163,7 +163,7 @@
163 163 -N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
164 164 generate patches.</li>
165 165 <li>Create a gist with your patch and link to it in a ticket on the issue
166   -tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
  166 +tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
167 167 patches to one ticket.</li>
168 168 </ol>
169 169
2  web/_site/doc/pl/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
152 152 <li>Commit your changes</li>
153 153 <li>Use <code>git format-patch</code></li>
154 154 <li>Create a gist with your patch and link to it in a ticket on the issue
155   -tracker at <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</li>
  155 +tracker at <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</li>
156 156 </ol>
157 157
158 158
2  web/_site/doc/pl/how-to/write-a-ticket/index.html
@@ -136,7 +136,7 @@
136 136
137 137
138 138
139   - <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
  139 + <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
140 140
141 141 <p>To be useful, tickets must be concise, focused, and actionable. If not, the
142 142 ticket will languish and become clutter. Accordingly, tickets must fall into
2  web/_site/doc/pl/what-is-rubinius/index.html
@@ -158,7 +158,7 @@ <h2 id="instalacja">Instalacja</h2>
158 158 więcej przeczytaj <a href="/doc/pl/getting-started/">Pierwsze kroki</a>.</p>
159 159
160 160 <ol>
161   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  161 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
162 162 <li><code>cd rubinius</code></li>
163 163 <li><code>./configure --prefix=/path/to/install/dir</code></li>
164 164 <li><code>rake install</code></li>
2  web/_site/doc/pt-br/getting-started/building/index.html
@@ -156,7 +156,7 @@ <h3 id="getting-the-source">Getting the Source</h3>
156 156
157 157 <ol>
158 158 <li>Change your current working directory to your development directory</li>
159   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  159 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
160 160 </ol>
161 161
162 162 <h3 id="installing-rubinius">Installing Rubinius</h3>
2  web/_site/doc/pt-br/how-to/fix-a-failing-spec/index.html
@@ -163,7 +163,7 @@
163 163 -N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
164 164 generate patches.</li>
165 165 <li>Create a gist with your patch and link to it in a ticket on the issue
166   -tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
  166 +tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
167 167 patches to one ticket.</li>
168 168 </ol>
169 169
2  web/_site/doc/pt-br/how-to/write-a-blog-post/index.html
@@ -145,7 +145,7 @@
145 145
146 146 <p>Clone Rubinius repository as that is where the website and posts are stored.</p>
147 147
148   -<pre><code>git clone https://github.com/evanphx/rubinius.git
  148 +<pre><code>git clone https://github.com/rubinius/rubinius.git
149 149 </code></pre>
150 150
151 151 <p>To get started, ensure you have the <code>kramdown</code> and <code>jekyll</code> gems installed.</p>
2  web/_site/doc/pt-br/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
152 152 <li>Commit your changes</li>
153 153 <li>Use <code>git format-patch</code></li>
154 154 <li>Create a gist with your patch and link to it in a ticket on the issue
155   -tracker at <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</li>
  155 +tracker at <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</li>
156 156 </ol>
157 157
158 158
2  web/_site/doc/pt-br/how-to/write-a-ticket/index.html
@@ -136,7 +136,7 @@
136 136
137 137
138 138
139   - <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
  139 + <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
140 140
141 141 <p>To be useful, tickets must be concise, focused, and actionable. If not, the
142 142 ticket will languish and become clutter. Accordingly, tickets must fall into
2  web/_site/doc/pt-br/what-is-rubinius/index.html
@@ -155,7 +155,7 @@ <h2 id="instalao">Instalação</h2>
155 155 veja <a href="/doc/pt-br/getting-started/">Começando</a>.</p>
156 156
157 157 <ol>
158   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  158 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
159 159 <li><code>cd rubinius</code></li>
160 160 <li><code>./configure --prefix=/path/to/install/dir</code></li>
161 161 <li><code>rake install</code></li>
2  web/_site/doc/ru/getting-started/building/index.html
@@ -158,7 +158,7 @@ <h3 id="section">Получение исходного кода</h3>
158 158
159 159 <ol>
160 160 <li>Перейдите в директорию для разработок;</li>
161   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  161 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
162 162 </ol>
163 163
164 164 <h3 id="rubinius">Установка Rubinius</h3>
2  web/_site/doc/ru/how-to/fix-a-failing-spec/index.html
@@ -165,7 +165,7 @@
165 165 -N&rsquo;, где N &ndash; число (1, 2, и т.п.) коммитов, из которых вы хотите сделать
166 166 патчи.</li>
167 167 <li>Создайте gist с вашим патчем и добавьте ссылку на него в тикет в трекере
168   -http://github.com/evanphx/rubinius/issues. В один тикет можно помещать
  168 +http://github.com/rubinius/rubinius/issues. В один тикет можно помещать
169 169 несколько патчей.</li>
170 170 </ol>
171 171
2  web/_site/doc/ru/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
152 152 <li>Закоммитьте изменения</li>
153 153 <li>Используйте <code>git format-patch</code></li>
154 154 <li>Создайте gist с вашим патчем и добавьте ссылку на него в тикет в трекере
155   -http://github.com/evanphx/rubinius/issues.</li>
  155 +http://github.com/rubinius/rubinius/issues.</li>
156 156 </ol>
157 157
158 158
2  web/_site/doc/ru/how-to/write-a-ticket/index.html
@@ -137,7 +137,7 @@
137 137
138 138
139 139 <p>Трекер Rubinius-а расположен по адресу
140   -<a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
  140 +<a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
141 141
142 142 <p>Тикеты должны быть краткими, предметными и осуществимыми. В противном случае
143 143 тикет будет подолгу весеть в трекере и мешаться. Поэтому тикеты должны
2  web/_site/doc/ru/what-is-rubinius/index.html
@@ -156,7 +156,7 @@ <h2 id="section-1">Установка</h2>
156 156 информацию можно найти в разделе <a href="/doc/ru/getting-started/">&laquo;Для начала&hellip;&raquo;</a>.</p>
157 157
158 158 <ol>
159   - <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
  159 + <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
160 160 <li><code>cd rubinius</code></li>
161 161 <li><code>./configure --prefix=/путь/до/директории</code></li>
162 162 <li><code>rake install</code></li>
158 web/_site/feed/atom.xml
@@ -9,6 +9,164 @@
9 9
10 10
11 11 <entry>
  12 + <title>Inside the Rubinius 2.0 Preview Release</title>
  13 + <id>http://rubini.us/2011/06/07/inside-rubinius-20-preview/</id>
  14 + <link rel="alternate" type="text/html" href="http://rubini.us/2011/06/07/inside-rubinius-20-preview/" />
  15 + <updated>2011-06-07T00:00:00+00:00</updated>
  16 + <author>
  17 + <name>Brian Ford</name>
  18 + </author>
  19 +
  20 + <content type="html">&lt;p&gt;Houston, we have a problem. Complex projects are difficult to transition
  21 +forward and Rubinius is a complex project. Rubinius is at the point of a major
  22 +transition and we need your help to move forward.&lt;/p&gt;
  23 +
  24 +&lt;p&gt;Just over a year ago, Rubinius released version 1.0. Since then, dozens of
  25 +contributors have added over 2,200 commits to the master branch and we have
  26 +released seven new versions. At the same time, we have added nearly 450
  27 +commits on a development branch to remove the global interpreter lock (GIL)
  28 +and begin adding Ruby 1.9 and Windows support.&lt;/p&gt;
  29 +
  30 +&lt;p&gt;&lt;img src=&quot;/images/rubinius-2-0-developer-preview-blog-post.png&quot; alt=&quot;Rubinius 2.0 Developer Preview&quot; /&gt;&lt;/p&gt;
  31 +
  32 +&lt;p&gt;Today we are releasing &lt;em&gt;Rubinius 2.0 Developer Preview&lt;/em&gt;. The primary focus of
  33 +this release is true Ruby multi-threaded concurrency. Additionally, it
  34 +contains the beginnings of Ruby 1.9 and Microsoft Windows support.&lt;/p&gt;
  35 +
  36 +&lt;h3 id=&quot;rubinius-20-developer-preview&quot;&gt;Rubinius 2.0 Developer Preview&lt;/h3&gt;
  37 +
  38 +&lt;p&gt;We are seeking developers interested in running their Ruby and Rails projects
  39 +on Rubinius to help us iron out issues as we work toward the final 2.0
  40 +release. Let&amp;rsquo;s look at the details of the 2.0 developer preview.&lt;/p&gt;
  41 +
  42 +&lt;p&gt;One of the central features of Rubinius 2.0 is a fundamental change in the
  43 +threading architecture. In Rubinius 2.0, Ruby threads will run with true
  44 +concurrency. This means that if multi-core or multi-CPU hardware is available,
  45 +Ruby code on different threads will actually run in parallel.&lt;/p&gt;
  46 +
  47 +&lt;p&gt;Another central feature of Rubinius 2.0 is support for both Ruby 1.8.7 and
  48 +Ruby 1.9.2 syntax. The Rubinius 2.0 support for Ruby 1.8.7 should be 100%
  49 +backward compatible with the support in the Rubinius master branch. The full
  50 +Ruby concurrency is enabled regardless of what language syntax mode is active.&lt;/p&gt;
  51 +
  52 +&lt;h3 id=&quot;repository-migration&quot;&gt;Repository Migration&lt;/h3&gt;
  53 +
  54 +&lt;p&gt;We are migrating the main Rubinius repository to the &lt;a href=&quot;https://github.com/rubinius&quot;&gt;Rubinius&lt;/a&gt; organization.&lt;/p&gt;
  55 +
  56 +&lt;p&gt;The RVM project has already been updated to work with the new repository. So
  57 +&lt;code&gt;rvm install rbx&lt;/code&gt; will use the new repository. If you have an existing clone
  58 +of Rubinius, update and run &lt;code&gt;rake github&lt;/code&gt; to point your existing repository to
  59 +the new one.&lt;/p&gt;
  60 +
  61 +&lt;p&gt;You can clone directly from the &lt;a href=&quot;https://github.com/rubinius/rubinius&quot;&gt;new repository&lt;/a&gt;.&lt;/p&gt;
  62 +
  63 +&lt;h3 id=&quot;installation&quot;&gt;Installation&lt;/h3&gt;
  64 +
  65 +&lt;p&gt;For testing Rubinius with your application, installing with RVM is probably
  66 +the easiest. To install the 2.0 developer preview, ensure that RVM is updated:&lt;/p&gt;
  67 +
  68 +&lt;pre&gt;&lt;code&gt;rvm get head
  69 +rvm reload
  70 +&lt;/code&gt;&lt;/pre&gt;
  71 +
  72 +&lt;p&gt;Then, install the Rubinius 2.0.0pre branch:&lt;/p&gt;
  73 +
  74 +&lt;pre&gt;&lt;code&gt;rvm install rbx-2.0.0pre
  75 +&lt;/code&gt;&lt;/pre&gt;
  76 +
  77 +&lt;p&gt;If you are interested in helping develop Rubinius, we suggest you clone the
  78 +repository directly and build. Rubinius runs fine from the source directory so
  79 +you don&amp;rsquo;t need to install it. For more details about building from a clone,
  80 +see &lt;a href=&quot;http://rubini.us/doc/en/getting-started/&quot;&gt;Getting Started&lt;/a&gt;.&lt;/p&gt;
  81 +
  82 +&lt;h3 id=&quot;configuration&quot;&gt;Configuration&lt;/h3&gt;
  83 +
  84 +&lt;p&gt;The goal of Rubinius 2.0 is to fully support both Ruby 1.8.7 and 1.9.2 in a
  85 +single executable. When running Rubinius, you can select which version to use.
  86 +There are configuration options to change which versions are supported and
  87 +which version is the default.&lt;/p&gt;
  88 +
  89 +&lt;p&gt;The first configure option is &lt;code&gt;--enable-version=X[,Y]&lt;/code&gt;. This option sets which
  90 +language versions will be supported. An example is:&lt;/p&gt;
  91 +
  92 +&lt;pre&gt;&lt;code&gt;./configure --enable-version=1.8,1.9
  93 +&lt;/code&gt;&lt;/pre&gt;
  94 +
  95 +&lt;p&gt;The language versions can be specified as &lt;code&gt;18&lt;/code&gt; or &lt;code&gt;1.8&lt;/code&gt;. Multiple versions are
  96 +separated by a comma and no space.&lt;/p&gt;
  97 +
  98 +&lt;p&gt;The second configure option is &lt;code&gt;--default-version=X&lt;/code&gt;. This option sets which
  99 +language version is the default when running Rubinius. An example is:&lt;/p&gt;
  100 +
  101 +&lt;pre&gt;&lt;code&gt;./configure --default-version=1.9
  102 +&lt;/code&gt;&lt;/pre&gt;
  103 +
  104 +&lt;p&gt;These options are intended to be used together. You must enable a version to
  105 +select it as the default, so the options must come in the following order:&lt;/p&gt;
  106 +
  107 +&lt;pre&gt;&lt;code&gt;./configure --enable-version=X,Y --default-version=Y
  108 +&lt;/code&gt;&lt;/pre&gt;