On Tue, Jun 19, 2012 at 11:04 AM, Alex Shulgin <a...@commandprompt.com> wrote: > > Dave Page <dp...@pgadmin.org> writes: > >> On Tue, Jun 19, 2012 at 4:43 AM, Robert Haas <robertmh...@gmail.com> wrote: >>> >>> >>> Please add this patch here so that it doesn't get lost in the shuffle: >>> >>> https://commitfest.postgresql.org/action/commitfest_view/open >> >> Hmm, that raises an interesting question (though maybe I've just >> missed this happening in the past). This is a bug fix, that we'll want >> in the next back branch updates, not just 9.3. Sticking it in the open >> commit fest means it may well not get looked at for 2-3 months or so. >> How do we prevent that happening? > > 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). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: 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
