Skip to content
Browse files

Merge branch 'master' into 2.0

Conflicts:
	web/_posts/2011-06-07-inside-rubinius-20-preview.markdown
  • Loading branch information...
2 parents 4273e24 + 7ae451a commit 23af0f7b3e0ff08a91349c1ba9e8bf5b0f6fd00a @evanphx evanphx committed Jun 7, 2011
Showing with 848 additions and 96 deletions.
  1. +11 −0 Rakefile
  2. +145 −0 web/_posts/2011-06-07-inside-rubinius-20-preview.markdown
  3. +263 −0 web/_site/2011/06/07/inside-rubinius-20-preview/index.html
  4. +166 −0 web/_site/blog/index.html
  5. +9 −0 web/_site/blog/posts_index/index.html
  6. +1 −1 web/_site/doc/de/getting-started/building/index.html
  7. +1 −1 web/_site/doc/de/how-to/fix-a-failing-spec/index.html
  8. +1 −1 web/_site/doc/de/how-to/write-a-ruby-spec/index.html
  9. +1 −1 web/_site/doc/de/how-to/write-a-ticket/index.html
  10. +1 −1 web/_site/doc/de/what-is-rubinius/index.html
  11. +1 −1 web/_site/doc/en/garbage-collector/large-objects/index.html
  12. +1 −1 web/_site/doc/en/garbage-collector/mature-generation/index.html
  13. +1 −1 web/_site/doc/en/getting-started/building/index.html
  14. +1 −1 web/_site/doc/en/how-to/fix-a-failing-spec/index.html
  15. +1 −1 web/_site/doc/en/how-to/write-a-blog-post/index.html
  16. +1 −1 web/_site/doc/en/how-to/write-a-ruby-spec/index.html
  17. +1 −1 web/_site/doc/en/how-to/write-a-ticket/index.html
  18. +1 −1 web/_site/doc/en/what-is-rubinius/index.html
  19. +1 −1 web/_site/doc/es/getting-started/building/index.html
  20. +1 −1 web/_site/doc/es/how-to/fix-a-failing-spec/index.html
  21. +1 −1 web/_site/doc/es/how-to/write-a-ruby-spec/index.html
  22. +1 −1 web/_site/doc/es/how-to/write-a-ticket/index.html
  23. +1 −1 web/_site/doc/es/what-is-rubinius/index.html
  24. +1 −1 web/_site/doc/fr/getting-started/building/index.html
  25. +1 −1 web/_site/doc/fr/how-to/fix-a-failing-spec/index.html
  26. +1 −1 web/_site/doc/fr/how-to/write-a-blog-post/index.html
  27. +1 −1 web/_site/doc/fr/how-to/write-a-ruby-spec/index.html
  28. +1 −1 web/_site/doc/fr/how-to/write-a-ticket/index.html
  29. +1 −1 web/_site/doc/fr/what-is-rubinius/index.html
  30. +1 −1 web/_site/doc/ja/getting-started/building/index.html
  31. +1 −1 web/_site/doc/ja/how-to/fix-a-failing-spec/index.html
  32. +1 −1 web/_site/doc/ja/how-to/write-a-ruby-spec/index.html
  33. +1 −1 web/_site/doc/ja/how-to/write-a-ticket/index.html
  34. +1 −1 web/_site/doc/ja/what-is-rubinius/index.html
  35. +1 −1 web/_site/doc/pl/getting-started/building/index.html
  36. +1 −1 web/_site/doc/pl/how-to/fix-a-failing-spec/index.html
  37. +1 −1 web/_site/doc/pl/how-to/write-a-ruby-spec/index.html
  38. +1 −1 web/_site/doc/pl/how-to/write-a-ticket/index.html
  39. +1 −1 web/_site/doc/pl/what-is-rubinius/index.html
  40. +1 −1 web/_site/doc/pt-br/getting-started/building/index.html
  41. +1 −1 web/_site/doc/pt-br/how-to/fix-a-failing-spec/index.html
  42. +1 −1 web/_site/doc/pt-br/how-to/write-a-blog-post/index.html
  43. +1 −1 web/_site/doc/pt-br/how-to/write-a-ruby-spec/index.html
  44. +1 −1 web/_site/doc/pt-br/how-to/write-a-ticket/index.html
  45. +1 −1 web/_site/doc/pt-br/what-is-rubinius/index.html
  46. +1 −1 web/_site/doc/ru/getting-started/building/index.html
  47. +1 −1 web/_site/doc/ru/how-to/fix-a-failing-spec/index.html
  48. +1 −1 web/_site/doc/ru/how-to/write-a-ruby-spec/index.html
  49. +1 −1 web/_site/doc/ru/how-to/write-a-ticket/index.html
  50. +1 −1 web/_site/doc/ru/what-is-rubinius/index.html
  51. +158 −0 web/_site/feed/atom.xml
  52. BIN web/_site/images/rubinius-2-0-developer-preview-blog-post.png
  53. +1 −1 web/doc/de/contributing.markdown
  54. +1 −1 web/doc/de/getting-started/building.markdown
  55. +1 −1 web/doc/de/getting-started/troubleshooting.markdown
  56. +1 −1 web/doc/de/how-to/fix-a-failing-spec.markdown
  57. +1 −1 web/doc/de/how-to/write-a-ruby-spec.markdown
  58. +1 −1 web/doc/de/how-to/write-a-ticket.markdown
  59. +1 −1 web/doc/de/what-is-rubinius.markdown
  60. +1 −1 web/doc/en/garbage-collector/large-objects.markdown
  61. +1 −1 web/doc/en/garbage-collector/mature-generation.markdown
  62. +1 −1 web/doc/en/getting-started/building.markdown
  63. +1 −1 web/doc/en/how-to/fix-a-failing-spec.markdown
  64. +1 −1 web/doc/en/how-to/write-a-blog-post.markdown
  65. +1 −1 web/doc/en/how-to/write-a-ruby-spec.markdown
  66. +1 −1 web/doc/en/how-to/write-a-ticket.markdown
  67. +1 −1 web/doc/en/systems/concurrency.markdown
  68. +1 −1 web/doc/en/tools/memory-analysis.markdown
  69. +1 −1 web/doc/en/what-is-rubinius.markdown
  70. +1 −1 web/doc/es/getting-started/building.markdown
  71. +1 −1 web/doc/es/how-to/fix-a-failing-spec.markdown
  72. +1 −1 web/doc/es/how-to/write-a-ruby-spec.markdown
  73. +1 −1 web/doc/es/how-to/write-a-ticket.markdown
  74. +1 −1 web/doc/es/what-is-rubinius.markdown
  75. +1 −1 web/doc/fr/getting-started/building.markdown
  76. +1 −1 web/doc/fr/how-to/fix-a-failing-spec.markdown
  77. +1 −1 web/doc/fr/how-to/write-a-blog-post.markdown
  78. +1 −1 web/doc/fr/how-to/write-a-ruby-spec.markdown
  79. +1 −1 web/doc/fr/how-to/write-a-ticket.markdown
  80. +1 −1 web/doc/fr/systems/concurrency.markdown
  81. +1 −1 web/doc/fr/tools/memory-analysis.markdown
  82. +1 −1 web/doc/fr/what-is-rubinius.markdown
  83. +1 −1 web/doc/ja/getting-started/building.markdown
  84. +1 −1 web/doc/ja/how-to/fix-a-failing-spec.markdown
  85. +1 −1 web/doc/ja/how-to/write-a-ruby-spec.markdown
  86. +1 −1 web/doc/ja/how-to/write-a-ticket.markdown
  87. +1 −1 web/doc/ja/what-is-rubinius.markdown
  88. +1 −1 web/doc/pl/getting-started/building.markdown
  89. +1 −1 web/doc/pl/how-to/fix-a-failing-spec.markdown
  90. +1 −1 web/doc/pl/how-to/write-a-ruby-spec.markdown
  91. +1 −1 web/doc/pl/how-to/write-a-ticket.markdown
  92. +1 −1 web/doc/pl/what-is-rubinius.markdown
  93. +1 −1 web/doc/pt-br/getting-started/building.markdown
  94. +1 −1 web/doc/pt-br/how-to/fix-a-failing-spec.markdown
  95. +1 −1 web/doc/pt-br/how-to/write-a-blog-post.markdown
  96. +1 −1 web/doc/pt-br/how-to/write-a-ruby-spec.markdown
  97. +1 −1 web/doc/pt-br/how-to/write-a-ticket.markdown
  98. +1 −1 web/doc/pt-br/what-is-rubinius.markdown
  99. +1 −1 web/doc/ru/getting-started/building.markdown
  100. +1 −1 web/doc/ru/how-to/fix-a-failing-spec.markdown
  101. +1 −1 web/doc/ru/how-to/write-a-ruby-spec.markdown
  102. +1 −1 web/doc/ru/how-to/write-a-ticket.markdown
  103. +1 −1 web/doc/ru/what-is-rubinius.markdown
  104. BIN web/images/rubinius-2-0-developer-preview-blog-post.png
