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
First of all, really great work here Fabrizio. Thank you very much for that!
We've noticed that this repository currently does not have any release tags. Adding release tags would be highly beneficial for the following reasons as you know yourself:
Versioning
Change Logs
Dependency Management
Improved Update Process
Additional Considerations for Production Use:
We're considering implementing an auto-update mechanism for the module in our production environment, particularly for security-related issues. Here are some points we'd like to address:
Automated Release Monitoring: We plan to automatically watch for new release tags.
Configuration Compatibility: We've noticed that configurations have changed over time. Is backward compatibility maintained between releases? If not, could this be considered for future releases?
Update Process: We're thinking of implementing the following:
Automated update triggering for 'security releases'
Pre-update configuration compatibility checks
Gradual rollout strategy
Rollback mechanism in case of issues
Documentation: Could you provide more detailed information about:
Your approach to backward compatibility
Any specific considerations for production use of the module
Recommended update practices
The module's usability in production environments we think is crucial. We appreciate your work on this module and look forward to your thoughts....
We are here to help with any testing you need. Please only let us know and we are very happy to get hands on...
The text was updated successfully, but these errors were encountered:
First of all, really great work here Fabrizio. Thank you very much for that!
We've noticed that this repository currently does not have any release tags. Adding release tags would be highly beneficial for the following reasons as you know yourself:
Additional Considerations for Production Use:
We're considering implementing an auto-update mechanism for the module in our production environment, particularly for security-related issues. Here are some points we'd like to address:
Automated Release Monitoring: We plan to automatically watch for new release tags.
Configuration Compatibility: We've noticed that configurations have changed over time. Is backward compatibility maintained between releases? If not, could this be considered for future releases?
Update Process: We're thinking of implementing the following:
Documentation: Could you provide more detailed information about:
The module's usability in production environments we think is crucial. We appreciate your work on this module and look forward to your thoughts....
We are here to help with any testing you need. Please only let us know and we are very happy to get hands on...
The text was updated successfully, but these errors were encountered: