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.

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

k6 release v0.48.0 #3382

Closed
47 of 48 tasks
olegbespalov opened this issue Oct 11, 2023 · 4 comments
Closed
47 of 48 tasks

k6 release v0.48.0 #3382

olegbespalov opened this issue Oct 11, 2023 · 4 comments
Assignees
Labels
Milestone

Comments

@olegbespalov
Copy link
Contributor

olegbespalov commented Oct 11, 2023

Release Date:

December 6th 2023 (06.12.2023)

Release Activities

At the beginning of the cycle

Release Preparation

~ 1 week before the release date.

~ 1 day before the release date.

Release Day

Documentation

  • Open and merge a PR from main in the k6-docs repository, copying the current k6's next to a folder named with the k6 version (e.g. v0.48.x).
  • Ensure the k6 repository release notes PR contains the correct links to the docs.

In k6 repository

Announcements

  • Publish a link to the new GitHub release in the #k6-changelog channel.
  • Notify the larger team in the #k6 channel, letting them know that the release is published.
  • Close the release's milestone.

Wrapping Release

@olegbespalov olegbespalov self-assigned this Oct 11, 2023
@olegbespalov olegbespalov added this to the v0.48.0 milestone Oct 12, 2023
@ka3de ka3de self-assigned this Oct 26, 2023
@inancgumus
Copy link
Member

inancgumus commented Oct 31, 2023

Shouldn't the k6-docs branch be named release-v0.48.0 instead of release-notes-v0.48.0? According to this. We've changed the branch name accordingly (also in this issue's description), but feel free to revert it if there is a misunderstanding.

Ideally, I suggest naming every branch the same to avoid confusion like this. Maybe like release-v0.48.0 for each repository (k6, k6-docs, and k6-DefinitelyTyped).

cc: @grafana/k6-core @grafana/k6-browser

@codebien
Copy link
Contributor

Maybe like release-v0.48.0 for each repository (k6, k6-docs, and k6-DefinitelyTyped).

@inancgumus I agree with you, it would be easier for everyone to remember what to research for. Can you open a PR to change it on the template?

inancgumus added a commit that referenced this issue Nov 1, 2023
@inancgumus
Copy link
Member

@codebien Sure: #3434.

@olegbespalov
Copy link
Contributor Author

In my opinion, having the exact same branch name is not something urgent and essential. The most important part is to communicate how to find this branch properly, and this is done by just having the reference from this task.

However, at the end of the cycle, during the last activity of the reviewing process, we could return to #3434.

inancgumus added a commit that referenced this issue Nov 7, 2023
@olegbespalov olegbespalov mentioned this issue Nov 23, 2023
26 tasks
This was referenced Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants