Re: No Issue Tracker - Say it Ain't So!
От | Josh Berkus |
---|---|
Тема | Re: No Issue Tracker - Say it Ain't So! |
Дата | |
Msg-id | 568EC148.5080405@agliodbs.com обсуждение исходный текст |
Ответ на | Re: No Issue Tracker - Say it Ain't So! (YUriy Zhuravlev <u.zhuravlev@postgrespro.ru>) |
Ответы |
Re: No Issue Tracker - Say it Ain't So!
|
Список | pgsql-hackers |
On 01/07/2016 10:30 AM, Jeff Janes wrote: > I don't completely agree with that. I have often wanted to know when > a specific item was added to the TODO page, and/or its individual edit > history. With only a unified history of the entire TODO page, and > with no wiki equivalent of "git blame", figuring this out is extremely > tedious. A tracker would precisely solve this problem, if nothing > else. And when I edit the wiki and forget to make a coherent edit > summary, there is no way to fix that, while presumably an issue > tracker would be more tolerant of people's imperfections. Yeah, we could also get rid of this conversation: "Here's a patch for X, which is on the TODO list" "Oh, we've obsolesced that, that was added to the TODO before we had Y" ... by auto-closing TODO items at a certain age. -- Josh Berkus Red Hat OSAS (opinions are my own)
В списке pgsql-hackers по дате отправления: