Github user rdblue commented on the issue:
    Sounds fine to me, then.
    My focus is on the long-term design issues. I still think that the changes 
to make plans immutable and to use the existing push-down code as much as 
possible is the best way to get a reliable 2.3.0, but it is fine if they don't 
make the release.


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to