20.2.0
This release aims at making the version 20 of Eclipse SW360 into a stable state. The aim is to bring functionalities to the same parity as they were with version 18.
The Release 20.2.0 can be considered as ready for release when:
- There are no more gaps, functionality wise, between version 18 and 20.
- Core backend business rules and validation logic - such as project state update restrictions and permission boundaries - are fully harmonized with v18 semantics, ensuring consistent behavior and documented rules that remain fixed unless discussed with community leads.
- The release aligns with the SW360 roadmap by delivering a modernized stack that maintains strict functional predictability and governance for enterprise deployments, without introducing unvetted behavioral changes.
Version 20.2.0 reinforces architectural quality by focusing strictly on backend stabilization and semantic parity with version 18. Core business logic, validation pathways, and permission boundaries have been audited and harmonized to prevent undocumented regressions. This release pays down significant "merge debt" accumulated during the v20 modernization path by locking down core rule enforcement. The architecture remains cleanly extensible, ensuring that project state rules and security boundaries cannot be inadvertently altered without community consensus. Unresolved component overlaps are actively tracked and minimized.
- User Documentation: Documentation is undergoing continuous review to reflect the formalized backend rules and stabilized permission boundaries established in this release.
- Localization/Externalization: Translation workflows have been successfully migrated to Weblate, streamlining localization updates and enabling non-technical community contributors.