You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 2, 2019. It is now read-only.
So I was thinking we may have some issues in the future if a third-party user decides to patch tollgate, and they introduce regressions, it would be helpful to track these down.
My solution to this is the "support" information dump.
It should dump hashes of all the project files, template locations, etc. and put it into a nice format we can use.
This can also help to identify when customisations have been made to tollgate that haven't made it upstream yet.
The other issue that I can see happening is if someone decides to patch tollgate, and one of their users starts reporting bugs in their version to us. :\
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So I was thinking we may have some issues in the future if a third-party user decides to patch tollgate, and they introduce regressions, it would be helpful to track these down.
My solution to this is the "support" information dump.
It should dump hashes of all the project files, template locations, etc. and put it into a nice format we can use.
This can also help to identify when customisations have been made to tollgate that haven't made it upstream yet.
The other issue that I can see happening is if someone decides to patch tollgate, and one of their users starts reporting bugs in their version to us. :\
The text was updated successfully, but these errors were encountered: