Release description is very incomplete

[JayFoxRox]

The Release description should mention the included / merged features.

Furthermore it should not blindly recommend the huge CitraSetup.exe. Instead we should only have nupkgs and provide CitraSetup.exe outside of the daily Releases and tell people to run it if they want to update (so they don't redownload it each time). I'm sure we can improve this update ritual further, but that should probably be part of a different issue.

---

Technical question: Where is the release description generated?

[Dragios]

I agree with @JayFoxRox Also needs to mention that nupkgs is actually an archieve file that can be open on any file archiver tool like WinZip, 7-zip, WinRAR and etc. I myself did not know about this until @jroweboy mention about nupkgs file.

My suggestion is to update the Changelog page manually to make it more visible to users on which commit has been merged. https://github.com/citra-emu/citra-bleeding-edge/releases/tag/bleeding-edge-70

[jroweboy]

Where is the release description generated?

Its part of the squirrel pr #3 in appveyor.yml

Instead we should only have nupkgs and provide CitraSetup.exe outside of the daily Releases and tell people to run it if they want to update (so they don't redownload it each time).

that doesn't make much sense as a first time user still needs to run CitraSetup.exe and other users will need the nupkgs. nupkgs + RELEASES file is used by the updater library to update to the latest version. So both files are used, just by different groups of people. With the user folder moving out of the citra folder, there shouldn't be any reason for someone to modify anything in the install location anymore.

My suggestion is to update the Changelog page manually to make it more visible to users on which commit has been merged. https://github.com/citra-emu/citra-bleeding-edge/releases/tag/bleeding-edge-70

My dream was to include this information as part of the updater. Sadly due to a bug in mingw its not really feasible. The windows API function to have pretty display boxes just isn't available on the version of mingw in appveyor. Maybe someday I'll find a work around. Maybe just link people to the changelog online or something.

Also needs to mention that nupkgs is actually an archieve file that can be open on any file archiver tool like WinZip, 7-zip, WinRAR and etc. I myself did not know about this until @jroweboy mention about nupkgs file.

Nah, in the future (near future when i get the nightlies up + mac and linux on bleeding edge) then I plan on adding portable windows version as well. (Just upload a zip for it) Also I want to make full static builds on windows because copying the right dlls is way more painful than just making a static build. Plus I want to experiment with LTO at somepoint as well to trim binary sizes. Lots to do, little time to do it :D