Skip to content

docs: 📝 describe release process in CONTRIBUTING#161

Open
lwjohnst86 wants to merge 1 commit into
mainfrom
docs/explain-about-release-process
Open

docs: 📝 describe release process in CONTRIBUTING#161
lwjohnst86 wants to merge 1 commit into
mainfrom
docs/explain-about-release-process

Conversation

@lwjohnst86

Copy link
Copy Markdown
Member

Description

This is hopefully a starting point for us to figure out how to work together and how releases should happen.

Needs a thorough review.

Checklist

  • Ran just run-all

@lwjohnst86
lwjohnst86 requested a review from a team as a code owner July 10, 2026 14:19
@lwjohnst86 lwjohnst86 moved this from Todo to In review in Data development Jul 10, 2026
Comment thread CONTRIBUTING.md
especially when there is human data involved and when the data is on secure
servers.

- Because the data is on secure servers, we can't use GitHub workflows. Which

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Because the data is on secure servers, we can't use GitHub workflows. Which
- Because the data is on secure servers, we can't use GitHub workflows. This

Comment thread CONTRIBUTING.md

<!-- TODO: When should a "stable release" be? After all participants go through the first phases? -->

Breaking changes with the `<type>!` format only happens after the first stable

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Breaking changes with the `<type>!` format only happens after the first stable
Breaking changes with the `<type>!` format only happen after the first stable

Comment thread CONTRIBUTING.md
Comment on lines +69 to +71
- Check the commit history since the last release for any releasable changes. If
no releasable changes are found, then no release is created. Otherwise, the
process continues.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if there are no changes in the history but there has been a data / metadata update? We would only find that out in step 3 here.

@github-project-automation github-project-automation Bot moved this from In review to In progress in Data development Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

2 participants