How to acheieve central Patch Management and Life Cycle Management for enterprise customer?

[Swanie75]

Hi, I am doing a pre-study in regards of implementing LibreOffice version 4.3.5 (still) for a rather large company.

One of the dependencies and what I need to be answered is in regards to centrally managed Lifecycle and Patch management for LibreOffice 4.3.5 in a Windows 7 (32-bit, 64-bit) client environment.

For this specific company an internal and central patch management and distribution setup is a requirement and I have not been able to verify how to achieve this without the need of purchasing Patch Management as a service from a third party supplier.

1. How and where are patches (security updates, monthly bug fix releases) located?

2. Is manual patch verification required or can a tool like e.g. WSUS be used in order to collect and import the latest patches and versions centrally before distributing them to the clients?

3. Are all patches released inside the monthly release cycle or can important patches (e.g. security bulletins) be released outside of the release plan cycle?

4. Are patches for Windows clients provided in MSI packages or does each patch or update pack require hands-on configuration before deploying it to the windows clients?

5. Is it possible to use SCCM “Out of the box” as a tool for internal management of patches and version control for LibreOffice?

[ROSt53]

My answer will not be the answers to all of your questions because I cannot answer them.

There is a fixed release plan always updated: https://wiki.documentfoundation.org/ReleasePlan#cite_note-1

I also would try to find out more starting from here: http://www.libreoffice.org/community/get-involved/