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) almost 11 years ago
- Target version changed from 2.1.0 to 2.2.0
Updated by naruse (Yui NARUSE) almost 7 years ago
- Target version deleted (
2.2.0)
Updated by jeremyevans0 (Jeremy Evans) over 5 years ago
- Tracker changed from Bug to Feature
- ruby -v deleted (
2.1.0dev) - Backport deleted (
1.9.3: UNKNOWN, 2.0.0: UNKNOWN)
Actions
Like0
Like0Like0Like0