Re: Postgres tracking - the pgtrack project
| От | Robert Treat |
|---|---|
| Тема | Re: Postgres tracking - the pgtrack project |
| Дата | |
| Msg-id | 200609021200.59376.xzilla@users.sourceforge.net обсуждение исходный текст |
| Ответ на | Re: Postgres tracking - the pgtrack project (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Postgres tracking - the pgtrack project
|
| Список | pgsql-hackers |
On Saturday 02 September 2006 11:42, Tom Lane wrote:
> BTW, another "output" thing you might consider is "having draft release
> notes ready-to-go on demand". Currently, Bruce prepares the release
> notes on the basis of a very tedious scan of the CVS commit logs.
> If this sort of stuff were being dropped into a tracker as it went
> into the CVS tree, at least the research part of making the notes would
> be zero-effort (or perhaps better to say that the work would be spread
> out instead of concentrated).
FWIW I have never understood why we don't require patch submitters/committers
to update the release notes when they do the patch. I know Bruce says that
it's not a problem for him to do it, but it sure would help out some of the
other folks.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
В списке pgsql-hackers по дате отправления: