Tim Leavitt

The original issue will be resolved with the release of v0.9.0 - split out the thing we found with multiple types as a separate issue.

Closing issues fixed in v1 branch for cleaner bookkeeping.

Discussed today: we need to expand the packages CI workflow to cover all packages, which involves some rearchitecture. I'll file a separate issue for that.

Found more cases of lifecycle class dependency (which motivated the expansion) - there are enough of these, and we don't want to require new releases of the packages involved. Strategy...

Our part in this is done - closing.

Closing issues fixed in v1 branch for cleaner bookkeeping.

This ends up becoming a release blocker because there are a lot of community packages that should be described in this way (the main set of differences between the master...

The v0.9.0 implication here ends up being covered better by #470 - pushing the actual SystemRequirements aspect of this to v1.

@isc-shuliu some guidance here: See %IPM.Storage.SystemRequirements Consider adding integration tests with new package definitions under tests/integration_tests/Test/PM/Integration/_data to cover the use cases. Recommended syntax - see https://github.com/intersystems/ipm/wiki/03.-IPM-Manifest-(Module.xml)#elements : Requires IRIS for...

Closing issues fixed in v1 branch for cleaner bookkeeping.