Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Formalize release process #2752

Open
danieldaquino opened this issue Nov 27, 2024 · 5 comments · May be fixed by #2818
Open

Formalize release process #2752

danieldaquino opened this issue Nov 27, 2024 · 5 comments · May be fixed by #2818

Comments

@danieldaquino
Copy link
Contributor

The release process is manual, and there are enough details that human errors are easy to happen.

I propose that we create a github issue template for the release process, containing a full checklist, and each release is a ticket where we work through the checklist.
@danieldaquino
Copy link
Contributor Author

danieldaquino commented Nov 27, 2024 •
edited
Loading

What comes to mind for the checklist:

  • Make build off of release target (not damus build)
  • check CI tests
  • Create changelog
  • Upload to TestFlight
  • Include TF build to Purple group, Translators group and internal contributors/developers
  • Make release video and marketing material

After:

  • Merge changelog
  • Do version bump

@jb55
Copy link
Collaborator

jb55 commented Nov 28, 2024 via email

@danieldaquino
Copy link
Contributor Author

Automate all the things.

@jb55 I created a workflow on Xcode Cloud to automate release candidate building, testing, and release build generation. It's not 100% automated yet to allow me to be in the loop and help ensure expected behavior, but I will keep formalizing and automating the process!

@danieldaquino danieldaquino mentioned this issue Dec 20, 2024
Closed
21 tasks
@danieldaquino
Copy link
Contributor Author

Automate all the things.

I created a workflow on Xcode Cloud to automate release candidate building, testing, and release build generation. It's not 100% automated yet to allow me to be in the loop and help ensure expected behavior, but I will keep formalizing and automating the process!

This also has other benefits:

  1. Fewer human errors
  2. Previous builds are available for download in Xcode Cloud, making it easier to symbolicate crashes (I realized we need to keep those archive files to be able to symbolicate some crash logs, and we can't download the ones we submit to AppStore Connect)

@jb55
Copy link
Collaborator

jb55 commented Dec 20, 2024 via email

danieldaquino added a commit to danieldaquino/damus that referenced this issue Jan 22, 2025
@danieldaquino
Add release process issue template
e2835a7 
A Github issue template to help formalizing the release process, in
order to avoid human errors in the process.

Closes: damus-io#2752
Signed-off-by: Daniel D’Aquino <[email protected]>
@danieldaquino danieldaquino linked a pull request Jan 22, 2025 that will close this issue
Open
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add release process issue template danieldaquino/damus
2 participants
@jb55 @danieldaquino