Can we make this bug depend on the currently open 2.6 rc-blocker bugs that
are caused by incompatibilities with postgresql 9.3?
I would rather not let someone install Evergreen on 9.3 when we know it
will silently/subtly fail. After those blocker bugs are merged, then would
be the time to merge this one.
Can we make this bug depend on the currently open 2.6 rc-blocker bugs that
are caused by incompatibilities with postgresql 9.3?
I would rather not let someone install Evergreen on 9.3 when we know it
will silently/subtly fail. After those blocker bugs are merged, then would
be the time to merge this one.