The future of sdk.gnome.org
Now that flat-manager is working, we would like to use it for nightly apps too. Here is a rough plan of the tasks needed to do it. I marked every task with whoever I think can do it best, but I can help with everything that doesn't require special permissions.
Here is my plan:
- Migrate a test app to flat-manager
-
maybe epiphany? (@mcatanzaro / @akitouni / @alatiera) GNOME/epiphany!383 (merged) GNOME/epiphany!387 (closed) -
Update CI Templates as needed? (@alatiera / @akitouni) GNOME/citemplates!5 (merged) GNOME/citemplates!6 (merged) GNOME/citemplates!7 (merged)
-
- Improve the experience downloading from the new server
-
Enable HTTP/2 (or at least connection keep-alive) on gbm-builder. (@barthalion / @averi)
-
- Announce it publicly
-
Decide on a final name for the repo -
Decide on a deprecation period for the old repos -
Announce the migration -
Mark the old repos as EOL
-
- Decomission old stuff (after the deprecation period is over)
-
Decommission sdkbuilder.g.o (@averi) -
make gnome{1,2}.codethink.co.uk gitlab CI runners (@jjardon / @barthalion) -
drop the old repos from spinner.g.o (sdk.g.o) and add redirects if we decide not to break compatibility.
-
- Add support for more architectures
-
aarch64 versions of gnome-runtime-images (@alatiera / @akitouni) -
Decide what to do for arm and i386 (in the same image as 64bit or separate images)
-
Edited by Javier Jardón