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

Release checklist #3135

Merged
merged 4 commits into from
Jun 26, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 58 additions & 0 deletions .github/ISSUE_TEMPLATE/release.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
---
name: k6 Release
about: k6 release accommodates activities and a checklist that has the k6 open-source release process.
title: 'k6 release v0.4x.0'
---

**Release Date**:

25th May 2023 << TODO: WRITE HERE THE UPDATED RELEASE DATE

## Release Activities

### At the beginning of the cycle

- [ ] Create a new branch `release-notes-v04x` and add a new related [release notes file](release-template/release%20notes) using the available [template](release-template/release%20notes/template.md).
- [ ] Go through the potential [dependencies updates](Dependencies.md) then create a PR if any is relevant.

### Release Preparation

~ 1 week before the release date.

- [ ] k6-docs PRs for all new or changed functionality have been created.
- [ ] All PRs to the k6 repository in the current [milestone](https://github.com/grafana/k6/milestones) have been merged.
- [ ] A pull request with the release notes and request the final reviews (including the @k6-browser, devrels folks).
- [ ] Open a PR for bumping [the version](https://github.com/grafana/k6/blob/9fa50b2d1f259cdccff5cc7bc18a236d31c345ac/lib/consts/consts.go#L11)).
- [ ] The release notes PR shared in the `#k6-oss-dev` internal channel mentioning all the impacted teams (@k6-browser, @k6-chaos, @k6 devrel and any other potential stackholder of the new release).
- [ ] `DefinitelyTyped/DefinitelyTyped` PR(s) is ready.

~ 1 day before the release date.

- [ ] PR for archiving the current k6's JavaScript [API version](https://github.com/grafana/k6-docs/wiki/Add-version-for-Javascript-API-documentation).
- [ ] Check that the [Existing k6-docs PRs](https://github.com/grafana/k6-docs/pulls) related to the new functionality are reviewed and rebased and pointing to the branch with k6's JavaScript API archived.

### Release Day

#### Documentation

- [ ] The PR with archiving the old version JS API merged first and rebase the rest on top.
- [ ] PRs with changes related to the release merged.
- [ ] After merging all k6-docs' PRs ensure that we have no broken links by checking "Check broken links" job in GitHub actions.
- [ ] [The new Docs Release vX.Y.Z](https://github.com/grafana/k6-docs/releases/new) published.
codebien marked this conversation as resolved.
Show resolved Hide resolved
- [ ] Release Notes PR contains the right links to the docs.

#### In k6 repository

- [ ] Release notes PR merged.
- [ ] A new tag from the CLI `vX.Y.Z` created (`git tag v0.4x.0 -m "v0.4x.0"`) & pushed.

#### Announcements

- [ ] A GitHub's link to the new release published in #k6-changelog.
- [ ] DevRel team is notified in #k6-devrel that release is published.
- [ ] The release's milestone closed.

## Wrapping Release

- [ ] `DefinitelyTyped/DefinitelyTyped` PR(s) merged.
codebien marked this conversation as resolved.
Show resolved Hide resolved
- [ ] Update the k6's `.github/ISSUE_TEMPLATE/release.md` if new repeated steps appear.