On Tue, Jun 19, 2012 at 6:36 AM, Alex Shulgin <a...@commandprompt.com> wrote: > Dave Page <dp...@pgadmin.org> writes: >> On Tue, Jun 19, 2012 at 11:04 AM, Alex Shulgin <a...@commandprompt.com> >> wrote: >>> >>> In a real bug-tracking system we would create a new bug/ticket and set >>> it's target version to 'candidate for next minor release' or something >>> like that. This way, if we don't release unless all targeted bugs are >>> resolved, this would be taken care of (hopefully.) >> >> Well yes, but the point is that that is not how the project works. I'm >> asking how we do handle this problem at the moment, because I realised >> I haven't seen this happen in the past (largely because I haven't been >> paying attention). > > It only works as long as there is some mechanism to ensure that the bugs > which were not submitted to commitfest are looked at. If there is no, > then it doesn't work actually. > > So is there a real and reliable mechanism for that?
No. There probably should be, but in the meantime adding it to the CommitFest is better than a poke in the eye with a sharp stick. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
