pgpool-II 3.6 development
Last update: 2016/3/7 (gray items are done, yellow items are behind schedule)
| ID | Registered/start Date | Target Date | Person in charge | Overview | Status | |
|---|---|---|---|---|---|---|
| 1 | pgpool-general:3907 | 2015/08/02 | 2015/10/28 | Usama | watchdog info | Done in [pgpool-general: 4452] |
| 2 | pgpool-general:3923 | 2015/08/06 | - | Tatsuo | pgpool_status | needs discussion, postpone to 3.6 |
| 3 | pgpool-hackers:994 | 2015/08/05 | - | Tatsuo | connect to necessary DB nodes | proposal, feedback, postpone to 3.6 |
| 4 | pgpool:330 | 2015/08/12 | - | Ahsan, Tatsuo | mesuring pgpool-II overhead | in progress, Tatsuo will review the result, postpone to 3.6 |
| 5 | pgpool-hackers:1034 | 2015/09/03 | - | - | add new child if it goes down | need to assign, postpone to 3.6 |
| 6 | pgpool-general:4016 | 2015/09/02 | - | - | deal with pg_terminate_backend | need to assign or expecting patches from user, postpone to 3.6 |
| 7 | Import PostgreSQL 9.6 parser | 2016/2/15 | - | - | - | Start after PostgreSQL 9.6 beta released |
| 8 | Add SET command | 2016/2/15 | - | Usama | - | Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly. |
| 9-1 | Convert the pgpool documentation to SGML | 2016/2/15 | 2016/2/15 | Usama | Tool set porting work time estimate | Estimating work hours to determine the shedule. He estimated as "3.5D". |
| 9-2 | Convert the pgpool documentation to SGML | 2016/2/16 | 2016/2/19 | Usama | Tool set porting | PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files |
| 9-3 | Convert the pgpool documentation to SGML | 2016/2/26 | 2016/2/29 | Tatsuo | Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs | |
| 10 | Make PCP set configuration command public | 2016/2/15 | - | Usama | - | |
| 11 | Keep current session alive in-case of failover | 2016/2/15 | 2016/3/31 | Tatsuo | http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html | |
| 12 | Yet another stuck connection problem | 2016/2/19 | 2016/2/23 | Usama | pgpool-general: 4457 | |
| 13 | Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS | 2016/2/26 | Usama | |||
| 14 | Allow to use multiple pgpool-II instances with in-memory query cache enabled | 2016/3/4 | http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery | |||
| 15 | Health-check timeout for each backend node | 2016/3/4 | http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node | |||
| 16 | Worker Processes Exit and Are Not Re-spawned | 2016/3/7 | Usama | http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html | ||
| 100 | Platform freeze | 2016/2/19 | 2016/3/15 | - | - | All the new platforms that we want to support and add to BF should be decided by this date. |
| 101 | Feature requirement freeze | 2016/2/19 | 2016/3/15 | - | - | We need to ensure all the features that we intend to add to 3.6 are speced out by this date |
| 102 | Feature Freeze | 2016/2/19 | 2016/7/30 | - | - | Ensure all the agreed upon features are committed to master by this date. This should be feature complete and we should only focus on bug fixed after this point. |
| 103 | Code Freeze | 2016/2/19 | 2016/8/31 | - | - | At-least one month period between feature and code freeze to ensure all new features are stable and critical bugs are fixed by this date. |
| 104 | pgpool-II 3.6 beta1 | 2016/2/19 | 2016/8/31 | - | - | First Beta |
| 105 | pgpool-II 3.6 RC1 | 2016/2/19 | 2016/9/30 | - | - | One month after beta1 |
| 106 | pgpool-II 3.6.0 official release | 2016/2/19 | 2016/10/30 | - | - |
