To Do for releasing Ferdium

I expanded here on a list I found on discord on things that need to be done before initial release. if I missed something or added something unnecessary please let me know/ add it in comment

• update name to “Ferdium” everywhere
• update visual branding everywhere (logo, images in READMEs of app, recipes and server)
• change copyright message everywhere to “Ferdium Contributors”
• Setup the nightly build process
• Setup the beta build process
• Enable Snapstore login + publishing
• review licensing
• add ‘https://ferdium.org’ to org repo description
• temporarily make https://ferdium.org/download redirect to https://github.com/ferdium/ferdi/releases
• get apple dev license and sign the macos builds
• get windows dev license and sign the windows builds
• host/run the API server
• get the debug API server running
• Initial setup is done. For the following (post 6.0.0 release) see #185
• transferring pre-existing ferdi profile to ferdium:
  • Migration scripts (#4)
  • Further testing on migration scripts
• replace ferdi with ferdium on all package managers
  • homebrew (we ended up creating our own tap: https://github.com/ferdium/homebrew-ferdium )
  • scoop
  • chocolatey
  • winget
  • aur
  • flatpak
• documentation and FAQ ⇒ first FAQ on https://ferdium.org/faq
• then make an initial release - Ferdium 6.0
• make https://ferdium.org/download redirect to https://github.com/ferdium/ferdium-app/releases (or just remove the old redirect) ⇒ custom page on the website
• after the initial release: website
• Make recipes automatically update on the API server. https://github.com/ferdium/ferdium-server/issues/31 and https://github.com/ferdium/ferdium-server/issues/32
• Find a solution for https://github.com/ferdium/ferdium-app/issues/224

[vraravam]

Closing this ticket now that we have released v6.0.0

[dqos]

Because binaries are not signed yet. For support please join our Discord. This issue is for TODO tracking.