View
11 Rakefile
@@ -104,6 +104,17 @@ task :default => %w[build vm:test] do
run_specs
end
+task :github do
+ cur = `git config remote.origin.url`.strip
+ if cur == "git://github.com/evanphx/rubinius.git"
+ sh "git config remote.origin.url git://github.com/rubinius/rubinius.git"
+ puts "\nSwitch to git://github.com/rubinius/rubinius.git"
+ else
+ sh "git config remote.origin.url git@github.com:rubinius/rubinius.git"
+ puts "\nSwitch to github.com:rubinius/rubinius.git"
+ end
+end
+
# See vm.rake for more information
desc "Build everything that needs to be built at default level."
task :build => ["build:build", "gem_bootstrap"]
View
145 web/_posts/2011-06-07-inside-rubinius-20-preview.markdown
@@ -4,3 +4,148 @@ title: Inside the Rubinius 2.0 Preview Release
author: Brian Ford
---
+Houston, we have a problem. Complex projects are difficult to transition
+forward and Rubinius is a complex project. Rubinius is at the point of a major
+transition and we need your help to move forward.
+
+Just over a year ago, Rubinius released version 1.0. Since then, dozens of
+contributors have added over 2,200 commits to the master branch and we have
+released seven new versions. At the same time, we have added nearly 450
+commits on a development branch to remove the global interpreter lock (GIL)
+and begin adding Ruby 1.9 and Windows support.
+
+![Rubinius 2.0 Developer Preview](/images/rubinius-2-0-developer-preview-blog-post.png)
+
+Today we are releasing *Rubinius 2.0 Developer Preview*. The primary focus of
+this release is true Ruby multi-threaded concurrency. Additionally, it
+contains the beginnings of Ruby 1.9 and Microsoft Windows support.
+
+
+### Rubinius 2.0 Developer Preview
+
+We are seeking developers interested in running their Ruby and Rails projects
+on Rubinius to help us iron out issues as we work toward the final 2.0
+release. Let's look at the details of the 2.0 developer preview.
+
+One of the central features of Rubinius 2.0 is a fundamental change in the
+threading architecture. In Rubinius 2.0, Ruby threads will run with true
+concurrency. This means that if multi-core or multi-CPU hardware is available,
+Ruby code on different threads will actually run in parallel.
+
+Another central feature of Rubinius 2.0 is support for both Ruby 1.8.7 and
+Ruby 1.9.2 syntax. The Rubinius 2.0 support for Ruby 1.8.7 should be 100%
+backward compatible with the support in the Rubinius master branch. The full
+Ruby concurrency is enabled regardless of what language syntax mode is active.
+
+
+### Repository Migration
+
+We are migrating the main Rubinius repository to the [Rubinius](
+https://github.com/rubinius) organization.
+
+The RVM project has already been updated to work with the new repository. So
+`rvm install rbx` will use the new repository. If you have an existing clone
+of Rubinius, update and run `rake github` to point your existing repository to
+the new one.
+
+You can clone directly from the [new repository](https://github.com/rubinius/rubinius).
+
+
+### Installation
+
+For testing Rubinius with your application, installing with RVM is probably
+the easiest. To install the 2.0 developer preview, ensure that RVM is updated:
+
+ rvm get head
+ rvm reload
+
+Then, install the Rubinius 2.0.0pre branch:
+
+ rvm install rbx-2.0.0pre
+
+If you are interested in helping develop Rubinius, we suggest you clone the
+repository directly and build. Rubinius runs fine from the source directory so
+you don't need to install it. For more details about building from a clone,
+see [Getting Started](http://rubini.us/doc/en/getting-started/).
+
+
+### Configuration
+
+The goal of Rubinius 2.0 is to fully support both Ruby 1.8.7 and 1.9.2 in a
+single executable. When running Rubinius, you can select which version to use.
+There are configuration options to change which versions are supported and
+which version is the default.
+
+The first configure option is `--enable-version=X[,Y]`. This option sets which
+language versions will be supported. An example is:
+
+ ./configure --enable-version=1.8,1.9
+
+The language versions can be specified as `18` or `1.8`. Multiple versions are
+separated by a comma and no space.
+
+The second configure option is `--default-version=X`. This option sets which
+language version is the default when running Rubinius. An example is:
+
+ ./configure --default-version=1.9
+
+These options are intended to be used together. You must enable a version to
+select it as the default, so the options must come in the following order:
+
+ ./configure --enable-version=X,Y --default-version=Y
+
+Once you have enabled support for a language version, to select that mode when
+running Rubinius, use the `-X18` or `-X19` command line switches. For example:
+
+ rbx -X19 -v
+
+This command will run Rubinius with the 1.9 language mode enabled.
+
+You may also use the `RBXOPT` environment variable to select the lanugage
+mode. Assuming that 1.8 is the default mode, the following command would run
+Rubinius with the 1.9 language mode enabled:
+
+ RBXOPT=-X19 rbx -v
+
+Right now, only the 1.8 language mode is enabled in the 2.0.0pre branch.
+However, we will be enabling the 1.9 mode in the very near future. The default
+mode will continue to be 1.8 unless you configure Rubinius to run in 1.9 mode.
+
+
+### Building on Windows
+
+On Windows, Rubinius uses the [MinGW-w64](http://mingw-w64.sourceforge.net/)
+compiler to build a native application. There remains a lot of work to do for
+Windows support but the Rubinius VM is currently compiling on Windows 7.
+
+If you are a bleeding-edge Windows developer interested in diving into
+Rubinius, here's how to get started:
+
+1. Install *MRI 1.9* using [RubyInstaller](http://rubyinstaller.org/).
+1. Install [MSysGit](http://code.google.com/p/msysgit/).
+1. Install the 32bit or 64bit MinGW-w64 toolchain.
+1. Clone the Rubinius repository.
+1. In CMD, run `ruby configure`.
+1. Run `rake`.
+
+
+### Moving Forward
+
+In the near future, we will release another version of Rubinius from the
+current master branch. We hope to merge 2.0.0pre into master as soon as
+possible and continue working toward the 2.0 final release. We'll make that
+decision based on your reports about how the 2.0.0pre branch is working with
+existing 1.8.7 applications.
+
+We greatly appreciate your help polishing up the Rubinius 2.0 release! Follow
+us on [Twitter](http://twitter.com/rubinius) for updates and stop by #rubinius
+on freenode.net to chat about anything on your mind.
+
+
+### Rubinius Support on EngineYard AppCloud
+
+Rubinius 1.2.3 is currently in beta on Engine Yard AppCloud, and we encourage
+users to [give it a try](http://docs.engineyard.com/rubinius.html). Engine
+Yard will support Rubinius 2.0.0 after it’s officially released.
+
+To learn more about Rubinius, join Engine Yard for a [Platform Options Webinar](http://pages.engineyard.com/RubyPlatformOptionsWebinarJuly212011.html) in July.
View
263 web/_site/2011/06/07/inside-rubinius-20-preview/index.html
@@ -0,0 +1,263 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Inside the Rubinius 2.0 Preview Release - Rubinius</title>
+ <meta content='text/html;charset=utf-8' http-equiv='content-type'>
+ <meta content='en' http-equiv='content-language'>
+ <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'>
+ <meta content='Less Than Three. &lt;3. http://less.thanthree.com' name='author'>
+ <link href='/' rel='home'>
+ <link href='/' rel='start'>
+
+
+ <link href='/feed/atom.xml' rel='alternate' type='application/atom+xml' title='Rubinius Blog' />
+ <!--[if IE]><script src="http://html5shiv.googlecode.com/svn/trunk/html5.js" type="text/javascript"></script><![endif]-->
+ <script src="/javascripts/jquery-1.3.2.js" type="text/javascript"></script>
+ <script src="/javascripts/paging_keys.js" type="text/javascript"></script>
+
+ <script src="/javascripts/application.js" type="text/javascript"></script>
+ <style>article, aside, dialog, figure, footer, header, hgroup, menu, nav, section { display: block; }</style>
+
+ <link href="/stylesheets/blueprint/screen.css" media="screen" rel="stylesheet" type="text/css" />
+ <link href="/stylesheets/application.css" media="screen" rel="stylesheet" type="text/css" />
+ <link href="/stylesheets/blueprint/print.css" media="print" rel="stylesheet" type="text/css" />
+ <!--[if IE]><link href="/stylesheets/blueprint/ie.css" media="screen" rel="stylesheet" type="text/css" /><![endif]-->
+ <!--[if IE]><link href="/stylesheets/ie.css" media="screen" rel="stylesheet" type="text/css" /><![endif]-->
+ <link href="/stylesheets/pygments.css" media="screen" rel="stylesheet" type="text/css" />
+ </head>
+ <body>
+ <div class='container'>
+ <div class='span-21 blog_menu'>
+ <header>
+ <nav>
+ <ul>
+ <li><a href="/">Home</a></li>
+ <li><a id="blog" href="/blog/">Blog</a></li>
+ <li><a id="documentation" href="/doc/en/">Documentation</a></li>
+ <li><a href="/projects/">Projects</a></li>
+ <li><a href="/roadmap/">Roadmap</a></li>
+ <li><a href="/releases/">Releases</a></li>
+ </ul>
+ </nav>
+
+ </header>
+ </div>
+ <div class='span-3 last'>
+ <div id='version'>
+ <a href="/releases/1.2.3">1.2.3</a>
+ </div>
+ </div>
+
+ </div>
+
+ <div class="container posts_nav">
+ <nav>
+ <a href="/blog/posts_index/">Index of Posts</a>
+ <a id="feed_icon" href="/feed/atom.xml"><img alt="subscribe" src="/images/feed-icon16x16.png" /></a>
+ </nav>
+ </div>
+
+
+ <div class="container blog_posts">
+ <h2 class="post_title">Inside the Rubinius 2.0 Preview Release</h2>
+
+ <div class="by_line">
+ <p><span class="author">Brian Ford</span>
+ <span class="date">07 June 2011</span>
+
+ </p>
+ </div>
+
+ <p>Houston, we have a problem. Complex projects are difficult to transition
+forward and Rubinius is a complex project. Rubinius is at the point of a major
+transition and we need your help to move forward.</p>
+
+<p>Just over a year ago, Rubinius released version 1.0. Since then, dozens of
+contributors have added over 2,200 commits to the master branch and we have
+released seven new versions. At the same time, we have added nearly 450
+commits on a development branch to remove the global interpreter lock (GIL)
+and begin adding Ruby 1.9 and Windows support.</p>
+
+<p><img src="/images/rubinius-2-0-developer-preview-blog-post.png" alt="Rubinius 2.0 Developer Preview" /></p>
+
+<p>Today we are releasing <em>Rubinius 2.0 Developer Preview</em>. The primary focus of
+this release is true Ruby multi-threaded concurrency. Additionally, it
+contains the beginnings of Ruby 1.9 and Microsoft Windows support.</p>
+
+<h3 id="rubinius-20-developer-preview">Rubinius 2.0 Developer Preview</h3>
+
+<p>We are seeking developers interested in running their Ruby and Rails projects
+on Rubinius to help us iron out issues as we work toward the final 2.0
+release. Let&rsquo;s look at the details of the 2.0 developer preview.</p>
+
+<p>One of the central features of Rubinius 2.0 is a fundamental change in the
+threading architecture. In Rubinius 2.0, Ruby threads will run with true
+concurrency. This means that if multi-core or multi-CPU hardware is available,
+Ruby code on different threads will actually run in parallel.</p>
+
+<p>Another central feature of Rubinius 2.0 is support for both Ruby 1.8.7 and
+Ruby 1.9.2 syntax. The Rubinius 2.0 support for Ruby 1.8.7 should be 100%
+backward compatible with the support in the Rubinius master branch. The full
+Ruby concurrency is enabled regardless of what language syntax mode is active.</p>
+
+<h3 id="repository-migration">Repository Migration</h3>
+
+<p>We are migrating the main Rubinius repository to the <a href="https://github.com/rubinius">Rubinius</a> organization.</p>
+
+<p>The RVM project has already been updated to work with the new repository. So
+<code>rvm install rbx</code> will use the new repository. If you have an existing clone
+of Rubinius, update and run <code>rake github</code> to point your existing repository to
+the new one.</p>
+
+<p>You can clone directly from the <a href="https://github.com/rubinius/rubinius">new repository</a>.</p>
+
+<h3 id="installation">Installation</h3>
+
+<p>For testing Rubinius with your application, installing with RVM is probably
+the easiest. To install the 2.0 developer preview, ensure that RVM is updated:</p>
+
+<pre><code>rvm get head
+rvm reload
+</code></pre>
+
+<p>Then, install the Rubinius 2.0.0pre branch:</p>
+
+<pre><code>rvm install rbx-2.0.0pre
+</code></pre>
+
+<p>If you are interested in helping develop Rubinius, we suggest you clone the
+repository directly and build. Rubinius runs fine from the source directory so
+you don&rsquo;t need to install it. For more details about building from a clone,
+see <a href="http://rubini.us/doc/en/getting-started/">Getting Started</a>.</p>
+
+<h3 id="configuration">Configuration</h3>
+
+<p>The goal of Rubinius 2.0 is to fully support both Ruby 1.8.7 and 1.9.2 in a
+single executable. When running Rubinius, you can select which version to use.
+There are configuration options to change which versions are supported and
+which version is the default.</p>
+
+<p>The first configure option is <code>--enable-version=X[,Y]</code>. This option sets which
+language versions will be supported. An example is:</p>
+
+<pre><code>./configure --enable-version=1.8,1.9
+</code></pre>
+
+<p>The language versions can be specified as <code>18</code> or <code>1.8</code>. Multiple versions are
+separated by a comma and no space.</p>
+
+<p>The second configure option is <code>--default-version=X</code>. This option sets which
+language version is the default when running Rubinius. An example is:</p>
+
+<pre><code>./configure --default-version=1.9
+</code></pre>
+
+<p>These options are intended to be used together. You must enable a version to
+select it as the default, so the options must come in the following order:</p>
+
+<pre><code>./configure --enable-version=X,Y --default-version=Y
+</code></pre>
+
+<p>Once you have enabled support for a language version, to select that mode when
+running Rubinius, use the <code>-X18</code> or <code>-X19</code> command line switches. For example:</p>
+
+<pre><code>rbx -X19 -v
+</code></pre>
+
+<p>This command will run Rubinius with the 1.9 language mode enabled.</p>
+
+<p>You may also use the <code>RBXOPT</code> environment variable to select the lanugage
+mode. Assuming that 1.8 is the default mode, the following command would run
+Rubinius with the 1.9 language mode enabled:</p>
+
+<pre><code>RBXOPT=-X19 rbx -v
+</code></pre>
+
+<p>Right now, only the 1.8 language mode is enabled in the 2.0.0pre branch.
+However, we will be enabling the 1.9 mode in the very near future. The default
+mode will continue to be 1.8 unless you configure Rubinius to run in 1.9 mode.</p>
+
+<h3 id="building-on-windows">Building on Windows</h3>
+
+<p>On Windows, Rubinius uses the <a href="http://mingw-w64.sourceforge.net/">MinGW-w64</a>
+compiler to build a native application. There remains a lot of work to do for
+Windows support but the Rubinius VM is currently compiling on Windows 7.</p>
+
+<p>If you are a bleeding-edge Windows developer interested in diving into
+Rubinius, here&rsquo;s how to get started:</p>
+
+<ol>
+ <li>Install <em>MRI 1.9</em> using <a href="http://rubyinstaller.org/">RubyInstaller</a>.</li>
+ <li>Install <a href="http://code.google.com/p/msysgit/">MSysGit</a>.</li>
+ <li>Install the 32bit or 64bit MinGW-w64 toolchain.</li>
+ <li>Clone the Rubinius repository.</li>
+ <li>In CMD, run <code>ruby configure</code>.</li>
+ <li>Run <code>rake</code>.</li>
+</ol>
+
+<h3 id="moving-forward">Moving Forward</h3>
+
+<p>In the near future, we will release another version of Rubinius from the
+current master branch. We hope to merge 2.0.0pre into master as soon as
+possible and continue working toward the 2.0 final release. We&rsquo;ll make that
+decision based on your reports about how the 2.0.0pre branch is working with
+existing 1.8.7 applications.</p>
+
+<p>We greatly appreciate your help polishing up the Rubinius 2.0 release! Follow
+us on <a href="http://twitter.com/rubinius">Twitter</a> for updates and stop by #rubinius
+on freenode.net to chat about anything on your mind.</p>
+
+<h3 id="rubinius-support-on-engineyard-appcloud">Rubinius Support on EngineYard AppCloud</h3>
+
+<p>Rubinius 1.2.3 is currently in beta on Engine Yard AppCloud, and we encourage
+users to <a href="http://docs.engineyard.com/rubinius.html">give it a try</a>. Engine
+Yard will support Rubinius 2.0.0 after it’s officially released.</p>
+
+<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>
+
+
+ <div id="disqus_thread"></div>
+<script type="text/javascript">
+ var disqus_shortname = 'rubinius';
+ var disqus_identifier = '/2011/06/07/inside-rubinius-20-preview/';
+ var disqus_url = 'http://rubini.us/2011/06/07/inside-rubinius-20-preview/';
+
+ (function() {
+ var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
+ dsq.src = 'http://' + disqus_shortname + '.disqus.com/embed.js';
+ (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
+ })();
+</script>
+<noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
+
+ </div>
+ <footer>
+ <div class='container'>
+ <nav>
+ <ul>
+ <li><a href="http://twitter.com/rubinius">Follow Rubinius on Twitter</a></li>
+ <li><a href="http://github.com/evanphx/rubinius">Fork Rubinius on github</a></li>
+ <li><a href="http://engineyard.com">An Engine Yard project</a></li>
+
+ <li id='credit'>
+ Site design by
+ <a href="http://less.thanthree.com">Less Than Three</a>
+ </li>
+ </ul>
+ </nav>
+ </div>
+ </footer>
+ <script type="text/javascript">
+ var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
+ document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
+ </script>
+
+ <script type="text/javascript">
+ try {
+ var pageTracker = _gat._getTracker("UA-12328521-1");
+ pageTracker._trackPageview();
+ } catch(err) {}</script>
+
+ </body>
+
+</html>
View
166 web/_site/blog/index.html
@@ -62,6 +62,172 @@
<div class="post">
<h2 class="post_title">
+ <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>
+ </h2>
+ <div class="by_line">
+ <p><span class="author">Brian Ford</span>
+ <span class="date">07 June 2011</span>
+
+ <a href="http://rubini.us/2011/06/07/inside-rubinius-20-preview/#disqus_thread"
+ data-disqus-identifier="/2011/06/07/inside-rubinius-20-preview/"></a>
+
+
+ </p>
+ </div>
+
+ <p>Houston, we have a problem. Complex projects are difficult to transition
+forward and Rubinius is a complex project. Rubinius is at the point of a major
+transition and we need your help to move forward.</p>
+
+<p>Just over a year ago, Rubinius released version 1.0. Since then, dozens of
+contributors have added over 2,200 commits to the master branch and we have
+released seven new versions. At the same time, we have added nearly 450
+commits on a development branch to remove the global interpreter lock (GIL)
+and begin adding Ruby 1.9 and Windows support.</p>
+
+<p><img src="/images/rubinius-2-0-developer-preview-blog-post.png" alt="Rubinius 2.0 Developer Preview" /></p>
+
+<p>Today we are releasing <em>Rubinius 2.0 Developer Preview</em>. The primary focus of
+this release is true Ruby multi-threaded concurrency. Additionally, it
+contains the beginnings of Ruby 1.9 and Microsoft Windows support.</p>
+
+<h3 id="rubinius-20-developer-preview">Rubinius 2.0 Developer Preview</h3>
+
+<p>We are seeking developers interested in running their Ruby and Rails projects
+on Rubinius to help us iron out issues as we work toward the final 2.0
+release. Let&rsquo;s look at the details of the 2.0 developer preview.</p>
+
+<p>One of the central features of Rubinius 2.0 is a fundamental change in the
+threading architecture. In Rubinius 2.0, Ruby threads will run with true
+concurrency. This means that if multi-core or multi-CPU hardware is available,
+Ruby code on different threads will actually run in parallel.</p>
+
+<p>Another central feature of Rubinius 2.0 is support for both Ruby 1.8.7 and
+Ruby 1.9.2 syntax. The Rubinius 2.0 support for Ruby 1.8.7 should be 100%
+backward compatible with the support in the Rubinius master branch. The full
+Ruby concurrency is enabled regardless of what language syntax mode is active.</p>
+
+<h3 id="repository-migration">Repository Migration</h3>
+
+<p>We are migrating the main Rubinius repository to the <a href="https://github.com/rubinius">Rubinius</a> organization.</p>
+
+<p>The RVM project has already been updated to work with the new repository. So
+<code>rvm install rbx</code> will use the new repository. If you have an existing clone
+of Rubinius, update and run <code>rake github</code> to point your existing repository to
+the new one.</p>
+
+<p>You can clone directly from the <a href="https://github.com/rubinius/rubinius">new repository</a>.</p>
+
+<h3 id="installation">Installation</h3>
+
+<p>For testing Rubinius with your application, installing with RVM is probably
+the easiest. To install the 2.0 developer preview, ensure that RVM is updated:</p>
+
+<pre><code>rvm get head
+rvm reload
+</code></pre>
+
+<p>Then, install the Rubinius 2.0.0pre branch:</p>
+
+<pre><code>rvm install rbx-2.0.0pre
+</code></pre>
+
+<p>If you are interested in helping develop Rubinius, we suggest you clone the
+repository directly and build. Rubinius runs fine from the source directory so
+you don&rsquo;t need to install it. For more details about building from a clone,
+see <a href="http://rubini.us/doc/en/getting-started/">Getting Started</a>.</p>
+
+<h3 id="configuration">Configuration</h3>
+
+<p>The goal of Rubinius 2.0 is to fully support both Ruby 1.8.7 and 1.9.2 in a
+single executable. When running Rubinius, you can select which version to use.
+There are configuration options to change which versions are supported and
+which version is the default.</p>
+
+<p>The first configure option is <code>--enable-version=X[,Y]</code>. This option sets which
+language versions will be supported. An example is:</p>
+
+<pre><code>./configure --enable-version=1.8,1.9
+</code></pre>
+
+<p>The language versions can be specified as <code>18</code> or <code>1.8</code>. Multiple versions are
+separated by a comma and no space.</p>
+
+<p>The second configure option is <code>--default-version=X</code>. This option sets which
+language version is the default when running Rubinius. An example is:</p>
+
+<pre><code>./configure --default-version=1.9
+</code></pre>
+
+<p>These options are intended to be used together. You must enable a version to
+select it as the default, so the options must come in the following order:</p>
+
+<pre><code>./configure --enable-version=X,Y --default-version=Y
+</code></pre>
+
+<p>Once you have enabled support for a language version, to select that mode when
+running Rubinius, use the <code>-X18</code> or <code>-X19</code> command line switches. For example:</p>
+
+<pre><code>rbx -X19 -v
+</code></pre>
+
+<p>This command will run Rubinius with the 1.9 language mode enabled.</p>
+
+<p>You may also use the <code>RBXOPT</code> environment variable to select the lanugage
+mode. Assuming that 1.8 is the default mode, the following command would run
+Rubinius with the 1.9 language mode enabled:</p>
+
+<pre><code>RBXOPT=-X19 rbx -v
+</code></pre>
+
+<p>Right now, only the 1.8 language mode is enabled in the 2.0.0pre branch.
+However, we will be enabling the 1.9 mode in the very near future. The default
+mode will continue to be 1.8 unless you configure Rubinius to run in 1.9 mode.</p>
+
+<h3 id="building-on-windows">Building on Windows</h3>
+
+<p>On Windows, Rubinius uses the <a href="http://mingw-w64.sourceforge.net/">MinGW-w64</a>
+compiler to build a native application. There remains a lot of work to do for
+Windows support but the Rubinius VM is currently compiling on Windows 7.</p>
+
+<p>If you are a bleeding-edge Windows developer interested in diving into
+Rubinius, here&rsquo;s how to get started:</p>
+
+<ol>
+ <li>Install <em>MRI 1.9</em> using <a href="http://rubyinstaller.org/">RubyInstaller</a>.</li>
+ <li>Install <a href="http://code.google.com/p/msysgit/">MSysGit</a>.</li>
+ <li>Install the 32bit or 64bit MinGW-w64 toolchain.</li>
+ <li>Clone the Rubinius repository.</li>
+ <li>In CMD, run <code>ruby configure</code>.</li>
+ <li>Run <code>rake</code>.</li>
+</ol>
+
+<h3 id="moving-forward">Moving Forward</h3>
+
+<p>In the near future, we will release another version of Rubinius from the
+current master branch. We hope to merge 2.0.0pre into master as soon as
+possible and continue working toward the 2.0 final release. We&rsquo;ll make that
+decision based on your reports about how the 2.0.0pre branch is working with
+existing 1.8.7 applications.</p>
+
+<p>We greatly appreciate your help polishing up the Rubinius 2.0 release! Follow
+us on <a href="http://twitter.com/rubinius">Twitter</a> for updates and stop by #rubinius
+on freenode.net to chat about anything on your mind.</p>
+
+<h3 id="rubinius-support-on-engineyard-appcloud">Rubinius Support on EngineYard AppCloud</h3>
+
+<p>Rubinius 1.2.3 is currently in beta on Engine Yard AppCloud, and we encourage
+users to <a href="http://docs.engineyard.com/rubinius.html">give it a try</a>. Engine
+Yard will support Rubinius 2.0.0 after it’s officially released.</p>
+
+<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>
+
+ </div>
+
+ <div class="post">
+ <h2 class="post_title">
<a href="/2011/05/26/rubinius-rewards/" title="Announcing Rubinius Rewards" class="post_title">
Announcing Rubinius Rewards
</a>
View
9 web/_site/blog/posts_index/index.html
@@ -55,6 +55,15 @@
<ul>
<li>
+ <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>
+ <span class="author">Brian Ford</span>
+ <span class="date">07 June 2011</span>
+ <a href="http://rubini.us/2011/06/07/inside-rubinius-20-preview/#disqus_thread"
+ data-disqus-identifier="/2011/06/07/inside-rubinius-20-preview/"></a>
+
+ </li>
+
+ <li>
<a href="/2011/05/26/rubinius-rewards/" title="Announcing Rubinius Rewards" class="post_title"> Announcing Rubinius Rewards </a>
<span class="author">Shane Becker</span>
<span class="date">26 May 2011</span>
View
2 web/_site/doc/de/getting-started/building/index.html
@@ -164,7 +164,7 @@ <h3 id="beschaffen-des-quellcodes">Beschaffen des Quellcodes</h3>
<ol>
<li>Wechsle in dein Entwicklungsverzeichnis</li>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
</ol>
<h3 id="rubinius-installieren">Rubinius installieren</h3>
View
2 web/_site/doc/de/how-to/fix-a-failing-spec/index.html
@@ -170,7 +170,7 @@
willst.</li>
<li>Erstelle ein Gist (auf http://gist.github.com) mit deinem Patch und
verlinke es in einem neuen Ticket im Issuetracker auf Github:
-http://github.com/evanphx/rubinius/issues Es können mehrere Patches pro
+http://github.com/rubinius/rubinius/issues Es können mehrere Patches pro
Ticket hinzugefügt werden.</li>
</ol>
View
2 web/_site/doc/de/how-to/write-a-ruby-spec/index.html
@@ -155,7 +155,7 @@
<li>Führe <code>git format-patch</code> aus</li>
<li>Erstelle ein Gist (auf http://gist.github.com) mit deinem Patch und
verlinke diesen in einem Ticket auf dem Issuetracker:
-<a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a></li>
+<a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a></li>
</ol>
View
2 web/_site/doc/de/how-to/write-a-ticket/index.html
@@ -137,7 +137,7 @@
<p>Den Rubinius Issuetracker findest du hier:
-<a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
+<a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
<p>Damit ein Ticket nützlich ist, sollte es prägnant, fokussiert und umsetzbar
sein. Falls es diese Kriterien nicht erfüllt, wird es vermutlich nur den
View
2 web/_site/doc/de/what-is-rubinius/index.html
@@ -157,7 +157,7 @@ <h2 id="installation">Installation</h2>
Informationen siehe auch: <a href="/doc/de/getting-started/">Erste Schritte</a>.</p>
<ol>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
<li><code>cd rubinius</code></li>
<li><code>./configure --prefix=/pfad/zum/installations/verzeichnis</code></li>
<li><code>rake install</code></li>
View
2 web/_site/doc/en/garbage-collector/large-objects/index.html
@@ -158,7 +158,7 @@
</code></pre>
<p>For more information on configuration variables available read the
-<a href="https://github.com/evanphx/rubinius/blob/master/vm/configuration.hpp">vm configuration source file </a></p>
+<a href="https://github.com/rubinius/rubinius/blob/master/vm/configuration.hpp">vm configuration source file </a></p>
View
2 web/_site/doc/en/garbage-collector/mature-generation/index.html
@@ -153,7 +153,7 @@
via gc.lifetime. gc.lifetime is used by autotune which sets the initial value.</p>
<p>For more information on configuration variables available read the
-<a href="https://github.com/evanphx/rubinius/blob/master/vm/configuration.hpp">vm configuration source file </a></p>
+<a href="https://github.com/rubinius/rubinius/blob/master/vm/configuration.hpp">vm configuration source file </a></p>
View
2 web/_site/doc/en/getting-started/building/index.html
@@ -156,7 +156,7 @@ <h3 id="getting-the-source">Getting the Source</h3>
<ol>
<li>Change your current working directory to your development directory</li>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
</ol>
<h3 id="installing-rubinius">Installing Rubinius</h3>
View
2 web/_site/doc/en/how-to/fix-a-failing-spec/index.html
@@ -163,7 +163,7 @@
-N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
generate patches.</li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.</li>
</ol>
View
2 web/_site/doc/en/how-to/write-a-blog-post/index.html
@@ -145,7 +145,7 @@
<p>Clone Rubinius repository as that is where the website and posts are stored.</p>
-<pre><code>git clone https://github.com/evanphx/rubinius.git
+<pre><code>git clone https://github.com/rubinius/rubinius.git
</code></pre>
<p>To get started, ensure you have the <code>kramdown</code> and <code>jekyll</code> gems installed.</p>
View
2 web/_site/doc/en/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
<li>Commit your changes</li>
<li>Use <code>git format-patch</code></li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</li>
+tracker at <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</li>
</ol>
View
2 web/_site/doc/en/how-to/write-a-ticket/index.html
@@ -136,7 +136,7 @@
- <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
+ <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
<p>To be useful, tickets must be concise, focused, and actionable. If not, the
ticket will languish and become clutter. Accordingly, tickets must fall into
View
2 web/_site/doc/en/what-is-rubinius/index.html
@@ -157,7 +157,7 @@ <h2 id="installing">Installing</h2>
see <a href="/doc/en/getting-started/">Getting Started</a>.</p>
<ol>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
<li><code>cd rubinius</code></li>
<li><code>./configure --prefix=/path/to/install/dir</code></li>
<li><code>rake install</code></li>
View
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>
<ol>
<li>Utilice la linea de comandos para entrar a su directorio de
desarrollo.</li>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
</ol>
<h3 id="instalacin-de-rubinius">Instalación de Rubinius</h3>
View
2 web/_site/doc/es/how-to/fix-a-failing-spec/index.html
@@ -171,7 +171,7 @@
-N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
generate patches.</li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.</li>
</ol>
View
2 web/_site/doc/es/how-to/write-a-ruby-spec/index.html
@@ -160,7 +160,7 @@
<li>Commit your changes</li>
<li>Use <code>git format-patch</code></li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at http://github.com/evanphx/rubinius/issues.</li>
+tracker at http://github.com/rubinius/rubinius/issues.</li>
</ol>
View
2 web/_site/doc/es/how-to/write-a-ticket/index.html
@@ -144,7 +144,7 @@
- <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
+ <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
<p>Para ser útiles, los boletos deben ser concisas, específicas y acciones
concretas. Si no, el boleto languidecen y se convierten en el desorden. En
View
2 web/_site/doc/es/what-is-rubinius/index.html
@@ -157,7 +157,7 @@ <h2 id="instalacin">Instalación</h2>
más detallada, vea <a href="/doc/es/getting-started/">Primeros pasos</a>.</p>
<ol>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
<li><code>cd rubinius</code></li>
<li><code>./configure --prefix=/path/to/install/dir</code></li>
<li><code>rake install</code></li>
View
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>
<ol>
<li>Changez de répertoire courant vers votre répertoire de développement</li>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
</ol>
<h3 id="installer-rubinius">Installer Rubinius</h3>
View
2 web/_site/doc/fr/how-to/fix-a-failing-spec/index.html
@@ -157,7 +157,7 @@
<li>Exécutez <code>git status, git add, git commit</code>, etc. Tout changement apporté aux fichiers de tests sous le dossier
spec/ruby doit être dans un commit différent de celui utilisé pour corriger le code source.</li>
<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>
- <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>
+ <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>
</ol>
<p>Quand votre patch est accepté par le project Rubinius, vous aurez un
View
2 web/_site/doc/fr/how-to/write-a-blog-post/index.html
@@ -147,7 +147,7 @@
<p>Clonez le dépôt Rubinius afin de récupérer le site web et les billets.</p>
-<pre><code>git clone https://github.com/evanphx/rubinius.git
+<pre><code>git clone https://github.com/rubinius/rubinius.git
</code></pre>
<p>Pour démarrer, assurez-vous d&rsquo;avoir installé les gems <code>kramdown</code> et <code>jekyll</code>.</p>
View
2 web/_site/doc/fr/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
historique MRI (aussi connue sous le nom de MatzRuby)</li>
<li>Committez vos changements</li>
<li>Utilisez <code>git format-patch</code></li>
- <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>
+ <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>
</ol>
View
2 web/_site/doc/fr/how-to/write-a-ticket/index.html
@@ -136,7 +136,7 @@
- <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>
+ <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>
<p>Pour être utile, un ticket doit être concis, précis et permettre d&rsquo;agir.
S&rsquo;il ne l&rsquo;est pas, le ticket va engendrer des aller-tours, des
View
2 web/_site/doc/fr/what-is-rubinius/index.html
@@ -156,7 +156,7 @@ <h2 id="installer">Installer</h2>
lisez le chapitre <a href="/doc/fr/getting-started/">Démarrage</a>.</p>
<ol>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
<li><code>cd rubinius</code></li>
<li><code>./configure --prefix=/path/to/install/dir</code></li>
<li><code>rake install</code></li>
View
2 web/_site/doc/ja/getting-started/building/index.html
@@ -163,7 +163,7 @@ <h3 id="getting-the-source">Getting the Source</h3>
<ol>
<li>Change your current working directory to your development directory</li>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
</ol>
<h3 id="installing-rubinius">Installing Rubinius</h3>
View
2 web/_site/doc/ja/how-to/fix-a-failing-spec/index.html
@@ -171,7 +171,7 @@
-N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
generate patches.</li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.</li>
</ol>
View
2 web/_site/doc/ja/how-to/write-a-ruby-spec/index.html
@@ -160,7 +160,7 @@
<li>Commit your changes</li>
<li>Use <code>git format-patch</code></li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</li>
+tracker at <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</li>
</ol>
View
2 web/_site/doc/ja/how-to/write-a-ticket/index.html
@@ -144,7 +144,7 @@
- <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
+ <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
<p>To be useful, tickets must be concise, focused, and actionable. If not, the
ticket will languish and become clutter. Accordingly, tickets must fall into
View
2 web/_site/doc/ja/what-is-rubinius/index.html
@@ -165,7 +165,7 @@ <h2 id="section-1">インストール</h2>
<a href="/doc/ja/getting-started/">はじめに</a>を参照してください。</p>
<ol>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
<li><code>cd rubinius</code></li>
<li><code>./configure --prefix=/path/to/install/dir</code></li>
<li><code>rake install</code></li>
View
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>
<ol>
<li><code>cd docelowy_katalog</code></li>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
</ol>
<h3 id="instalacja-rubiniusa">Instalacja Rubiniusa</h3>
View
2 web/_site/doc/pl/how-to/fix-a-failing-spec/index.html
@@ -163,7 +163,7 @@
-N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
generate patches.</li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.</li>
</ol>
View
2 web/_site/doc/pl/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
<li>Commit your changes</li>
<li>Use <code>git format-patch</code></li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</li>
+tracker at <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</li>
</ol>
View
2 web/_site/doc/pl/how-to/write-a-ticket/index.html
@@ -136,7 +136,7 @@
- <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
+ <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
<p>To be useful, tickets must be concise, focused, and actionable. If not, the
ticket will languish and become clutter. Accordingly, tickets must fall into
View
2 web/_site/doc/pl/what-is-rubinius/index.html
@@ -158,7 +158,7 @@ <h2 id="instalacja">Instalacja</h2>
więcej przeczytaj <a href="/doc/pl/getting-started/">Pierwsze kroki</a>.</p>
<ol>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
<li><code>cd rubinius</code></li>
<li><code>./configure --prefix=/path/to/install/dir</code></li>
<li><code>rake install</code></li>
View
2 web/_site/doc/pt-br/getting-started/building/index.html
@@ -156,7 +156,7 @@ <h3 id="getting-the-source">Getting the Source</h3>
<ol>
<li>Change your current working directory to your development directory</li>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
</ol>
<h3 id="installing-rubinius">Installing Rubinius</h3>
View
2 web/_site/doc/pt-br/how-to/fix-a-failing-spec/index.html
@@ -163,7 +163,7 @@
-N&rsquo;, where N is the number (1, 2, etc.) of commits for which you want to
generate patches.</li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.</li>
</ol>
View
2 web/_site/doc/pt-br/how-to/write-a-blog-post/index.html
@@ -145,7 +145,7 @@
<p>Clone Rubinius repository as that is where the website and posts are stored.</p>
-<pre><code>git clone https://github.com/evanphx/rubinius.git
+<pre><code>git clone https://github.com/rubinius/rubinius.git
</code></pre>
<p>To get started, ensure you have the <code>kramdown</code> and <code>jekyll</code> gems installed.</p>
View
2 web/_site/doc/pt-br/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
<li>Commit your changes</li>
<li>Use <code>git format-patch</code></li>
<li>Create a gist with your patch and link to it in a ticket on the issue
-tracker at <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</li>
+tracker at <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</li>
</ol>
View
2 web/_site/doc/pt-br/how-to/write-a-ticket/index.html
@@ -136,7 +136,7 @@
- <p>The Rubinius issue tracker is <a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
+ <p>The Rubinius issue tracker is <a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
<p>To be useful, tickets must be concise, focused, and actionable. If not, the
ticket will languish and become clutter. Accordingly, tickets must fall into
View
2 web/_site/doc/pt-br/what-is-rubinius/index.html
@@ -155,7 +155,7 @@ <h2 id="instalao">Instalação</h2>
veja <a href="/doc/pt-br/getting-started/">Começando</a>.</p>
<ol>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
<li><code>cd rubinius</code></li>
<li><code>./configure --prefix=/path/to/install/dir</code></li>
<li><code>rake install</code></li>
View
2 web/_site/doc/ru/getting-started/building/index.html
@@ -158,7 +158,7 @@ <h3 id="section">Получение исходного кода</h3>
<ol>
<li>Перейдите в директорию для разработок;</li>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
</ol>
<h3 id="rubinius">Установка Rubinius</h3>
View
2 web/_site/doc/ru/how-to/fix-a-failing-spec/index.html
@@ -165,7 +165,7 @@
-N&rsquo;, где N &ndash; число (1, 2, и т.п.) коммитов, из которых вы хотите сделать
патчи.</li>
<li>Создайте gist с вашим патчем и добавьте ссылку на него в тикет в трекере
-http://github.com/evanphx/rubinius/issues. В один тикет можно помещать
+http://github.com/rubinius/rubinius/issues. В один тикет можно помещать
несколько патчей.</li>
</ol>
View
2 web/_site/doc/ru/how-to/write-a-ruby-spec/index.html
@@ -152,7 +152,7 @@
<li>Закоммитьте изменения</li>
<li>Используйте <code>git format-patch</code></li>
<li>Создайте gist с вашим патчем и добавьте ссылку на него в тикет в трекере
-http://github.com/evanphx/rubinius/issues.</li>
+http://github.com/rubinius/rubinius/issues.</li>
</ol>
View
2 web/_site/doc/ru/how-to/write-a-ticket/index.html
@@ -137,7 +137,7 @@
<p>Трекер Rubinius-а расположен по адресу
-<a href="http://github.com/evanphx/rubinius/issues">http://github.com/evanphx/rubinius/issues</a>.</p>
+<a href="http://github.com/rubinius/rubinius/issues">http://github.com/rubinius/rubinius/issues</a>.</p>
<p>Тикеты должны быть краткими, предметными и осуществимыми. В противном случае
тикет будет подолгу весеть в трекере и мешаться. Поэтому тикеты должны
View
2 web/_site/doc/ru/what-is-rubinius/index.html
@@ -156,7 +156,7 @@ <h2 id="section-1">Установка</h2>
информацию можно найти в разделе <a href="/doc/ru/getting-started/">&laquo;Для начала&hellip;&raquo;</a>.</p>
<ol>
- <li><code>git clone git://github.com/evanphx/rubinius.git</code></li>
+ <li><code>git clone git://github.com/rubinius/rubinius.git</code></li>
<li><code>cd rubinius</code></li>
<li><code>./configure --prefix=/путь/до/директории</code></li>
<li><code>rake install</code></li>
View
158 web/_site/feed/atom.xml
@@ -9,6 +9,164 @@
<entry>
+ <title>Inside the Rubinius 2.0 Preview Release</title>
+ <id>http://rubini.us/2011/06/07/inside-rubinius-20-preview/</id>
+ <link rel="alternate" type="text/html" href="http://rubini.us/2011/06/07/inside-rubinius-20-preview/" />
+ <updated>2011-06-07T00:00:00+00:00</updated>
+ <author>
+ <name>Brian Ford</name>
+ </author>
+
+ <content type="html">&lt;p&gt;Houston, we have a problem. Complex projects are difficult to transition
+forward and Rubinius is a complex project. Rubinius is at the point of a major
+transition and we need your help to move forward.&lt;/p&gt;
+
+&lt;p&gt;Just over a year ago, Rubinius released version 1.0. Since then, dozens of
+contributors have added over 2,200 commits to the master branch and we have
+released seven new versions. At the same time, we have added nearly 450
+commits on a development branch to remove the global interpreter lock (GIL)
+and begin adding Ruby 1.9 and Windows support.&lt;/p&gt;
+
+&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;
+
+&lt;p&gt;Today we are releasing &lt;em&gt;Rubinius 2.0 Developer Preview&lt;/em&gt;. The primary focus of
+this release is true Ruby multi-threaded concurrency. Additionally, it
+contains the beginnings of Ruby 1.9 and Microsoft Windows support.&lt;/p&gt;
+
+&lt;h3 id=&quot;rubinius-20-developer-preview&quot;&gt;Rubinius 2.0 Developer Preview&lt;/h3&gt;
+
+&lt;p&gt;We are seeking developers interested in running their Ruby and Rails projects
+on Rubinius to help us iron out issues as we work toward the final 2.0
+release. Let&amp;rsquo;s look at the details of the 2.0 developer preview.&lt;/p&gt;
+
+&lt;p&gt;One of the central features of Rubinius 2.0 is a fundamental change in the
+threading architecture. In Rubinius 2.0, Ruby threads will run with true
+concurrency. This means that if multi-core or multi-CPU hardware is available,
+Ruby code on different threads will actually run in parallel.&lt;/p&gt;
+
+&lt;p&gt;Another central feature of Rubinius 2.0 is support for both Ruby 1.8.7 and
+Ruby 1.9.2 syntax. The Rubinius 2.0 support for Ruby 1.8.7 should be 100%
+backward compatible with the support in the Rubinius master branch. The full
+Ruby concurrency is enabled regardless of what language syntax mode is active.&lt;/p&gt;
+
+&lt;h3 id=&quot;repository-migration&quot;&gt;Repository Migration&lt;/h3&gt;
+
+&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;
+
+&lt;p&gt;The RVM project has already been updated to work with the new repository. So
+&lt;code&gt;rvm install rbx&lt;/code&gt; will use the new repository. If you have an existing clone
+of Rubinius, update and run &lt;code&gt;rake github&lt;/code&gt; to point your existing repository to
+the new one.&lt;/p&gt;
+
+&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;
+
+&lt;h3 id=&quot;installation&quot;&gt;Installation&lt;/h3&gt;
+
+&lt;p&gt;For testing Rubinius with your application, installing with RVM is probably
+the easiest. To install the 2.0 developer preview, ensure that RVM is updated:&lt;/p&gt;
+
+&lt;pre&gt;&lt;code&gt;rvm get head
+rvm reload
+&lt;/code&gt;&lt;/pre&gt;
+
+&lt;p&gt;Then, install the Rubinius 2.0.0pre branch:&lt;/p&gt;
+
+&lt;pre&gt;&lt;code&gt;rvm install rbx-2.0.0pre
+&lt;/code&gt;&lt;/pre&gt;
+
+&lt;p&gt;If you are interested in helping develop Rubinius, we suggest you clone the
+repository directly and build. Rubinius runs fine from the source directory so
+you don&amp;rsquo;t need to install it. For more details about building from a clone,
+see &lt;a href=&quot;http://rubini.us/doc/en/getting-started/&quot;&gt;Getting Started&lt;/a&gt;.&lt;/p&gt;
+
+&lt;h3 id=&quot;configuration&quot;&gt;Configuration&lt;/h3&gt;
+
+&lt;p&gt;The goal of Rubinius 2.0 is to fully support both Ruby 1.8.7 and 1.9.2 in a
+single executable. When running Rubinius, you can select which version to use.
+There are configuration options to change which versions are supported and
+which version is the default.&lt;/p&gt;
+
+&lt;p&gt;The first configure option is &lt;code&gt;--enable-version=X[,Y]&lt;/code&gt;. This option sets which
+language versions will be supported. An example is:&lt;/p&gt;
+
+&lt;pre&gt;&lt;code&gt;./configure --enable-version=1.8,1.9
+&lt;/code&gt;&lt;/pre&gt;
+
+&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
+separated by a comma and no space.&lt;/p&gt;
+
+&lt;p&gt;The second configure option is &lt;code&gt;--default-version=X&lt;/code&gt;. This option sets which
+language version is the default when running Rubinius. An example is:&lt;/p&gt;
+
+&lt;pre&gt;&lt;code&gt;./configure --default-version=1.9
+&lt;/code&gt;&lt;/pre&gt;
+
+&lt;p&gt;These options are intended to be used together. You must enable a version to
+select it as the default, so the options must come in the following order:&lt;/p&gt;
+
+&lt;pre&gt;&lt;code&gt;./configure --enable-version=X,Y --default-version=Y
+&lt;/code&gt;&lt;/pre&gt;
+
+&lt;p&gt;Once you have enabled support for a language version, to select that mode when
+running Rubinius, use the &lt;code&gt;-X18&lt;/code&gt; or &lt;code&gt;-X19&lt;/code&gt; command line switches. For example:&lt;/p&gt;
+
+&lt;pre&gt;&lt;code&gt;rbx -X19 -v
+&lt;/code&gt;&lt;/pre&gt;
+
+&lt;p&gt;This command will run Rubinius with the 1.9 language mode enabled.&lt;/p&gt;
+
+&lt;p&gt;You may also use the &lt;code&gt;RBXOPT&lt;/code&gt; environment variable to select the lanugage
+mode. Assuming that 1.8 is the default mode, the following command would run
+Rubinius with the 1.9 language mode enabled:&lt;/p&gt;
+
+&lt;pre&gt;&lt;code&gt;RBXOPT=-X19 rbx -v
+&lt;/code&gt;&lt;/pre&gt;
+
+&lt;p&gt;Right now, only the 1.8 language mode is enabled in the 2.0.0pre branch.
+However, we will be enabling the 1.9 mode in the very near future. The default
+mode will continue to be 1.8 unless you configure Rubinius to run in 1.9 mode.&lt;/p&gt;
+
+&lt;h3 id=&quot;building-on-windows&quot;&gt;Building on Windows&lt;/h3&gt;
+
+&lt;p&gt;On Windows, Rubinius uses the &lt;a href=&quot;http://mingw-w64.sourceforge.net/&quot;&gt;MinGW-w64&lt;/a&gt;
+compiler to build a native application. There remains a lot of work to do for
+Windows support but the Rubinius VM is currently compiling on Windows 7.&lt;/p&gt;
+
+&lt;p&gt;If you are a bleeding-edge Windows developer interested in diving into
+Rubinius, here&amp;rsquo;s how to get started:&lt;/p&gt;
+
+&lt;ol&gt;
+ &lt;li&gt;Install &lt;em&gt;MRI 1.9&lt;/em&gt; using &lt;a href=&quot;http://rubyinstaller.org/&quot;&gt;RubyInstaller&lt;/a&gt;.&lt;/li&gt;
+ &lt;li&gt;Install &lt;a href=&quot;http://code.google.com/p/msysgit/&quot;&gt;MSysGit&lt;/a&gt;.&lt;/li&gt;
+ &lt;li&gt;Install the 32bit or 64bit MinGW-w64 toolchain.&lt;/li&gt;
+ &lt;li&gt;Clone the Rubinius repository.&lt;/li&gt;
+ &lt;li&gt;In CMD, run &lt;code&gt;ruby configure&lt;/code&gt;.&lt;/li&gt;
+ &lt;li&gt;Run &lt;code&gt;rake&lt;/code&gt;.&lt;/li&gt;
+&lt;/ol&gt;
+
+&lt;h3 id=&quot;moving-forward&quot;&gt;Moving Forward&lt;/h3&gt;
+
+&lt;p&gt;In the near future, we will release another version of Rubinius from the
+current master branch. We hope to merge 2.0.0pre into master as soon as
+possible and continue working toward the 2.0 final release. We&amp;rsquo;ll make that
+decision based on your reports about how the 2.0.0pre branch is working with
+existing 1.8.7 applications.&lt;/p&gt;
+
+&lt;p&gt;We greatly appreciate your help polishing up the Rubinius 2.0 release! Follow
+us on &lt;a href=&quot;http://twitter.com/rubinius&quot;&gt;Twitter&lt;/a&gt; for updates and stop by #rubinius
+on freenode.net to chat about anything on your mind.&lt;/p&gt;
+
+&lt;h3 id=&quot;rubinius-support-on-engineyard-appcloud&quot;&gt;Rubinius Support on EngineYard AppCloud&lt;/h3&gt;
+
+&lt;p&gt;Rubinius 1.2.3 is currently in beta on Engine Yard AppCloud, and we encourage
+users to &lt;a href=&quot;http://docs.engineyard.com/rubinius.html&quot;&gt;give it a try&lt;/a&gt;. Engine
+Yard will support Rubinius 2.0.0 after it’s officially released.&lt;/p&gt;
+
+&lt;p&gt;To learn more about Rubinius, join Engine Yard for a &lt;a href=&quot;http://pages.engineyard.com/RubyPlatformOptionsWebinarJuly212011.html&quot;&gt;Platform Options Webinar&lt;/a&gt; in July.&lt;/p&gt;
+</content>
+ </entry>
+
+ <entry>
<title>Announcing Rubinius Rewards</title>
<id>http://rubini.us/2011/05/26/rubinius-rewards/</id>
<link rel="alternate" type="text/html" href="http://rubini.us/2011/05/26/rubinius-rewards/" />
View
BIN web/_site/images/rubinius-2-0-developer-preview-blog-post.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
2 web/doc/de/contributing.markdown
@@ -73,4 +73,4 @@ andere ebenso davon profitieren und verstehen, wie Rubinius implementiert ist.
* Alte Tickets prüfen oder schließen
* Minitests schreiben, die die Fehler reproduzieren. Anschließend prüfen,
ob es schon Specs für diese Fälle gibt. Wenn nicht, evtl. welche schreiben.
-
+
View
2 web/doc/de/getting-started/building.markdown
@@ -34,7 +34,7 @@ werden](http://rubini.us/download/latest).
Um Git zu nutzen:
1. Wechsle in dein Entwicklungsverzeichnis
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Rubinius installieren
View
2 web/doc/de/getting-started/troubleshooting.markdown
@@ -50,4 +50,4 @@ Lösung:
Generell sollte das Quell- oder Kompilierverzeichnis nicht nach dem Kompilieren
umbenannt werden.
-
+
View
2 web/doc/de/how-to/fix-a-failing-spec.markdown
@@ -38,7 +38,7 @@ beheben:
willst.
11. Erstelle ein Gist (auf http://gist.github.com) mit deinem Patch und
verlinke es in einem neuen Ticket im Issuetracker auf Github:
- http://github.com/evanphx/rubinius/issues Es können mehrere Patches pro
+ http://github.com/rubinius/rubinius/issues Es können mehrere Patches pro
Ticket hinzugefügt werden.
Wenn dein Patch vom Rubinius Projekt akzeptiert wird, erhältst du ein sog.
View
2 web/doc/de/how-to/write-a-ruby-spec.markdown
@@ -23,4 +23,4 @@ schreiben:
7. Führe `git format-patch` aus
8. Erstelle ein Gist (auf http://gist.github.com) mit deinem Patch und
verlinke diesen in einem Ticket auf dem Issuetracker:
- <http://github.com/evanphx/rubinius/issues>
+ <http://github.com/rubinius/rubinius/issues>
View
2 web/doc/de/how-to/write-a-ticket.markdown
@@ -8,7 +8,7 @@ next_url: how-to/write-a-ruby-spec
---
Den Rubinius Issuetracker findest du hier:
-<http://github.com/evanphx/rubinius/issues>.
+<http://github.com/rubinius/rubinius/issues>.
Damit ein Ticket nützlich ist, sollte es prägnant, fokussiert und umsetzbar
sein. Falls es diese Kriterien nicht erfüllt, wird es vermutlich nur den
View
2 web/doc/de/what-is-rubinius.markdown
@@ -29,7 +29,7 @@ Windows Unterstützung kommt ebenfalls bald und ist derzeit in Entwicklung.
Um Rubinius zu installieren, folge den unteren Anweisungen. Für detailliertere
Informationen siehe auch: [Erste Schritte](/doc/de/getting-started/).
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/pfad/zum/installations/verzeichnis`
1. `rake install`
View
2 web/doc/en/garbage-collector/large-objects.markdown
@@ -19,5 +19,5 @@ object* which by default is 2700 (such a good baud rate eh?) bytes.
rbx ... -Xgc.large_object=<number of bytes> ...
For more information on configuration variables available read the
-[vm configuration source file ](https://github.com/evanphx/rubinius/blob/master/vm/configuration.hpp)
+[vm configuration source file ](https://github.com/rubinius/rubinius/blob/master/vm/configuration.hpp)
View
2 web/doc/en/garbage-collector/mature-generation.markdown
@@ -15,5 +15,5 @@ mature collection occurrs. This can be turned off or a static number may be used
via gc.lifetime. gc.lifetime is used by autotune which sets the initial value.
For more information on configuration variables available read the
-[vm configuration source file ](https://github.com/evanphx/rubinius/blob/master/vm/configuration.hpp)
+[vm configuration source file ](https://github.com/rubinius/rubinius/blob/master/vm/configuration.hpp)
View
2 web/doc/en/getting-started/building.markdown
@@ -26,7 +26,7 @@ You can [download the tarball here](http://rubini.us/download/latest).
To use Git:
1. Change your current working directory to your development directory
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Installing Rubinius
View
2 web/doc/en/how-to/fix-a-failing-spec.markdown
@@ -31,7 +31,7 @@ Then, follow these steps to fix a failing spec:
-N', where N is the number (1, 2, etc.) of commits for which you want to
generate patches.
11. Create a gist with your patch and link to it in a ticket on the issue
- tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+ tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.
When your patch is accepted by the Rubinius project, you'll get a commit bit
View
2 web/doc/en/how-to/write-a-blog-post.markdown
@@ -16,7 +16,7 @@ formatting needs, the post can be written in HTML directly.
Clone Rubinius repository as that is where the website and posts are stored.
- git clone https://github.com/evanphx/rubinius.git
+ git clone https://github.com/rubinius/rubinius.git
To get started, ensure you have the `kramdown` and `jekyll` gems installed.
View
2 web/doc/en/how-to/write-a-ruby-spec.markdown
@@ -20,4 +20,4 @@ Then, follow these steps to write a spec for a Ruby method:
4. Commit your changes
7. Use `git format-patch`
8. Create a gist with your patch and link to it in a ticket on the issue
- tracker at <http://github.com/evanphx/rubinius/issues>.
+ tracker at <http://github.com/rubinius/rubinius/issues>.
View
2 web/doc/en/how-to/write-a-ticket.markdown
@@ -7,7 +7,7 @@ next: Write a Ruby Spec
next_url: how-to/write-a-ruby-spec
---
-The Rubinius issue tracker is <http://github.com/evanphx/rubinius/issues>.
+The Rubinius issue tracker is <http://github.com/rubinius/rubinius/issues>.
To be useful, tickets must be concise, focused, and actionable. If not, the
ticket will languish and become clutter. Accordingly, tickets must fall into
View
2 web/doc/en/systems/concurrency.markdown
@@ -91,4 +91,4 @@ Actors can also have a parent/child relationship using `Actor.spawn_link`; if th
end
sleep 1
-This example is a snippet from [girl_friday](http://github.com/mperham/girl_friday). You can review that codebase for more detail if you have questions.
+This example is a snippet from [girl_friday](http://github.com/mperham/girl_friday). You can review that codebase for more detail if you have questions.
View
2 web/doc/en/tools/memory-analysis.markdown
@@ -239,4 +239,4 @@ problem.
As it turns out, the `ZMQ::Message` class allocates some memory via `malloc` that is not
tracked by the Rubinius GC. It needs to be manually deallocated.
-Changing the code to call `ZMQ::Message#close` resolves the last leak.
+Changing the code to call `ZMQ::Message#close` resolves the last leak.
View
2 web/doc/en/what-is-rubinius.markdown
@@ -29,7 +29,7 @@ Microsoft Windows is coming soon.
To install Rubinius, use the following steps. For more detailed information,
see [Getting Started](/doc/en/getting-started/).
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/path/to/install/dir`
1. `rake install`
View
2 web/doc/es/getting-started/building.markdown
@@ -28,7 +28,7 @@ Para usar Git:
1. Utilice la linea de comandos para entrar a su directorio de
desarrollo.
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Instalación de Rubinius
View
2 web/doc/es/how-to/fix-a-failing-spec.markdown
@@ -32,7 +32,7 @@ Then, follow these steps to fix a failing spec:
-N', where N is the number (1, 2, etc.) of commits for which you want to
generate patches.
11. Create a gist with your patch and link to it in a ticket on the issue
- tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+ tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.
When your patch is accepted by the Rubinius project, you'll get a commit bit
View
2 web/doc/es/how-to/write-a-ruby-spec.markdown
@@ -21,4 +21,4 @@ Then, follow these steps to write a spec for a Ruby method:
4. Commit your changes
7. Use `git format-patch`
8. Create a gist with your patch and link to it in a ticket on the issue
- tracker at http://github.com/evanphx/rubinius/issues.
+ tracker at http://github.com/rubinius/rubinius/issues.
View
2 web/doc/es/how-to/write-a-ticket.markdown
@@ -8,7 +8,7 @@ next_url: how-to/write-a-ruby-spec
translated: true
---
-The Rubinius issue tracker is <http://github.com/evanphx/rubinius/issues>.
+The Rubinius issue tracker is <http://github.com/rubinius/rubinius/issues>.
Para ser útiles, los boletos deben ser concisas, específicas y acciones
concretas. Si no, el boleto languidecen y se convierten en el desorden. En
View
2 web/doc/es/what-is-rubinius.markdown
@@ -29,7 +29,7 @@ pronto estará disponible tambien en plataformas Microsoft Windows.
Para instalar Rubinius, realize los siguientes pasos. Para obtener información
más detallada, vea [Primeros pasos](/doc/es/getting-started/).
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/path/to/install/dir`
1. `rake install`
View
2 web/doc/fr/getting-started/building.markdown
@@ -29,7 +29,7 @@ Vous pouvez [télécharger l'archive ici](http://rubini.us/download/latest).
Pour utiliser Git :
1. Changez de répertoire courant vers votre répertoire de développement
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Installer Rubinius
View
2 web/doc/fr/how-to/fix-a-failing-spec.markdown
@@ -25,7 +25,7 @@ Ensuite, suivez ces étapes pour corriger un test en échec:
9. Exécutez `git status, git add, git commit`, etc. Tout changement apporté aux fichiers de tests sous le dossier
spec/ruby doit être dans un commit différent de celui utilisé pour corriger le code source.
10. Exécutez `git format-patch origin`, 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', ou N (un entier, 1, 2,...) est le nombre de commits que vous souhaitez extraire afin de génerer le patch
- 11. 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.
+ 11. 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.
Quand votre patch est accepté par le project Rubinius, vous aurez un
droit d'accès au dépôt Rubinius. Communiquez votre nom d'utilisateur
View
2 web/doc/fr/how-to/write-a-blog-post.markdown
@@ -18,7 +18,7 @@ HTML directement.
Clonez le dépôt Rubinius afin de récupérer le site web et les billets.
- git clone https://github.com/evanphx/rubinius.git
+ git clone https://github.com/rubinius/rubinius.git
Pour démarrer, assurez-vous d'avoir installé les gems `kramdown` et `jekyll`.
View
2 web/doc/fr/how-to/write-a-ruby-spec.markdown
@@ -20,4 +20,4 @@ Ensuite, suivez ces étapes pour écrire le test d'une méthode Ruby:
historique MRI (aussi connue sous le nom de MatzRuby)
4. Committez vos changements
7. Utilisez `git format-patch`
- 8. Créez un gist avec votre patch et faites référence à ce ticket sur notre gestionnaire de ticket <http://github.com/evanphx/rubinius/issues>.
+ 8. Créez un gist avec votre patch et faites référence à ce ticket sur notre gestionnaire de ticket <http://github.com/rubinius/rubinius/issues>.
View
2 web/doc/fr/how-to/write-a-ticket.markdown
@@ -7,7 +7,7 @@ next: Ecrire un Test Ruby</