Releases

Release policy and versioning overview.

Versioning Scheme

UNA CMS follows a structured versioning scheme that helps users understand the nature and significance of each release. The versioning format follows this pattern:

MAJOR.MINOR.PATCH-STAGE

Version Components

MAJOR: Incremented for significant changes that may include architectural modifications and major feature additions.
MINOR: Incremented for new features, improvements and minor functionality updates.
PATCH: Incremented for bug fixes, security updates and minor improvements
STAGE: Indicates the development stage of the release

Development Stages

UNA CMS releases progress through several development stages before reaching a stable release:

Alpha (A) - Early development stage with core functionality implemented but potentially unstable
- Example: 14.0.0-A1, 14.0.0-A2, 14.0.0-A3
- Alpha releases may contain experimental features and are primarily for testing purposes
- Not recommended for production environments
Beta (B) - More stable than Alpha with most features implemented
- Example: 14.0.0-B1, 14.0.0-B2
- Beta releases undergo more extensive testing but may still contain bugs
- Can be used in non-critical production environments with caution
Release Candidate (RC) - Feature-complete and approaching stable release
- Example: 14.0.0-RC1, 14.0.0-RC2, 14.0.0-RC3
- RC releases focus on bug fixing and polishing
- Generally stable enough for most production environments
Stable - Final release version without a stage suffix
- Example: 14.0.0
- Thoroughly tested and suitable for all production environments
- Receives only critical bug fixes until the next release

Release Cycle

UNA CMS follows a predictable release cycle that balances innovation with stability:

Feature Releases

Major and minor version updates (e.g., from 13.x to 14.x or from 14.0 to 14.1)
Typically released every 4-6 months
Include new features, enhancements, and architectural improvements
Follow the development stage progression (Alpha → Beta → Release Candidate → Stable)

Service Updates

Patch version updates (e.g., from 14.0.0 to 14.0.1)
Released as needed, typically every 2-4 weeks
Focus on bug fixes, security patches, and minor improvements
May skip some development stages for critical fixes

Development Timeline

A typical major version release follows this approximate timeline:

Alpha Phase: 1-2 months with multiple alpha releases (A1, A2, A3)
Beta Phase: 1-2 months with multiple beta releases (B1, B2)
Release Candidate Phase: 1-2 months with multiple RC releases (RC1, RC2, RC3)
Stable Release: Final version released after successful RC testing

Update Channels

UNA CMS provides different update channels to give users control over the stability and frequency of updates:

Stable Channel

Default update channel for all UNA installations
Receives only thoroughly tested stable releases
Recommended for production environments
Updates are less frequent but more reliable

Beta Channel

Optional update channel for early access to new features
Receives beta and release candidate versions before they reach the stable channel
Suitable for testing environments or non-critical production sites
Updates are more frequent but may contain occasional bugs

Changing Update Channels

You can change the update channel in one of two ways:

Via Studio: Navigate to Studio > Developer > Settings > Update channel
Via SQL: If the Developer module isn't installed, run the following SQL query:
```
UPDATE `sys_options` SET `value` = 'beta' WHERE `name` = 'sys_upgrade_channel';
```
Then clear the DB cache in Studio > Dashboard > Cache block.

Update Methods

UNA CMS offers two primary methods for applying updates:

Automatic Updates

Enabled by default
System checks for updates every 24 hours
Updates are applied automatically when available
Can be enabled/disabled in Studio > Settings > System > Site Settings > Enable auto-update

Manual Updates

Go to Studio > Dashboard and click/tap Upgrade
After system update, go to Studio > Apps Market > Updates and apply all available module updates
Reload the page and apply any remaining updates until none are available
Repeat for each system update

Development Releases

UNA CMS makes development releases (Alpha, Beta, RC) available to users who want early access to new features or wish to participate in testing:

Benefits of Development Releases

Early access to new features and improvements
Opportunity to provide feedback that may influence the final release
More frequent updates and fixes

Cautions for Development Releases

May contain bugs or incomplete features
Potential for data migration issues when upgrading
Not recommended for critical production environments
May require more frequent updates

Best Practices for Using Development Releases

Testing Environment: Always use development releases in a testing environment first
Backup: Create complete backups before installing or upgrading to development releases
Feedback: Report any issues or bugs to help improve the final stable release
Upgrade Path: Be prepared to follow the full upgrade path through subsequent development releases

Conclusion

Understanding UNA CMS's versioning scheme and release process helps you make informed decisions about when and how to update your installation. By choosing the appropriate update channel and being aware of the development stages, you can balance access to new features with the stability requirements of your specific environment.

For critical production environments, it's recommended to:

Use the stable update channel
Wait for stable releases rather than development releases
Test updates in a staging environment before applying to production
Always maintain current backups before performing any updates

For development or testing environments, you might prefer:

Using the beta update channel
Accessing new features through development releases
Participating in the testing and feedback process
Updating more frequently to stay current with the latest changes

2025-04-14T11:31:14+0000