How We Distribute Ruby to the World
summary
Core team runs build and packaging pipelines: automated builds via Ruby CI, binary/source release workflow using ruby-build and RubyInstaller, and CDN/FTP distribution to mirrors; Ruby 2.6 targets Christmas release with an experimental JIT, Ruby 3x3 aims for 2020. Security triage uses encrypted PGP reports and a HackerOne bounty channel. Migration from Subversion to Git/GitHub is underway, incoming pull requests accepted, and maintainers support five active branches (2.6, 2.5, 2.4, 2.3, 2.2 security-only).
AI-written summary · about
chapters (23)
- 0:00Start
- 1:34self.introduce
- 3:47Ruby Committer
- 4:42Branch maintainers
- 5:42Platform maintainers
- 6:08Ruby 2.6 timeframe
- 7:51Version number and release cycle
- 8:39Ruby core backport model
- 9:37How do request to back port
- 10:45What's Ruby CI
- 12:15Ruby Cl resources
- 13:46Security release
- 14:45HackerOne
- 15:11Why security is hard
- 16:20What does mean "official"?
- 19:01Sponsors of the Ruby language
- 20:41Source distribution
- 21:30What's difference source package and others
- 22:28Start to build Ruby language from source
- 23:06Ruby package manager
- 23:45rbenv/ruby-build
- 25:57What's issues of migration of Git
- 28:09Where do we go from here?
