| ▲ | MostlyStable 2 days ago | |
>Care has been taken to ensure minimal impact to BookStack end users. The original GitHub repository is still staying around, and will essentially act as a mirror of the codebase on Codeberg, so any existing instances fetching updates from GitHub can continue to do so. Since they are keeping the github as essentially a mirror, doesn't this obviate those concerns? -edit- although also: >although eventually we will only create releases on Codeberg so it’s advised to watch/subscribe to them there instead: I guess someone _else_ could choose to fork and keep up-to-date. | ||
| ▲ | ssddanbrown 2 days ago | parent [-] | |
BookStack maintainer here. Just to clarify on that, the GitHub repo will continue to be updated and mirror the Codeberg repo (including release tags/code) for the foreseeable future, it's just that I might stop specifically publishing GitHub release entries (details on the release tag) at some point to avoid the duplication of work. | ||