Re: Maintaining the list of release changes
От | Peter Eisentraut |
---|---|
Тема | Re: Maintaining the list of release changes |
Дата | |
Msg-id | Pine.LNX.4.30.0202112318500.1903-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Re: Maintaining the list of release changes (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Maintaining the list of release changes
|
Список | pgsql-hackers |
Tom Lane writes: > That's a valid complaint against CVS-log-based notes, since most people > probably don't have or know how to use tools like cvs2cl. I don't see > why it's an argument against my idea of a dedicated text file, though. > Such a file would be just as readily found as release.sgml, possibly > more so. Do you have a suggestion for a name and where to put the file. Will it be removed or cleared before releases? > I am still concerned about the prospect of either release.sgml or > a dedicated file becoming commit bottlenecks because everyone is > constantly hitting them (and in approximately the same place, too). There are lots of and big projects that use GNU-style ChangeLogs. Theoretically, they would all hit at the same place, but in practice this is never a problem. When an outsider submits a patch he just puts the changelog entry into a separate attachment or right into the message and the committer puts it into the right place. We can make this to work as well. If someone comes along, "hey, I just added a --foo option to pg_bar to do xyx", the patch committer simply adds a line "added --foo option to pg_bar to do xyz" to the log. All the release note items are one-liners, so this can't be too big of a deal. -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-hackers по дате отправления: