Appendix A. Release Notes

Table of Contents
A.1. Release 3.7.2
A.2. Release 3.7.1
A.3. Release 3.7
A.4. Release 3.6.9
A.5. Release 3.6.8
A.6. Release 3.6.7
A.7. Release 3.6.6
A.8. Release 3.6.5
A.9. Release 3.6.4
A.10. Release 3.6.3
A.11. Release 3.6.2
A.12. Release 3.6.1
A.13. Release 3.6
A.14. Release 3.5.13
A.15. Release 3.5.12
A.16. Release 3.5.11
A.17. Release 3.5.10
A.18. Release 3.5.9
A.19. Release 3.5.8
A.20. Release 3.5.7
A.21. Release 3.5.6
A.22. Release 3.5.5
A.23. Release 3.4.16
A.24. Release 3.4.15
A.25. Release 3.4.14
A.26. Release 3.4.13
A.27. Release 3.4.12
A.28. Release 3.4.11
A.29. Release 3.4.10
A.30. Release 3.4.9
A.31. Release 3.3.20
A.32. Release 3.3.19
A.33. Release 3.3.18
A.34. Release 3.3.17
A.35. Release 3.3.16
A.36. Release 3.3.15
A.37. Release 3.3.14
A.38. Release 3.3.13
A.39. Release 3.2.22
A.40. Release 3.2.21
A.41. Release 3.2.20
A.42. Release 3.2.19
A.43. Release 3.2.18
A.44. Release 3.1.21

The release notes contain the significant changes in each Pgpool-II release, with major features and migration issues listed at the top. The release notes do not contain changes that affect only a few users or changes that are internal and therefore not user-visible.

A complete list of changes for each release can be obtained by viewing the Git logs for each release. The pgpool-committers email list records all source code changes as well. There is also a web interface that shows changes to specific files.

The name appearing next to each item represents the major developer for that item. Of course all changes involve community discussion and patch review, so each item is truly a community effort.