Software Lifecycle Policy

Introduction

This Software Lifecycle Policy describes how Tappd manages versions, deprecations, and updates to our platform, APIs, and SDKs. Our goal is to provide transparency and predictability while continuously improving our services.

Version Support

Current Version: We maintain support for the current stable version of our platform, APIs, and SDKs. The current version receives:

• Active development and feature updates
• Security patches and bug fixes
• Performance improvements
• Technical support

Previous Version Support: We typically maintain support for the previous major version for a period of [12 months] after a new major version is released. During this period:

• Critical security patches will be provided
• Critical bug fixes may be provided
• New features will not be added
• Technical support will be available but may be limited

Older Versions: Versions older than the previous major version are considered end-of-life and will not receive updates or support.

Deprecation Notices

When we plan to deprecate a feature, API endpoint, or SDK version, we will:

• Provide at least [90 days] advance notice before deprecation
• Notify you via email, dashboard notifications, and release notes
• Document the deprecation in our changelog and documentation
• Provide migration guides and support resources
• Offer alternative solutions or upgrade paths when available

During the deprecation notice period, the feature will continue to function normally. After the deprecation date, the feature may be removed or disabled.

Breaking Changes

We understand that breaking changes can impact your integration. We follow these guidelines:

• Major Version Releases: Breaking changes are typically introduced in major version releases (e.g., v1.0 → v2.0)
• Advance Notice: We provide at least [90 days] notice before implementing breaking changes
• Documentation: All breaking changes are documented with migration guides
• Backward Compatibility: We maintain backward compatibility within the same major version when possible
• Emergency Changes: In rare cases (security vulnerabilities, legal compliance), we may implement breaking changes with shorter notice

End-of-Life (EOL) Timeline

When a version or feature reaches end-of-life:

• EOL Announcement: We announce the EOL date at least [6 months] in advance
• Support Period: Critical security support may continue for [90 days] after EOL
• Service Continuity: The service may continue to function but without updates or support
• Data Access: You will have access to export your data during the EOL transition period

Migration Support

We provide resources to help you migrate to newer versions:

• Migration guides and documentation
• Code examples and sample implementations
• Support via email and documentation
• Webinars or training sessions for major migrations (when applicable)

While we provide these resources, you are responsible for testing and implementing migrations in your environment.

API Versioning

Our REST APIs use versioning to manage changes:

• Version Format: APIs are versioned as `/api/v1/`, `/api/v2/`, etc.
• Version Support: We maintain support for the current and previous major API version
• Version Selection: You specify the API version in the URL path
• Default Version: Requests without a version may default to the latest stable version

SDK Updates

Our SDKs (Web, iOS, Android) follow semantic versioning:

• Major Versions (X.0.0): May include breaking changes
• Minor Versions (0.X.0): Add new features, backward compatible
• Patch Versions (0.0.X): Bug fixes and security patches
• Update Frequency: We release updates regularly to add features and fix issues
• Update Notifications: Major updates are announced via release notes and changelog

We recommend keeping your SDKs updated to the latest stable version to receive security patches and new features.

Staying Informed

To stay informed about updates and changes:

• Subscribe to our release notes and changelog
• Monitor dashboard notifications
• Follow our documentation updates
• Join our developer community (if available)
• Review email notifications for important changes

Changes to This Policy

We may update this Software Lifecycle Policy from time to time to reflect changes in our practices or services. We will notify you of material changes by posting the updated policy on this page and updating the "Last Updated" date.

Contact Us

If you have questions about our Software Lifecycle Policy or need assistance with migrations, please contact us: