You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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.
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:
CHANGELOG.md
file (or multiple files)changelog
label to relevant Pull Requests(Currently being decided.)
Roles / responsibilities:
Seeding / back-filling the new changelogs
To help kickstart the new changelogs, I'm:
Here goes (WIP, newest first):
May (unreleased):
April:
gp
CLI rely onPATH
to look upcode
: Call/ide/bin/code
explicitely instead of relying onPATH
#3846March:
The text was updated successfully, but these errors were encountered: