|
| 1 | +# Deprecated Compiler Projects |
| 2 | + |
| 3 | +This directory contains compiler projects that are no longer actively maintained or used in production. These projects have been moved here from the main `compiler/` directory to preserve historical context while keeping the active codebase clean and maintainable. |
| 4 | + |
| 5 | +### Purpose |
| 6 | + |
| 7 | +The `_DEPRECATED` directory serves as a repository for projects that: |
| 8 | +- Have been superseded by newer implementations or alternatives |
| 9 | +- Are no longer supported by the maintenance team |
| 10 | +- Have been archived for historical reference |
| 11 | +- Contain functionality that is no longer required by the project |
| 12 | + |
| 13 | +### Moving Projects to This Directory |
| 14 | + |
| 15 | +A project should be moved to this directory when: |
| 16 | + |
| 17 | +1. **No Active Development**: The project has not received active development or maintenance for an extended period. |
| 18 | +2. **No Active Users**: There are no known users or workflows relying on the project. |
| 19 | +3. **Better Alternatives Exist**: The project's functionality has been replaced by a more suitable alternative in the active codebase. |
| 20 | + |
| 21 | +### Maintenance Policy |
| 22 | + |
| 23 | +Projects in this directory are **not actively maintained**. This means: |
| 24 | + |
| 25 | +- Bug fixes will not be applied |
| 26 | +- New features will not be added |
| 27 | +- Compatibility updates will not be made |
| 28 | +- Documentation will not be updated |
| 29 | +- Security patches will not be provided |
| 30 | + |
| 31 | +### Removal Policy |
| 32 | + |
| 33 | +Projects in this directory may be **permanently removed** from the repository after **one year** from their deprecation date. Note that the code will remain accessible through Git history for reference purposes. |
| 34 | + |
| 35 | +### Accessing Deprecated Projects |
| 36 | + |
| 37 | +Projects in this directory remain in the repository for: |
| 38 | +- Historical reference and audit purposes |
| 39 | +- Potential reactivation if business requirements change |
| 40 | +- Understanding the evolution of the codebase |
| 41 | + |
| 42 | +If you need to use a deprecated project: |
| 43 | +1. **Evaluate Alternatives**: Check if there is a maintained alternative that fulfills your requirements. |
| 44 | +2. **Contact Maintainers**: Discuss with the project maintainers before depending on deprecated code. |
| 45 | +3. **Accept Risks**: Be aware that deprecated projects may have security vulnerabilities, compatibility issues, or lack of support. |
| 46 | + |
| 47 | +### List of Deprecated Projects |
| 48 | + |
| 49 | +This section will be updated as projects are moved to this directory. |
| 50 | + |
| 51 | +| Project | Deprecation Date | Reason | |
| 52 | +|---------|------------------|--------| |
| 53 | +| - | - | - | - | |
0 commit comments