Recommend new communication process for releases #200

New Issue

gosam · 2024-07-02T13:14:30Z

gosam commented

2024-07-02 13:14:30 +00:00

We have seen that the community would prefer to vote on releases earlier on in the process rather than at the end. But there is also good reason for this, in that we are not asking the community to dictate the content of our releases, rather we want them involved in the process of the deployment of the release. Of course, we appreciate input and we should definitely open the content of our releases up to the community as early as possible and ask for their feedback or input, and we should also reiterate to them that they are always free to leave GH issues on relevant repos and flag for an upcoming release.

Anyway long story short I will put together a new recommendation for process of releases and circulate and let's see if we can implement something that works better for everyone.

Write draft
Get feedback from comms team
Get feedback from stakeholders
Next steps decided based on feedback

We have seen that the community would prefer to vote on releases earlier on in the process rather than at the end. But there is also good reason for this, in that we are not asking the community to dictate the content of our releases, rather we want them involved in the process of the deployment of the release. Of course, we appreciate input and we should definitely open the content of our releases up to the community as early as possible and ask for their feedback or input, and we should also reiterate to them that they are always free to leave GH issues on relevant repos and flag for an upcoming release. Anyway long story short I will put together a new recommendation for process of releases and circulate and let's see if we can implement something that works better for everyone. - [x] Write draft - [ ] Get feedback from comms team - [ ] Get feedback from stakeholders - [ ] Next steps decided based on feedback

❤️ 1

gosam self-assigned this 2024-07-02 13:14:30 +00:00

gosam added this to the June 24 – July 07 project 2024-07-02 13:14:30 +00:00

gosam commented

2024-07-03 10:07:59 +00:00

Here is the draft:

https://docs.google.com/document/d/1NQ5-aQAFFppYICIUy_8JMJHGH4-gc8CfMUsYZhQjuWc/edit

Passed around for feedback from comms team and stakeholders. Ideally need:

Scott
Mik
Sabrina
Thabet
Kristof

Here is the draft: https://docs.google.com/document/d/1NQ5-aQAFFppYICIUy_8JMJHGH4-gc8CfMUsYZhQjuWc/edit Passed around for feedback from comms team and stakeholders. Ideally need: - [ ] Scott - [x] Mik - [ ] Sabrina - [x] Thabet - [ ] Kristof

gosam commented

2024-07-04 10:37:15 +00:00

Waiting for feedback, this will surely not be completed in this sprint. I will move to the next one and put in blocked for now. We should be having a meeting on 3.15 next Tuesday so will update after that.

gosam modified the project from June 24 – July 07 to July 08 – July 21

2024-07-04 10:37:19 +00:00

gosam commented

2024-07-04 11:35:31 +00:00

Thabet has a strong opinion here that the community should not vote at all on tech developments. We'll have to discuss next week.

gosam modified the project from July 08 – July 21 to July 22 – Aug 04

2024-07-23 08:09:28 +00:00

gosam modified the project from July 22 – Aug 04 to Aug 05 – Aug 18

2024-08-02 11:04:54 +00:00

gosam referenced this issue

2024-08-09 06:45:40 +00:00

Announce TF Grid 3.15 #204

gosam commented

2024-08-09 06:48:24 +00:00

As part of #204 please also include in that post or create a new post to clarify the release process and why we do things the way we do it. Can use the draft above, it's a good start, but no need to go into so much detail or background.