hackforla / hackforla/peopledepot

Setup 6-month status releases

Open
#527 1 comment 0 reactions 1 assignee Claimed by @fyliu View on GitHub
complexity: medium feature: build feature: docs: PD team documentation PII: FALSE role: dev lead s: PD team size: 2pt
Dominant language
Python
Stars
14
Forks
37
Avg merge
9d 15h
Merged PRs (30d)
5

Description

### Overview

We need to try out release notes by setting up 6-month dev stage "releases", or progress reports. This will show us what they look like so we can adjust our PR titles if needed, since that's what the release notes use.

### Action Items

- [ ] document how to create a release
- [ ] maybe mention plan for real releases after v0.1.0

### Resources/Instructions

- dev stage release requirements
- We should add tags in order from `v0.0.1` onward, increasing the patch release number.
- We would like to add build metadata so it looks like this `v0.0.1+2021111`
- the metadata is human-readable but not used for the release versioning.

- See [discussion here](https://github.com/hackforla/peopledepot/issues/461#issuecomment-3212390366)
- See [chatgpt log](https://github.com/hackforla/peopledepot/issues/461#issuecomment-3212582460) for more guidelines

- from v0.1.0 onward
- use semantic versioning

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.