Re: No Issue Tracker - Say it Ain't So!
От | Joe Conway |
---|---|
Тема | Re: No Issue Tracker - Say it Ain't So! |
Дата | |
Msg-id | 5603525A.4050407@joeconway.com обсуждение исходный текст |
Ответ на | Re: No Issue Tracker - Say it Ain't So! (Thomas Munro <thomas.munro@enterprisedb.com>) |
Ответы |
Re: No Issue Tracker - Say it Ain't So!
|
Список | pgsql-hackers |
On 09/23/2015 05:21 PM, Thomas Munro wrote: > Do you think it would make any sense to consider evolving what we have > already? At the moment, we have a bug form, and when you submit it it > does this (if I'm looking at the right thing, please correct me if I'm > not): > > http://git.postgresql.org/gitweb/?p=pgweb.git;a=blob;f=pgweb/misc/views.py > > That is, the database interaction is limited to using a SEQUENCE to > generate a new bug ID, and then an email is sent to pgsql-bugs. What > if we also created a bug record for that ID to track its status, and > allowed anyone with a community account to edit the bug record and > change the status? There could be a simple page that lets you see and > search for bugs, with a link to the flat mail archive thread where > discussion is held. All actual discussion would continue on mailing > lists. That would be similar to the commitfest. > > I suppose some forms of cross-reference would also be useful: when > viewing the bug's page, you might want to see any commitfest items or > pgsql-committers messages that relate to that bug. Perhaps we could > automatically create those links when bug IDs are recognised in those > messages, so that no extra workflow/maintenance is required in It would be nice if you could essentially promote a bug into a commitfest item, maybe through a status change. > straightforward cases. To continue that line of thinking it would > also be possible for bug statuses to be changed when certain words are > spotted in either commit messages (which doesn't have to be a commit > hook, it could be taken from pgsql-committers messages) or pgsql-bugs > messages. > > Cf github commit message parsing: > https://help.github.com/articles/closing-issues-via-commit-messages/ I was thinking along the same lines. If we could paste a bug reference number into the commit message and have that change the bug status it would go a long way to making this workable I think. Joe -- Crunchy Data - http://crunchydata.com PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development
В списке pgsql-hackers по дате отправления: