-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
3.43.0 release tracking issue #39333
Comments
Hey, @sourcegraph/batchers (@eseliger @LawnGnome @courier-new @adeola-ak @BolajiOlajide @Piszmog @malomarrec @chrispine @danielmarquespt) - we have been mentioned. Let's take a look. |
Sourcegraph 3.43.0 has been published
@coury-clark: Please complete the post-release steps before closing this issue. |
Waiting to update the release-config until I confirm when the September release is going to be. |
Issue closed by release tool. #39333 |
3.43 release
This release is scheduled for Aug 22, 2022, 6:00 PM (UTC).
Setup
dev/release/release-config.jsonc
onmain
is up to date with the parameters for the current release.sourcegraph@main
.Cut Release (three days before release - Aug 17, 2022, 6:00 PM (UTC))
Perform these steps three days before the release date to generate a stable release candidate.
Prepare release
Do the branch cut for the release:
Update the changelog and create pull requests:
Manually review the pull requests created in the previous step and merge.
Create the
3.43
branch off the CHANGELOG commit in the previous step:Upon branch cut, create and test release candidates:
Tag the first release candidate:
Ensure that the following Buildkite pipelines all pass for the
v3.43.0-rc.1
tag:File any failures and regressions in the pipelines as
release-blocker
issues and assign the appropriate teams.Revert or disable features that may cause delays. As necessary,
git cherry-pick
bugfix (not feature!) commits frommain
into the release branch. Continue to create new release candidates as necessary, until no morerelease-blocker
issues remain.Note: You will need to re-check the above pipelines for any subsequent release candidates. You can see the Buildkite logs by tweaking the "branch" query parameter in the URLs to point to the desired release candidate. In general, the URL scheme looks like the following (replacing
N
in the URL):Sourcegraph:
https://buildkite.com/sourcegraph/sourcegraph/builds?branch=v3.43.0-rc.N
Post a release status update to Slack:
Post the following message to the #cloud channel asking for the release candidate to be deployed to a test managed instance. You're good to go once the instance is up and running:
Release Day (Aug 22, 2022, 6:00 PM (UTC))
Stage release
On the day of the release, confirm there are no more release-blocking issues (as reported by the
release:status
command), then proceed with creating the final release:main
after the branch cut (whose changes are not in the3.43
branch).main
after the branch cut (whose changes are not in the3.43
branch).v3.43.0
tag:v3.43.0
release Docker images to be available in Docker HubFinalize release
sourcegraph/sourcegraph@main
into the release branch.v3.43.0
has been createdv3.43.0
has been createdPost-release
dev/release/release-config.jsonc
with the parameters for the next release.upcomingRelease
to the current patch releasepreviousRelease
to the previous patch release versionreleaseDate
to the current date (time is optional) along withoneWorkingDayAfterRelease
andthreeWorkingDaysBeforeRelease
captainSlackUsername
andcaptainGitHubUsername
accordinglysourcegraph@main
.Note: If a patch release is requested after the release, ask that a patch request issue be filled out and approved first.
The text was updated successfully, but these errors were encountered: