SOP: Releases

[dan-menlo]

SOP

• PRs
• Issues

[eckartal]

@dan-homebrew, I prepared the announcement SOP, copying the updated version here:

1. Get release details from the related Discord channel/forum created by Ashley
2. Sort all updates by importance and select the major/most important ones
3. Describe each update in one simple, clear sentence
4. Draft concise announcement texts for Twitter, LinkedIn, and Discord. Ensure you tag the contributors and the companies integrated with or supported
5. List Reddit channels for sharing updates and prepare posts accordingly
6. Prepare a GIF or png/jpg with 10% padding using ScreenStudio or Canva. PNG is for social media posts, JPG or GIF is for changelog
7. For announcement images: Use Ashley’s “Release Template” draft to add release names and updates
8. Identify relevant brands and communication contacts via LinkedIn, and send informative messages
9. Create a new changelog page and add updates with GIFs in a new .mdx file
10. Create an Announcement discussion on Jan’s Discussion board
11. Post texts and GIF drafts in Discord’s copywriting channel for feedback
12. Update texts and images based on feedback
13. Share updates on internal channels like Discord, Twitter, and LinkedIn post-release
14. Prepare and schedule separate feature announcements on social media with GIFs

cc: @0xSage, @imtuyethan

[LazyYuuki]

Currently, the cadence of 1 release per week feel too rushed and we don't have enough resources to do a quality delivery. The suggestion is to increase the cadence of release to 2 week instead. The process will be as follow (subjected to change):

The key idea here is that:

1. Development cycle for a release is 2 week (1 sprint)
2. Testing period internally of 1 week but overlapping with development cycle of next sprint
3. Release will always be in week 2 of a sprint
4. Development and Test is two separate work stream, not everyone will involve in both process.

The rationale behind is that:

1. User feedback of not wanting to update so frequently, they one more quality release than a lot of release.
2. Team currently does not have the result and the automation needed to work with shorter cadence yet.
3. Why no extra week just for testing? We shouldn't loop in everyone for testing -> wasted of development resources.

[freelerobot]

Open to this, but not mutually exclusive with setting up good QA automation and best practices.
We should not be doing any manual QA in 1 months time.