Re: Template for commit messages
От | Joshua D. Drake |
---|---|
Тема | Re: Template for commit messages |
Дата | |
Msg-id | 56AE4807.3070302@commandprompt.com обсуждение исходный текст |
Ответ на | Re: Template for commit messages (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: Template for commit messages
Re: Template for commit messages |
Список | pgsql-hackers |
On 01/29/2016 03:05 PM, Alvaro Herrera wrote: > Joshua D. Drake wrote: > >> I think the best question to ask is: >> >> "What is the problem we are trying to solve?" > > The problem is alluring more patch reviewers, beta testers and bug > reporters. Do we really want patch reviewers, beta testers and bug reporters that are doing it because we created a fixed template for commit messages that may mention their name? > One of the offers is to credit them (I'm not exactly clear > on what is the group to benefit from this, but the phrasing used in the > meeting was "contributors to the release") by having a section somewhere > in the release notes with a list of their names. I can see this as being a nice thing but knowing that someone is a contributor isn't hard. There is a contributor list on the website and it is obvious from mail lists, archives and simple searches who is actually participating. > This proposal is > different from the previous proposal because their names wouldn't appear > next to each feature. That certainly is a good thing. > > So the problem, of course, is collating that list of names, and the > point of having a commit template is to have a single, complete source > of truth from where to extract the info. > I think the problem is that we think that this is somehow going to allure more people. I also think it is a quick step from: Oh, Alvaro helped a lot with that. vs On, 2Q wrote that feature. Any smart business is going to push for that once we start down this path in earnest. Sincerely, Joshua D. Drake -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development.
В списке pgsql-hackers по дате отправления: