How to distribute Ruby to the world
0 likes952 views
The document discusses how the Ruby programming language is developed and released. It describes the Ruby core team and committers, release cycles, backporting fixes, testing on various platforms via Ruby CI, packaging and distributing releases, handling security issues, and the *.ruby-lang.org domains. It also discusses moving the source code repository from Subversion to Git and migrating development tools and processes.
![self.introduce
=> {
name: “SHIBATA Hiroshi”,
nickname: “hsbt”,
organizations: [“pepabo”, “ruby”, “rubygems”,
“asakusarb”],
commit_bits: [“ruby”, “rake”, “rubygems”, “bundler”,
“rdoc”, “psych”, “ruby-build”, “railsgirls”, “railsgirls-
jp”, …],
sites: [“hsbt.org”, “ruby-lang.org”, “rubyci.org”,
“railsgirls.com”, “railsgirls.jp”],
}](https://image.slidesharecdn.com/20180316-rubyconfph2018-4x3-180316094733/85/How-to-distribute-Ruby-to-the-world-3-320.jpg)
How to distribute Ruby to the world
- 1. The secret of Release story SHIBATA Hiroshi / GMO Pepabo, inc. 2018.03.16 RubyConf.ph 2018 How to distribute Ruby to the world
- 3. self.introduce => { name: “SHIBATA Hiroshi”, nickname: “hsbt”, organizations: [“pepabo”, “ruby”, “rubygems”, “asakusarb”], commit_bits: [“ruby”, “rake”, “rubygems”, “bundler”, “rdoc”, “psych”, “ruby-build”, “railsgirls”, “railsgirls- jp”, …], sites: [“hsbt.org”, “ruby-lang.org”, “rubyci.org”, “railsgirls.com”, “railsgirls.jp”], }
- 7. Ruby Committer Heroku • matz • n0kada $ cat ~svn/.ssh/authorized_keys | awk '{print $5}' | sort | uniq | wc -l 97 Total 95 people + 2 bot Money Forward • shyouhei Full-time commiters Cookpad • ko1 • mametter Speee • mrkn
- 8. Branch maintainers trunk known as 2.6 and 2.5 @nurse: Release manager 2.4 @nagachika: Stable branch maintainer 2.3, 2.2 @unak: Old stable branch maintainer
- 9. Linux • normalperson • akr • n0kada and others Windows • unak • n0kada Platform maintainers BSD • nurse Solaris • ngoto macOS • n0kada • mrkn
- 10. Ruby 2.6
- 11. 2/24: 2.6.0preview1 release It contained MJIT feature see https://bugs.ruby-lang.org/issues/14235 5/?: 2.6.0preview2 release RubyGems 3.0 Improve MJIT Performance 12/25: 2.6.0 final release Ruby 2.6 timeframe
- 13. How release the Ruby language 2.
- 14. Version number and release cycle We plan to release every Christmas day. • 2.1.0: 2013/12/25 • 2.2.0: 2014/12/25 • 2.3.0: 2015/12/25 • 2.4.0: 2016/12/25 • 2.5.0: 2017/12/25 • 2.6.0: 2018/12/25(TBD) • … • 3.0.0: 2020/xx/xx
- 15. Backport
- 16. Ruby core backport model trunk ruby_2_4 ruby_2_3 trunk ruby_2_4 ruby_2_3 We backport fixes to stable branch from trunk. We do not merge fixes to trunk from stable branch
- 17. How do request to back port We use to management backport’s patch on redmine with specific rule. • Write a revision number to Title or library version • Set a status to “close” • Fill backport field to “2.5:REQUIRED”
- 18. Ruby CI
- 19. What’s Ruby CI Ruby CI is a CI results collector for alternative platforms • https://rubyci.org • https://github.com/ruby/rubyci • https://github.com/ruby/chkbuild Ruby CI goal is entirely supports all of Ruby platform.
- 21. Ruby CI resources Ruby CI goal is entirely supports all of Ruby platform. Ruby CI built by a lot of cloud platforms. • AWS • Azure • GCP • DigitalOcean • on-premise servers(macOS) • opencsw(Solaris)
- 23. Release time We build a tar packages from svn repository used `tools/make-snapshot`. After that, We will put them to ftp server. We have announce following resources. • https://www.ruby-lang.org (and RSS) • Mailing-list: ruby-list (https://lists.ruby-lang.org) • Twitter: @rubylangorg
- 25. Security release We received buffer overflow/underflow, memory leak, escape string, directory traversal etc… every week. We hard to fix and release these security issue. so all of release maintainer are volunteer work. We have “security@ruby-lang.org” for security report.
- 26. HackerOne We’ve been use https://hackerone.com/ ruby It has bounty program provided by IBB. We accepts to security report via hackerone too.
- 27. Why security is hard • We must to work with closed discussion for fixing Open-Source vulnerability. • We get a CVE identity from MITRE by ourselves. • We should release all versions of Ruby at the same timing. This is most hard thing.
- 29. What does mean “official”? “official” means “Matz controllable” Un-controllable examples: • ruby-doc.org • rubygems.org • bundler.io • Ruby version manager(rvm/rbenv/chruby)
- 30. *.ruby-lang.org www.ruby-lang.org Official Website of Ruby language. see http://github.com/ruby/www.ruby-lang.org svn.ruby-lang.org Main repository of Ruby source. (Not git !!!) bugs.ruby-lang.org Official issue tracker build by redmine.
- 31. *.ruby-lang.org ftp.ruby-lang.org Site of distribute official package lists.ruby-lang.org Site of Mailing-list docs.ruby-lang.org Hosted document generated from RDoc on Ruby source code and rubima project. Rubima project is a Japanese Documentation about ruby languages.
- 32. CDN Our site and package distribution were supported by fastly. • www.ruby-lang.org • cache.ruby-lang.org • docs.ruby-lang.org Statistics of our CDN: • Access ratio: USA: 44.6%, EU: 18.0%, Asia: 31.0%, Australia: 2.1%, Latin America: 3.7%, South Africa: 0.04% • Bandwidth: 7,203 GB/month
- 33. Sponsors of the Ruby language • heroku: Unlimited dyno resources for websites • fastly: OSS plan of CDN for *.ruby-lang.org • NaCl: Network and Compute resources for website • Microsoft: Provides Azure environment via MSDN Enterprise
- 34. Sponsors of the Ruby language(2) • Ruby Association: Grant of development • Nihon Ruby no Kai: macOS Server * 2 Grant of development(Windows) • Sugaya research laboratory: Network resources for macOS Server
- 36. Source distributeion Binary distribution • Windows: RubyInstaller2 • Linux: apt/yum/dnf brightbox/software collection/snapcraft • macOS: System tools Source distribution • Package: cache.ruby-lang.org • Source code: svn.ruby-lang.org or github
- 37. What’s difference source package and others Package(*.tar.gz) • Pre-build transcode • Generate configure script • Do not need gnu tools without complier like autoconf, bison Source • Need to gnu tools • Need to ruby :)
- 38. Start to build Ruby language from source $ git clone https://github.com/ruby/ruby $ cd ruby $ autoconf $ ./configure —disable-install-doc $ make -j $ make install You can invoke language tests with the following instructions:
- 39. Ruby package manager RVM • To support Binary installation • Applied Custom patchset • Automatic installation of latest rubygems and bundler rbenv/ruby-build • Modify environment variables. • I’m also maintain them chruby/ruby-install • Modify a few environment variables.
- 40. rbenv/ruby-build You can get them from • homebrew • git clone Basic instructions are:$ rbenv install 2.5.0 $ rbenv install 2.6.0-dev $ RUBY_CONFIGURE_OPT=—disable-install-doc rbenv install 2.4.3 $ rbenv install jruby-9.1.16.0 $ RUBY_CONFIGURE_OPT= rbenv install rbx-3.89
- 42. git.ruby-lang.org It’s available under the ruby-lang.org now!!! https://git.ruby-lang.org • It’s READONLY • It’s built by cgit web interface, • It’s still experimental status. I’m preparing to it now.
- 43. What’s issues of migration of Git Toolchain: • Packaging script depends on Subversion repository and API. Issue Tracker: • Redmine on Heroku couldn’t use git repository. Strategy • How migrate git or github from svn (now resolved!)
- 45. Where do we go from here? 1. We migrate a toolchain like package script to git from svn. 2. We will ship ruby package from git.ruby- lang.org. 3. We will accept write commit on git.ruby- lang.org. 4. We will accept to merge pull-request on GitHub and sync them to git.ruby-lang.org (final goal)
- 46. Executive Officer CPO(Chief Productivity Officer) Director of Business Process Re-engineering Office at GMO Pepabo, Inc. @pepabo Hiroshi SHIBATA @hsbt https://www.hsbt.org