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

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

Closed
jankeromnes opened this issue May 10, 2021 · 2 comments
Assignees
Labels
feature: documentation meta: stale This issue/PR is stale and will be closed soon

Comments

@jankeromnes
Copy link
Contributor

jankeromnes commented May 10, 2021

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:

@jankeromnes jankeromnes changed the title Seed Changelog v2 with exciting / user-visible changes from the March / April / May cycles Seed Changelog v2 with exciting / user-visible changes from the April / May cycles May 10, 2021
@stale
Copy link

stale bot commented Aug 8, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Aug 8, 2021
@gtsiolis
Copy link
Contributor

gtsiolis commented Aug 9, 2021

Closing this, feel free to reopen if this is still relevant. Cc @jankeromnes @mikenikles

@gtsiolis gtsiolis closed this as completed Aug 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: documentation meta: stale This issue/PR is stale and will be closed soon
Projects
None yet
Development

No branches or pull requests

3 participants