Difference between revisions of "EOL information"
(→Pgpool-II release support policy) |
|||
| Line 27: | Line 27: | ||
|2016/1 | |2016/1 | ||
|2021/1 | |2021/1 | ||
| − | |- | + | |- style="background:silver" |
|3.4 | |3.4 | ||
|2014/11 | |2014/11 | ||
|2019/11 | |2019/11 | ||
| − | |- | + | |- style="background:silver" |
|3.3 | |3.3 | ||
|2013/7 | |2013/7 | ||
|2018/7 | |2018/7 | ||
| − | |- | + | |- style="background:silver" |
|3.2 | |3.2 | ||
|2012/8 | |2012/8 | ||
|2017/8 | |2017/8 | ||
| − | |- | + | |- style="background:silver" |
|3.1 | |3.1 | ||
|2011/9 | |2011/9 | ||
|2016/9 | |2016/9 | ||
|} | |} | ||
Revision as of 09:36, 31 October 2019
Pgpool-II release support policy
The Pgpool-II project aims to fully support a major release for five years. (if you need longer support, please contact to SRA OSS, Inc.).
After a release falls out of full support, we may (at our committers' discretion) continue to apply further critical fixes to the source code, on a best-effort basis. No formal releases or binary packages will be produced by the project, but the updated source code will be available from our source code control system.
This policy will be followed on a best-effort basis. In extreme cases it may not be possible to support a release for the planned lifetime; for example if a serious bug is found that cannot be resolved in a given major version without significant risk to the stability of the code or loss of application compatibility. In such cases, early retirement of a major version may be required.
| Version | First release date | EOL date |
|---|---|---|
| 4.0 | 2018/10 | 2023/10 |
| 3.7 | 2017/11 | 2022/11 |
| 3.6 | 2016/11 | 2021/11 |
| 3.5 | 2016/1 | 2021/1 |
| 3.4 | 2014/11 | 2019/11 |
| 3.3 | 2013/7 | 2018/7 |
| 3.2 | 2012/8 | 2017/8 |
| 3.1 | 2011/9 | 2016/9 |
