This memo is concerning on the issue: ruby/www.ruby-lang.org#2965.
- Ubuntu: https://ubuntu.com/about/release-cycle
- Node.js: https://github.com/nodejs/Release
- Python: https://devguide.python.org/versions/index.html
- PHP: https://www.php.net/supported-versions.php
| Features (requester) | Ubuntu | Node | Python | PHP | (proposal) |
|---|---|---|---|---|---|
| order (unak) | descending | ascending | ascending | ascending | ascending |
| shows EOL branch (unak) | (interim only) | ― | ✓ | ✓ | ✓ |
| today line (znz) | ― | ― | ✓ | ✓ | ✓ |
| multi phase color (unak) | ✓ | ✓ | ― | ✓ | ✓ |
| EOL timeline color | ― | ― | ✓ | ― | ✓ |
| alters branch name style | ✓ | ― | ― | ✓ | ✓ |
| future color | ― | ― | ― | ― | ✓ |
| text label in timeline | ― | ✓ | ✓ | ― | ― |
| phase color legend | ✓ | ― | ― | ✓ | ― |
| media | browser SVG | static SVG | browser SVG | server SVG | browser SVG |
| technology | D3.js | D3.js | Mermaid | PHP | Google or vis-timeline |
- D3.js: https://d3js.org/
- Mermaid Gantt: https://mermaid.js.org/syntax/gantt.html
- Mermaid does not support putting two sections in the same line: mermaid-js/mermaid#1996
- Google Charts Timeline: https://developers.google.com/chart/interactive/docs/gallery/timeline
- vis-timeline: https://github.com/visjs/vis-timeline
CodePen: timeline coloring proposal
These use Google Charts timelines. A self-hosted library (e.g., vis-timeline) is perhaps better.
The page /ja/downloads/branches/ should be added, IMHO.
- I want to be able to see at a glance the current state of the branches that are maintained. Green for safe, orange for warning, vivid for available.
- Text on the timeline cannot be neatly arranged in short sections. Especially in mobile browsers.
- Legend is not user friendly at least for this level of complexity.
- The today-line may be impossible with Google Charts.
- Consideration for low vision may not be enough. I picked these base colors from Google Charts default coloring set.
- branches.yml has no
security_maintenace_date - A liquid-includable JSON format data on the source tree may help efficiency and security. A current prototype uses liquid generated inline JSON but it has no suitable escaping so that way may be fragile. With liquid, suitable JSON escaping is very complicated.