Actions
Feature #9235
openDocumentation for commercial support
Description
We should document the following:
- What happens when a Ruby version goes EOL?
- What can (my) company do to help maintain an EOL ruby?
- How do we backport security patches?
- How do we run tests?
- How do we release our own version of ruby?
Updated by hsbt (Hiroshi SHIBATA) over 8 years ago
- Target version changed from 2.1.0 to 2.2.0
Updated by jeremyevans0 (Jeremy Evans) almost 3 years ago
- Backport deleted (
1.9.3: UNKNOWN, 2.0.0: UNKNOWN) - ruby -v deleted (
2.1.0dev) - Tracker changed from Bug to Feature
Actions