As we move toward EOL we will need to sort out how we handle dependencies. Currently they are hard coded to specific versions and if security releases occur that would break EOL. I would like to pose that we move away from hardcoded versioning and describe the versions of dependencies that are still working.
This may require some method to test the tool in a more automated way as well.
As we move toward EOL we will need to sort out how we handle dependencies. Currently they are hard coded to specific versions and if security releases occur that would break EOL. I would like to pose that we move away from hardcoded versioning and describe the versions of dependencies that are still working.
This may require some method to test the tool in a more automated way as well.