raylib new release publish checklist

[raysan5]

This is the list with required steps I usually follow to publish a new raylib release, categorized and organized by priority. It's a slow and mostly manual process that really takes long time and effort.

raylib code update checklist

• Update ALL raylib/src/external libraries: dependencies list
• Compile raylib/src for ALL supported platforms -> CI: GitHub Actions, Travis, AppVeyor
• Update and test raylib/examples
• Update and test raylib/templates
• Update and test raylib/games

raylib webpage update checklist

• Update raylib.com/cheatsheet.html - Add/Review new functionality
• Review raylib.com/examples.html - Add new examples -> Port examples for web compilation
• Update raylib.com/games.html - Add new games and recompile for web
• Review raylib.com/index.html - Add new version features
• Update raylib ARCHITECTURE image if required

raylib GitHub update checklist

• Review README - Any addition/modification required?
• Review HISTORY - Add new version evolution comments
• Review CHANGELOG - Check, categorize and format all changes for the release
• Review CONTRIBUTING - Add new contributors
• Review ROADMAP - Review current implementations and add future plans

raylib package setup checklist

• Update Notepad++ to latest version -> 7.8.4
• Update Notepad++ raylib functions list xml
• Review Notepad++ compiling scripts
• Test Notepad++ compiling scripts
• Update MinGW to latest version -> GCC 8.1
• Update TCC to latest version

raylib installer package checklist

• Setup package information (version, publisher, …)
• Setup package files (MinGW, Notepad++, raylib)
• Compile package: raylib_installer_v[x.x].[migw | tcc].exe
• Test raylib generated package

Please, feel free to comment and give some feedback!

[raysan5]

ok, it seems everything is ready... :)