Are you mirroring the Zimbra repo's internally Mark? Then you can clearly see which packages are updated.
Additionally, we always peek inside the *-patch packages (rpm -q --scripts) and diff the contents to get an idea of the changes (besides watching github). Here it was clearly visible that only a single zm-store jar was being updated. In that case we don't even install the zimbra-patch package, we just push that one file (or files) via ansible, and restart mailboxd.
For larger / more complex patches, we often cherry-pick critical fixes in the same way (XSS fixes, postjournal, ...), and install the full patches at a much slower cadence.
Additionally, we always peek inside the *-patch packages (rpm -q --scripts) and diff the contents to get an idea of the changes (besides watching github). Here it was clearly visible that only a single zm-store jar was being updated. In that case we don't even install the zimbra-patch package, we just push that one file (or files) via ansible, and restart mailboxd.
For larger / more complex patches, we often cherry-pick critical fixes in the same way (XSS fixes, postjournal, ...), and install the full patches at a much slower cadence.
Statistics: Posted by ghen — Wed Oct 09, 2024 5:44 pm
