asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Westmann" <ti...@apache.org>
Subject Commit messages (again)
Date Sun, 25 Jun 2017 08:51:55 GMT
Hi,

I’ve been looking at our last 10 commits to find out how we’re doing
wrt to the goal of producing commit messages that will help the release
manager to provide useful release notes.
Out of those commit messages 5 [0,3,5,6,8] looked good, 2 listed no
issue [2,7], 3 [2,7,9] gave no or incomplete information about the
changes we care about (user mode, storage, interfaces), and 2 [1,4]
gave incorrect information in the commit message.

While we’re making good progress, I think that we need to be more
careful when reviewing the commit messages. Ideally, the release
manager should be able to rely on those messages and not have to hunt
through commits (that have been reviewed already) again to find out
what happened.

Please help to get those right.

Cheers,
Till

[0] 
https://github.com/apache/asterixdb/commit/d8536d7a108f03c705a9f82c953f7ae296d394e5
[1] 
https://github.com/apache/asterixdb/commit/63ab05d2a60c5b18bba3e9e4a350a79abfc728f6
[2] 
https://github.com/apache/asterixdb/commit/2138420500a0e4eb917d3e094132037a5c621a56
[3] 
https://github.com/apache/asterixdb/commit/d1d047b5e4d8a097c6b0c9d49058fc4ffe137cf6
[4] 
https://github.com/apache/asterixdb/commit/e0cf970124baed319800d58d107c4bfbe98ae84a
[5] 
https://github.com/apache/asterixdb/commit/a32a852bef6d15f0d99b85d548a99d8ab88b4bba
[6] 
https://github.com/apache/asterixdb/commit/fe00b1af941382c3f47737e9b0d5a9b667365dc7
[7] 
https://github.com/apache/asterixdb/commit/52ca73695ad4d0297341196c768d83404bdb663b
[8] 
https://github.com/apache/asterixdb/commit/198ffbca2eac15d542ea46ea863cebde1fa29138
[9] 
https://github.com/apache/asterixdb/commit/a7fa05bb014503609d1b6287fa08b0a296098088

Mime
View raw message