Skip to content
Snippets Groups Projects
Closed 3.1 release plan
  • View options
  • 3.1 release plan

  • View options
  • Closed Issue created by Warren Gifford

    Created by: nicksnyder

    3.1 Release (2019-02-20)

    No later than 5 working days before release (2019-02-15)

    • Choose dates/times for the steps in this release process and update this issue template accordingly. Note that this template references working days, which do not include weekends or holidays observed by Sourcegraph.
    • Send message to #dev-announce with a link to this tracking issue to notify the team of the release schedule.
    • Private message each teammate who has open issues in the milestone and ask them to remove any issues that won't be done three working days before the release.

    3 working days before release (2019-02-14)

    • 4:00 PM PT Create the branch for this release off of master (e.g. 3.1) and tag the first release candidate (e.g. v3.1.0-rc.1).
    • Add a new section header for this version to the CHANGELOG immediately under the ## Unreleased changes heading. Commit and git push this change directly to upstream master.
    • Send a message to #dev-announce to announce the release candidate.
    • Run Sourcegraph Docker image with no previous data.
      • CLEAN=true IMAGE=sourcegraph/server:3.1.0-rc.3 ./dev/run-server-image.sh
      • Initialize the site by creating an admin account.
      • Add a public repository (i.e. https://github.com/sourcegraph/sourcegraph).
      • Add a private repository (i.e. https://github.com/sourcegraph/infrastructure).
      • Verify that code search returns results as you expect (depending on the repositories that you added).
      • Verify that basic code intelligence works on Go or TypeScript.
    • Upgrade Sourcegraph Docker image from previous released version.
      • CLEAN=true IMAGE=sourcegraph/server:3.0.1 ./dev/run-server-image.sh
      • Initialize the site by creating an admin account.
      • Add a public repository (i.e. https://github.com/sourcegraph/sourcegraph).
      • Add a private repository (i.e. https://github.com/sourcegraph/infrastructure).
      • CLEAN=false IMAGE=sourcegraph/server:3.1.0-rc.3 ./dev/run-server-image.sh
      • Verify that code search returns results as you expect (depending on the repositories that you added).
      • Verify that basic code intelligence works on Go or TypeScript.
    • Run Sourcegraph on a clean Kubernetes cluster with no previous data.
    • Upgrade Sourcegraph on a Kubernetes cluster.
    • Add any release blocking issues as checklist items and start working to resolve them.

    As necessary

    • git cherry-pick necessary bug fixes (not features) from master into the release branch.
    • Re-test any flows that might have been impacted by commits that have been cherry picked into the release branch.
    • Tag additional release candidates.

    1 working day before the release (2019-02-10)

    • 10:00 AM PT Tag the final release.
    • Send a message to #dev-announce to announce the final release.
    • Verify that all changes that have been cherry picked onto the release branch have been moved to the approriate section of the CHANGELOG on master.
    • Wait for the final Docker images to be available at https://hub.docker.com/r/sourcegraph/server/tags.
    • Update the image tags in deploy-sourcegraph (e.g. d0bb80)
    • Wait for Renovate to pin the hashes in deploy-sourcegraph (e.g. #190), or pin them yourself.
    • In deploy-sourcegraph, tag the release (e.g. v3.0.0) and create the release branch off of master at this commit (e.g. v3.0).

    On or before release day (2019-02-20)

    • 10:00 AM/PM PT Merge the blog post.
    • Update the documented version of Sourcegraph in master (e.g. find . -type f -name '*.md' -exec sed -i '' -E 's/sourcegraph\/server:[0-9\.]+/sourcegraph\/server:$NEWVERSION/g' {} +) (e.g. https://github.com/sourcegraph/sourcegraph/pull/2210/files ).
    • Update versions in docs.sourcegraph.com header (example)
    • Update latestReleaseKubernetesBuild and latestReleaseDockerServerImageBuild in master.
    • Review all issues in the release milestone. Backlog things that didn't make it into the release and ping issues that still need to be done for the release (e.g. Tweets, marketing).
    • Close this issue.
    ✓ 47 of 47 checklist items completed

    Activity

    • All activity
    • Comments only
    • History only
    • Newest first
    • Oldest first