Patch Updates Best Practices

Following these best practices will help you maximize the benefits of Patch Updates.

Release Strategy

Keep Releases Frequent

Keep your releases frequent to maximize patch efficiency. Smaller, incremental changes result in smaller patches.

Example: Instead of bundling multiple features into one large release, release features incrementally. Each release will generate a smaller, more efficient patch.

Maintain Consecutive Versions

Ensure your version numbers are consecutive for optimal patching. Patches are generated between consecutive versions, so maintaining consecutive version numbers ensures the best patch efficiency.

Monitoring

Monitor Patch Metrics

Use the Stallion Console to monitor patch sizes and the breakdown of patch vs full bundle downloads. Check metrics after each release to track efficiency.

Track Patch Efficiency

Monitor patch sizes and reduction percentages to ensure optimal efficiency. Aim for 90-98% reduction.

Testing

Test patch updates in your staging environment before promoting to production, just as you would with full bundle updates:

• Always test patches in staging first
• Ensure patches don't introduce regressions
• Verify patch performance matches expectations

Common Pitfalls to Avoid

Avoid Large Breaking Changes

Don't: Make large breaking changes that require full bundle downloads.

Do: Break large changes into smaller, incremental updates that can be patched.

Avoid Infrequent Releases

Don't: Bundle many changes into infrequent, large releases.

Do: Release frequently with smaller, incremental changes.

Conclusion

Following these best practices will help you maximize the benefits of Patch Updates:

• Keep releases frequent and incremental
• Monitor patch efficiency regularly
• Maintain consecutive version numbers
• Test patches before production

By following these practices, you'll get the most out of Patch Updates and deliver the best possible update experience to your users.

Learn how to monitor Patch Updates or get started.