Give examples when asking for the configuration values to make these scripts even more foolproof :)
svn path=/trunk/Release_Engineering/; revision=2259
Download the wine_gecko packages from svn.reactos.org and add them to a newly created "optional" folder.
This mustn't be done manually (because non-redistributable copyrighted files may easily slip through), but this is also mandatory for a release.
svn path=/trunk/Release_Engineering/; revision=2258
Add a set of scripts to fully automate our Building and Packaging process for ReactOS Releases.
This ensures we always start from a 100% clean environment, all required modules are added and each command is run with the right parameters.
Inspired by https://www.jitbit.com/alexblog/249-now-thats-what-i-call-a-hacker/ :)
TODO: I don't have a solution for the VM packages and optional modules yet.
Also the wallpapers module needs some cleanup or it will bloat the packages.
svn path=/trunk/Release_Engineering/; revision=2256
- Add a document "Packaging ReactOS Releases.odt" describing how each ReactOS release package is created.
This file also supersedes the "SVN-Readme.txt" files in the "QEMU" and "VMware" subdirectories, so I removed them.
svn path=/trunk/tools/Release Engineering/; revision=638
A user, who extracts this package, will now first see the "boot.bat" and "Readme.txt" files, so he can't be confused by all these QEMU files ;-)
svn path=/trunk/tools/VM-Templates/; revision=371
- Add a directory "VM-Templates" containing new QEMU and VMware templates. These templates can be used for packaging the next ReactOS Releases
svn path=/trunk/tools/VM-Templates/; revision=228