release_process

validate images

The list of images not yet released and still in validation : https://mirrors.o2switch.fr/batocera/rc.html

for each image to release

update, and check you're in the udpated version
check minimum 3 emulators including retroarch
check audio is working
check eventually kodi
maximum validation duration : 10 minutes

The aim of validation is not to discover bugs. This was the aim of the previous builds.

The aim is to validate that the last build image works correctly : aka booting, and minimal function to avoid release a corrupted image.

prepare images links on the mirror server for faster downloads

update x86_64, rpi images on the mirror.

update rc.html to make visibility on what to test

# to update https://mirrors.o2switch.fr/batocera/rc.html
# this is the list of ready rc images not yet relased.
# update it whe new images are released with:
connect on mirrors.o2switch.fr and execute ./listRC.sh

release some images

# connect on mirrors.o2switch.fr
1) ./doRelease.sh rk3326 39
2) ./listInstalls.sh # update list of install files (to install from batocera) (https://mirrors.o2switch.fr/batocera/installs.txt)
3) ./listRC.sh # reupdate rc.html

# on the website
4) updateImages.sh

update the changelog

# generate and copy the changelog on the website (remove any lines from the next version already present)
~/git/batocera.linux$ python3 ./scripts/linux/convertChangelog.py < ./batocera-Changelog.md > changelog-content.html

update the last version file

includes/config.php

add new boards

see images/download and include/boards.php to add some new boards on the website.

validation devices

https://docs.google.com/spreadsheets/d/1_YZtQyVpyF9mcUKoy6AAgTSP-IdOuQ5AliYSNosg8tc/