One maintenance cycle?

Some consultants are stating that it's better to have 1 maintenance cycle per system in solution manager and keep moving the phases back and forward (thus: after go-live the phase is being moved back to "development without release" and from there a new normal correction can start). But can somebody explain to me <b>why</b> this is better than closing a maintenance cycle at the end of a normal correction?

Thanks in advance!