Ruby¶
NOTE: Please DO NOT report security issues via this system.¶
Please report through our bounty program page at HackerOne or send a mail to security@ruby-lang.org instead.
Reported problems will be published after fixes.
Contributions¶
- Contributions
- Donation How to donate Ruby development.
For Users¶
- UpgradingRuby
- MJIT How to use Ruby's JIT compiler
Also follow news announcements on www.ruby-lang.org.
For Developers¶
- DeveloperHowto, DeveloperHowtoJa (日本語)
- HowToReport, HowToReportJa (日本語)
- HowToRequestFeatures
- HowToRequestBackport
- HowToContribute
- HowToAnnounce
- Security
- Documentation guidelines at documenting-ruby.org
For Committers¶
Ruby-core¶
See the general maintenance policy for Ruby.
Release Engineering¶
Developer Meetings¶
Realtime Meetings are run according to the DevelopersMeetingRealtimeGuidelines
IRC meetings are run according to the DevelopersMeetingIRCGuidelines
Previous Issues for Developers Meetings¶
For past meetings please see the DevelopersMeetingArchive.
Projects¶
- Ruby Enhancement Proposals (REP)
- StdlibGem
- DevelopmentProjects
- DTraceProbes
- DenverAccord
- CryptoProject
Continuous Build¶
Developer docs¶
Memorandum¶
- Script Encoding Summary (日本語版)
- Assumptions of Ruby C source code (日本語版 Rubyソースコードの仮定事項)
- 修正予定のないこと (WontFix) (日本語)
- PortabilityHacks
- r35480_ExtendedMemo
- MachineInstructionsTraceWithGDB
- ImplementationOfModulePrepend
- flonum_tech
- GC_design
- RGenGC
- RincGC_ja
- RefinementsSpec
- Frozen Array and Hash literals proposal
- CAPI obsolete definitions
- Ruby 3x3 Optimization Ideas
Obsoleted¶
Release Plan¶
- Release plan, Supported platforms
- Supported platforms (日本語)
- How to release Ruby 1.9
- 1.9.3 リリース作業手順 -> リリース手順(Japanese)
- Migrations issues from 1.8
Like1