32 lines
1.6 KiB
Markdown
32 lines
1.6 KiB
Markdown
# WP Allstars Plugin Stability Status
|
|
|
|
This document tracks the stability status of different versions of the WP Allstars Plugin.
|
|
|
|
## Stability Classification
|
|
|
|
- **[STABLE]**: Thoroughly tested, works as expected in production environments
|
|
- **[FUNCTIONAL]**: Works but may have minor issues or incomplete features
|
|
- **[EXPERIMENTAL]**: Contains new features that are not fully tested
|
|
- **[UNSTABLE]**: Known to have critical issues that affect functionality
|
|
|
|
## Version Status
|
|
|
|
| Version | Status | Notes |
|
|
|---------|--------|-------|
|
|
| v0.2.3-stable-base | **[STABLE]** | Base stable version with robust file loading. All core functionality works properly. |
|
|
| v0.2.4 | **[UNSTABLE]** | Contains critical errors - reference only for feature ideas. |
|
|
| v0.2.6 | **[UNSTABLE]** | Contains file structure issues and critical errors - reference only for feature ideas. |
|
|
| v0.2.6-fix | **[UNSTABLE]** | Attempted fixes but still has issues - reference only. |
|
|
| v0.2.6-revert | **[UNSTABLE]** | Failed attempt to revert to stable version - do not use. |
|
|
|
|
## Current Development
|
|
|
|
Current development is based on the v0.2.3-stable-base version. Features from later versions are being analyzed and reimplemented in a stable manner.
|
|
|
|
## Stability Guidelines
|
|
|
|
1. All new features must be developed in isolated feature branches
|
|
2. Comprehensive testing is required before merging
|
|
3. Each feature should be implemented as a series of small, atomic commits
|
|
4. All commits should include a stability classification in commit messages: [STABLE], [FUNCTIONAL], etc.
|
|
5. Full testing checklist must be completed before marking a version as [STABLE] |