What I have been doing to create new AppImage releases for Cinelerra-GG (basically these are what I call Moderator tasks). Neither difficult nor time-consuming.
- as provided or updated, commit any changes to GIT source and GIT manual on server - update msg/txt to describe more noteworthy items in the release and checkin - create a new PDF and HTML manual version so it has the current date - update the Release Notes in Office Writer and create PDF file to put on website - build new binaries of CinGG for a) most used generic x86_64 with libsvtav1 and opencv built on fedora 32 b) ubuntu 16.04 for older x86_64 with libaom 3.4 instead of 3.8 c) same for ubuntu 16.04 with alternative shortcuts d) debian 11 32-bit for newer i386 with libsvtav1 e) debian 9.1 32-bit for older i386 (requires special export ac_cv_header... and FFMPEG_EXTRA_CFG...) - copy all of the HTML manual files to the newly built bin/doc/CinelerraGG_Manual for Help inclusion - create AppImages using linuxdeploy from the binaries - make tgz files of the CinGG source and HTML Manual files to put on the website - 10 files are moved to /tmp on the server via firehoze, or scp, or rsync (firehoze was needed in the past to get multiple network streams as numerous packages for all of the various distros and distro versions were moved over but that has been replaced by the generic AppImages). On the server, copy files from /tmp to final location which involves some tar extracts, deletions, and replacing files. - set tags on GIT for both the source and manual to note a new release version update - update News in WordPress on website and notify Mailing list of release
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
