Skip to content

Seed Changelog v2 with exciting / user-visible changes from the April / May cycles #4187

Closed
@jankeromnes

Description

@jankeromnes

Context

We'd like to resume publishing regular changelogs for Gitpod:

Process

We want to keep track of exciting / user-visible changes in Gitpod, by either:

  • Maintaining a CHANGELOG.md file (or multiple files)
  • Adding a changelog label to relevant Pull Requests

(Currently being decided.)

Roles / responsibilities:

  • Author of Pull Request: Should add a one-line changelog entry if their change is user-visible or otherwise exciting/interesting for users (e.g. performance/stability improvements)
  • Reviewer of Pull Request: Should remind the author about adding a changelog entry
  • Developer Success team: Should communicate Gitpod releases by picking out a few highlights from the changelog, and adding more context & visuals

Seeding / back-filling the new changelogs

To help kickstart the new changelogs, I'm:

  • going through Gitpod's commit history page by page
  • opening relevant commits, then their linked Pull Request, and optionally their linked issue
  • writing a short one-line summary of relevant PRs from a user's perspective

Here goes (WIP, newest first):

May (unreleased):

April:

March:

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions