This release schedule policy, (“Release Schedule Policy”), outlines our approach to releasing updates, including the cadence of releases, notification policies, and emergency patches. It is designed to provide customers with clarity on how and when changes to the Services are deployed. This Release Schedule Policy complements the Service Level Agreement (SLA) and is referenced within it.
1. Release Cadence
We deploy updates on a monthly basis to introduce new features, enhancements, bug fixes, and performance improvements. While we aim to maintain a regular monthly release schedule, the exact timing of releases may vary based on development priorities, testing requirements, and operational needs.
2. Notification Policy
Planned Releases
Notification Period: Customers will receive at least 3 Business Days’ notice prior to a planned release.
Details Provided:
Summary of changes or updates.
Expected impact on service availability (if any).
Any actions required from customers.
Emergency Patches
Purpose: Emergency patches are deployed outside of the regular release cadence to address critical issues such as security vulnerabilities, high-severity bugs, or urgent performance risks.
Notification Period: Customers will be notified as soon as possible prior to deployment, depending on the urgency of the issue.
Maintenance Windows
Scheduled downtime for maintenance will be communicated with at least 48 hours’ notice. Maintenance is typically scheduled during off-peak hours to minimize disruption.
3. Release Process Overview
Development Phase:
Updates are developed and rigorously tested internally to ensure quality and reliability.
Pre-Release Notification:
Customers are informed via email or through the status page of the Services about upcoming releases.
Deployment Phase:
Updates are deployed during low-traffic periods to minimize service interruptions.
Post-Release Communication:
Release notes are shared with customers detailing new features, fixes, and any other relevant information.
4. Emergency Patches
Emergency patches may be deployed at any time outside of planned release schedules to address critical issues. These patches are prioritized based on severity and impact and may result in temporary service interruptions. We will make every effort to notify customers promptly before deployment.
5. Customer Responsibilities
To ensure smooth transitions during releases:
Review release announcements promptly upon receipt.
Prepare for any required actions outlined in the notification (e.g., testing new features).
Report any issues encountered post-release to support@letsflo.co.
6. Updates to This Policy
We may update this Release Schedule Policy periodically to reflect changes in our release process or business needs. Customers will be notified of any updates via email or through the status page of the Services.
7. Contact Information
For questions about this Service Credit Policy or to request service credits, please contact Lets Flo Support at support@letsflo.co.
8. Flexibility Clause
While we aim to deploy updates monthly, exact dates may vary depending on internal priorities or unforeseen circumstances. Customers will always receive advance notice of confirmed deployment dates.