mirror of
https://github.com/ether/etherpad-lite.git
synced 2026-07-22 17:46:55 +00:00
Patch-specific release branches should never diverge from the tag, so they serve no useful purpose. (If they do diverge, which some did before I deleted them all, what does it mean? Are we going to move the tag in the future? It's just too confusing.) In the future we might want to do major- or minor-specific branches (e.g., `release/1` or `release/1.8`), but only if we want to maintain old releases. For example, if 2.0 is a major release that doesn't work with plugins designed for 1.x we might want to maintain a `release/1` branch that continues to get bugfixes while the bulk of new work continues to land on `develop`. If we do decide to maintain old releases we'll need a new set of release scripts (or edit the `release.js` script on the `release/1` branch). |
||
|---|---|---|
| .. | ||
| bin | ||
| locales | ||
| node | ||
| static | ||
| templates | ||
| tests | ||
| ep.json | ||
| etherpad_icon.svg | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| web.config | ||
Ignore this file and see the file in the base installation folder