Communicate IT plans

IT has been discussing how they could improve their processes related to bigger changes in IT-systems. And especially how to avoid problems when changes are done. One example was qt-project.org email server related change. It should have been planned, documented and communicated better. For example roll-back was not possible as person who did changes was on holiday when problems started. Others did not know what was changed and what to rollback.

IT guys said that for some services (like mailman) version control is hard to establish or at least more work. Is that still worth to study...maybe or at least reasons for some other approach should be communicated to R&D. Then everyone knows why some approach was selected.

markopm said that IT should start using Jira for their planning. That would be also channel for at least internal Qt employees to get visibility and also help if they have knowledge of some specific area.

Reason for this ticket: petri.puurunen to communicate these plans is somehow...is it Intra news or Jira user story with sub-tasks that is up to IT to decide. Main thing is that everyone knows how this is improving and also Qt employees can comment and help if they want.