Announce the Allegro 4 move

Author: SiegeLordEx

en/_include/before-body

@@ -14,6 +14,7 @@
     - [Examples](examples_demos.html)
     - [Bug tracker](https://github.com/liballeg/allegro5/issues)
     - [Language bindings](bindings.html)
+    - [Other Git repositories](https://github.com/liballeg)
 
 * **Downloads**
     - **[Latest version](download.html)**

en/_meta/atom

@@ -184,3 +184,5 @@ en/news/news.2024-11-27 uuid=50042891-e644-45ea-b9ef-51d55191e2bb
 en/news/news.2024-11-27 date=2024-11-27T19:54:22-08:00
 en/news/news.2024-12-28 uuid=6bcb860f-3239-4ad2-82ef-13c91418e9e9
 en/news/news.2024-12-28 date=2024-12-28T20:23:02-08:00
+en/news/news.2025-04-20 uuid=1dc12402-9389-462d-8c40-c2d981c8c0b3
+en/news/news.2025-04-20 date=2025-04-20T16:32:18-07:00

en/news/news.2025-04-20

@@ -0,0 +1,15 @@
+## 2025-04-20 - Allegro 4 moved to its own repository.
+
+We've moved Allegro 4 sources to its [own repository](https://github.com/liballeg/allegro4).
+
+Previously (and, in fact, currently) Allegro 4 was placed in a few separate
+branches in the main Allegro 5 repository. This made it hard to find and
+cumbersome to use. So, we've moved the relevant branches, tags and issues to a
+separate repository. We'll probably make a new release so that there is also a
+"latest" release with the relevant source archives (and also to nominally treat
+a bit of bitrot).
+
+Note that Allegro 4 should still be treated as mostly abandoned, and won't be
+receving regular updates. This change is for the convenience of the few
+remaining users of it, and to enable easier historical exploration of the
+repository using Github's tooling.