-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove support for pre-9.3 #162
Comments
sounds good 👍 |
I suggest posting to the mail list to take the temperature of the community. I've had pretty strong pushback on dropping old versions in the past, but I admit that was years ago. |
If we drop support for 9.0 and earlier, I'd like to suggest we also commit this change:
|
Hello, |
So.... I've got a branch where I've tested 8.1 through 11. 9.0 and older don't work because the travis script can't find appropriate packages. Also, we're unable to test versions older than 9.4 due to issue #212; that build has a work-around that disables extension testing if the extensions don't exist. Based on these results, my thought is to do the following:
I think we should also adopt a formal policy of dropping support for deprecated versions, although in order to do that I think we'll need to be able to support patch releases (issue #210). |
Why do you think we'd need to support patch releases in the version returned from |
I'd like to officially remove support for pre-9.3 versions of Postgres, due to issues in #128. 9.2 went EOL 6 months ago.
https://travis-ci.org/decibel/pgtap/builds/358206497 shows the failures that #128 is getting (I believe #161 explains the version 10 failure). It might be possible to fix the upgrade tests for 9.1 and 9.2, as it appears that the issue is simply some minor changes to output formatting, but I'm not sure it's worth it. Another option would be to simply disable upgrade tests in 9.1 and 9.2 (I'll actually go commit that right now).
9.0 and 8.4 flat-out fail with the changes I've made to
Makefile
. Possibly fixable, but I definitely don't think it's worth the effort for branches that are 2.5 and 3.5 years past their expiration dates.The text was updated successfully, but these errors were encountered: