Tranquil IT Forum

Hello,

I'd like to understand something about package maturity.

I've set the maturity level of a group of computers to DEV to test packages before deployment across the entire network.
I believe that as soon as I set a package to DEV, it should be automatically retrieved by all computers with DEV maturity. However, I've noticed that it must be applied to the OU (Organizational Unit).
In this case, the machines in the OU that don't have DEV maturity can see the package (their status changes to TO UPGRADE), but they can't install the software, which is expected.

Could you please tell me the correct procedure?

Hello Tchoko,

maturity is a way of selecting packages from among several available packages. If you have a package on an OU, it means that all packages must have that package, and therefore you must have the same package in both PROD and DEV environments; otherwise, there will be missing packages—this is by design.

Could you please indicate in the documentation which page is unclear regarding this issue?

Regards,

Denis

Hello,

Actually, the documentation explains how to change the maturity of packages. However, it doesn't specify that the maturity should be changed when applying test packages.

I was able to find the solution to my question using common sense.
When applying to the OU, you need to click on "view more attributes" and choose the maturity on which to apply the updates. See the link below.

Thank

you. I'm marking this as resolved.

Hi Tchoko,

thanks for the feedback.

As with the other post, I've removed the image linking to remote content. Images should be included directly in posts (see forum rules). It's more practical; you can see the image directly. It's also better for security, because you never know what you're clicking on when you go to a Google Drive. And it's better for long-term preservation, since files on Google Drives are constantly being moved.

Regards,

Denis