-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Extensions testing against Solidus versions that have reached EOL #2866
Comments
No. Although we have a rule of supporting as much as Solidus versions as possible, the amount of resources we are burning alone is reason to not to. It does not make any sense to do not support the Solidus version of it, but still test the extension for it. |
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Pretty sure I made PRs to all of the Solidus Extensions from http://extensions.solidus.io/ that are still running against EOL versions. I'll leave the issue open for now in case there is more discussion. |
If we stop testing against EOL versions as a rule, should this toggle on http://extensions.solidus.io/ go away? |
Testing versions of Solidus that have reached EOL is a misuse of resources and should be avoided. The extension documentation should reflect the practice of only testing versions that are currently supported. Refs solidusio#2866
Yes. Very good catch |
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
Refs solidusio/solidus#2866 (comment) There is no reason to invest resources in testing extensions against Solidus versions that have passed EOL. [Solidus Version Maintenance/EOL policy](https://solidus.io/blog/2018/01/04/maintenance-eol-policy.html)
I would like to get some discussion on this:
I recently added a new Solidus versions to TravisCI in bunch of Solidus extensions. I noticed that some extensions have .travis.yml files that list a ton of Solidus versions which have now reach EOL.
(from solidus_i18n)
This kind of thing causes tests to take a lot longer, and in some cases when CI hangs, tests can take a really long time.
Should we only be testing extensions against versions that haven't reached EOL?
The text was updated successfully, but these errors were encountered: