Michael Paquier <michael.paquier@gmail.com> writes:
> Should we consider this bug a 9.5 blocker? I feel uneasy with the fact
> of releasing a new major version knowing that we know some bugs on it,
> and this one is not cool so I have added it in the list of open items.
> We know the problem and there is a patch, so this is definitely
> solvable.
FWIW, general project policy has been that pre-existing bugs are not
release blockers as such. However, if we have a fix in hand that we
would like to get some field testing on, it's certainly desirable to
push it out first in a beta or RC release, rather than having it first
hit the field in stable-branch updates. So we might delay a beta/RC
to make sure such a fix is available for testing. But that's not quite
the same thing as a release blocker. To my mind, a release blocker
is something that would make it undesirable for users to upgrade to
the new release compared to the previous branch, so bugs the branches
have in common are never that.
regards, tom lane