Skip to content

Instantly share code, notes, and snippets.

@pbatard

pbatard/RufusMaintainer.md

Last active March 25, 2023 15:08
Star
Embed
What would you like to do?
Learn more about clone URLs
Download ZIP
Rufus Maintainer's Corner
Raw
RufusMaintainer.md

Github stats Github stats Github stats Github stats Github stats Github stats Github stats

  • Make sure all milestones issues have been addressed
  • Make sure the ChangeLog is up to date, with actual release date
  • Update MSYS/MinGW and run a test release in case breakage was introduced
  • Update Readme.md if relevant (major new feature, etc.)
  • Run .\gen_listing.ps1 in res\appstore
  • Commit and tag release
  • Git push release commit
  • Wait for VS2022 builds and download all artifacts to res\appstore\ Make sure to pick the artifacts from tagged release!
  • Run res\appstore\packme.cmd. This will sign the MSVC executables
  • Wait for MinGW build and download x86 artifact (as rufus-#.##.exe)
  • Sign the MinGW executables
  • Upload signed executables to VT Monitor, VirusTotal and AVG whitelist
  • Run a limited set of tests with actual release binary
  • Upload all the binaries (including _arm & _arm64) to staging server and create a rufus-#.#p.exe
  • Run ./_sign.sh script to create .sig
  • Edit github.io's downloads/index.html page to include the new download links by sourcing the staging server's download page
  • Validate github.io's downloads/index.html page
  • Update index.php in rufus-web and copy it to staging server Note: Make sure that any href's in the ChangeLog have target="_blank" due to using a frame.
  • (OPTIONAL) Upload new 1x and 2x screenshots if needed
  • Run _refresh.sh from MinGW in github.io directory to update index_##.html pages (also update en_US if different)
  • Run _create_pot.sh to update locale/index.pot
  • Validate at least en/index.html and fr/index.html
  • Also Update Loc.ver to point to latest version
  • Create a draft release and upload binaries to github release (if BETA, need to create a temporary v#.#_BETA tag). Don't forget to upload the .sig as well as the portable version. Also don't forget to uploade portable executable.
  • Commit and push github.io's modified content.
  • Submit executable to Windows Defender so that they don't get tricked AGAIN into a false positive
  • Test download links (including latest source tarball)
  • Update AppStore submission and upload new package as well as a new folder with .csv
  • Update reboot.pro download
  • Update FossHub downloads
  • Announce release on reboot.pro and mydigitallife relevant threads
  • Update Wikipedia page
  • Close milestone
  • Edit this page for the download counters

~24 hours after release

  • Update Rufus_win.ver on staging server
  • Run _sign.sh script to create .ver.sig
  • Update and push github.io
  • Test automatic update

Post-Release

  • Wait ~1 week and edit download's index.html to remove the BETA links
  • Delete the BETA git tags and remove BETA release
  • _chver.sh to rufus-next

VirusTotal links

Windows Defender Submission Data

Windows Defender Submission Extra

From an elevated command prompt, change to directory %programfiles%\windows defender and execute mpcmdrun.exe with option GetFiles:

cd "%programfiles%\windows defender"
mpcmdrun.exe -GetFiles

All created log files will be compressed into MPSupportFiles.cab. Please send us the detected file and MPSupportFiles.cab using https://aka.ms/wdsi We will continue the investigation once we receive the support log files.

Also known as Seriously Microsoft?!?: microsoft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment