4 | | If you are submitting a patch for a new feature, keep in mind we only allow new feature patches for semi-major (minor) and major releases, not for micro releases. So for example if the latest stable version of PostGIS is 1.4 or 1.4 is in freeze mode (which usually happens about 2 months or more before planned release), then your new feature must |
5 | | go into 1.5. If you are supplying a bug fix then that can go into the next stable release. So for example a bug fix for 1.4.0 will go into both 1.4.1 and 1.5.0. A bug fix that fixes further back can be provided for 1.3,1.4, and 1.5 |
6 | | |
| 4 | If you are submitting a patch for a new feature, keep in mind we only allow new feature patches for semi-major (minor) and major releases, not for micro releases. So for example if the latest stable version of PostGIS is 3.0.1 and then your new feature must |
| 5 | go into 3.1 (or 3.2 if we've already frozen 3.1 - which happens about 1 month before release). If you are supplying a bug fix then that can go into the next stable release. So for example a bug fix for 3.0.0 will go into both 3.0.1 . A bug fix that fixes further back can be provided for any release not yet End of Lifed - e.g 3.0, 2.5, 2.4 |