A master suite that runs on Fedora will help us to detect bugs on the next Centos.
Don't you think this better be an epic rather then a plain ticket?
Let's add subtasks, if we see that this ticket become unmanageable we can split it.
Do you really think a ticket this broad will be completed within a "sprint' (2-3 weeks) ?
subtasks are OK, but we recently learned we've been using it wrong most of the time.
The usage of sub-tasks is mostly to split the work between multiple team members, while the use of Epics is to track work that spans between multiple tickets.
So I'd say, let's try to follow that and see how it goes ( we might need to drop all existing Epics we've been using and replace them with the proper labels though ).
This should be an Epic which links multiple sub-tickets ( user stories ) that each one of those should be able to fit in one sprint.