I've managed to clean up all but one of the open items[1] attributable
to my v10 commits; the exception is the issue with pg_dump and
partitioned tables, which I still hope to get resolved this week.
On Friday, I'm leaving on vacation; my first day back in the office
will be April 24th. While I expect to check email, including
pgsql-hackers, periodically while on vacation, my ability to spend
serious time addressing open items will obviously be reduced.
Therefore, I'd like to request that the RMT accept the following
blanket status update for open items attributable to my commits which
arise after April 13th: "I will begin investigating this no later than
April 24th, my first day back from vacation, and will provide a
further update by that same day."
Most of my close colleagues at EnterpriseDB will be in the office
during this time, and I have asked the people with whom I work closely
to follow up on items related to their own commits and, even, where
possible, other open items with my name on them. However, as none of
those individuals are committers[2], they will not be able to do more
than propose patches and review those proposed by others. It would be
great if other committers are able to help out with committing any
unintimidating patches which may be proposed.
I apologize for any disruption this may cause, but I'm hopeful that it
won't be too bad.
Thanks,
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
[1] https://wiki.postgresql.org/wiki/PostgreSQL_10_Open_Items
[2] Something which I hope will change at an appropriate point in time.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
