You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mage-OS operates multiple packages, and some of them are located in separate repositories (e.g. mage-os/zend-db and etc...).
Once the bug/changes are required to be added to those repositories - they won't be included in tests run (integration/unit/functional) as the main development repository is locked to released versions of these packages, but not develop versions.
Solution
One of the ideas to solve this problem - run special build process that would pack mage-os dev version with all development/current versions of all packages.
This would mean that all changes added into main branches of package repositories of Mage-OS, but have not been released in tag/version yet, will anyway be included & installed in test build for running various types of tests.
Expected behavior
TBD
Benefits
No response
Additional information
No response
Release note
No response
The text was updated successfully, but these errors were encountered:
Description
Problem
Mage-OS operates multiple packages, and some of them are located in separate repositories (e.g.
mage-os/zend-db
and etc...).Once the bug/changes are required to be added to those repositories - they won't be included in tests run (integration/unit/functional) as the main development repository is locked to released versions of these packages, but not develop versions.
Solution
One of the ideas to solve this problem - run special
build
process that would pack mage-os dev version with all development/current versions of all packages.This would mean that all changes added into main branches of package repositories of Mage-OS, but have not been released in tag/version yet, will anyway be included & installed in test build for running various types of tests.
Expected behavior
TBD
Benefits
No response
Additional information
No response
Release note
No response
The text was updated successfully, but these errors were encountered: