Issue #12283 has been updated by Shyouhei Urabe.

Status changed from Open to Assigned
Assignee set to Yui NARUSE

----------------------------------------
Misc #12283: Obsolete ChangeLog and commit message in Git-style
https://bugs.ruby-lang.org/issues/12283#change-59159

* Author: Yui NARUSE
* Status: Assigned
* Priority: Normal
* Assignee: Yui NARUSE
----------------------------------------
How about Git-style commit message instead of ChangeLog?

## Proposal

After we reach the consensus

1. Write a commit message in Git-style.

  * Line 1: summary of commit (around 80 characters or less, <50 is better)
  * Line 2: empty line
  * Line 3-: More detailed explanation of commit

See also: https://git-scm.com/book/ch5-2.html#Commit-Guidelines

2. Stop manually edit ChangeLog and auto-generate on `make dist`.

## Rationale

A good commit message should include the objective of the commit.
Committers should write "what purpose the change is for".
In this sense, ChangeLog is not a good format.  It lists per-file changes, so committers tend to write just "how the files were changed".

Also, ChangeLog causes commit conflicts frequently.
Though it is not related with the actual commit.
People who uses svn/git should see the log with it; ChangeLog is only for tarball users.

## Status

mame made this proposal at the developers' meeting (13 Apr.), and there was no objection.

Matz agreed with this proposal, provided that a ChangeLog-like plain-text file is generated from the commit log.
The release manager will create the file when Ruby is released.

### Note

This ticket does NOT propose a migration from SVN to Git.  Never discuss that in this ticket.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>