Opened 8 years ago
Closed 7 years ago
#778 closed task (fixed)
Generate ChangeLog from git log
Reported by: | strk | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 3.7.0 |
Component: | Default | Version: | 3.5.0 |
Severity: | Unassigned | Keywords: | git |
Cc: | mloskot |
Description
A git2cl tool exists and is packaged on debian, but as the current ChangeLog format includes revision numbers we'll need to drop that information for the new ChangeLog (no revision numbers in a git-only repo).
One possibility here is to save the old ChangeLog files into a subdirectory (doc/changelog?) and start with a fresh one starting from where the old one ends.
Another is to STOP checking the ChangeLog into the repository but always only generate it at "make dist" time, which may be a bit tricky to pass "make distcheck" (as it sets the sources read-only) but may set us free from future management issues.
This is propedeutic for moving the codebase from SVN to git.
Change History (15)
comment:1 by , 8 years ago
Version: | → 3.5.0 |
---|
comment:4 by , 8 years ago
comment:5 by , 8 years ago
comment:6 by , 8 years ago
No revision numbers, is my proposal. Autogenerated ChangeLog in the release tarball. Manually edited NEWS (by maintainer-or-committer).
comment:10 by , 7 years ago
Food for thoughts: https://lists.gnu.org/archive/html/bug-mcron/2015-09/msg00008.html
comment:11 by , 7 years ago
comment:15 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I think this can be considered closed now
Another possibility is to stop replicating VCS log in the ChangeLog and not to include any revision info.
Typically, ChangeLog is written, by humans for humans, as a chronologically ordered list of notable changes for each version of a project, but not all changes/revisions checked in to the repo. I like http://keepachangelog.com/