NEWS file and container-versioning
@phracek is already working on this.
Since Feb 22, 2023.
Assessment
This issue has not been assessed yet.
Description
It would be nice to have some "NEWS" file saying what feature was added
and when. Similar for bugfixes. So far, we never incremented the version of image,
and the image had only the version of the base component (e.g. 9.6, then we
switched to version=1).
- the NEWS file should be available in git root directory
- but also added to
/NEWSpath, so anyone can dodocker run ... cat /NEWS - the version of the container should be printed out by
usage - I'm not sure we need docker tag here
- major version should be incremented if some incompatible change is done
- minor version should be incremented right after release (every 6 weeks so far)
- we should tag git commit before any version change
- Dominant language
- PLpgSQL
- Stars
- 178
- Forks
- 220
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sclorg/postgresql-container
-
Difficulty 2/5 1-2 days Newbie friendliness 72/100
sclorg/postgresql-container#661 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
sclorg/postgresql-container#669 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
sclorg/postgresql-container#668 ·
-
Dockerfile failing Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
sclorg/postgresql-container#656 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
sclorg/postgresql-container#654 ·