What's a good practice when managing a small/frequent release process? Edited

[colin.currie]

Hi,

We have recently been aiming to deploy features to production in small and frequent deploys. Ideally one ticket at a time, but due to timing and resource constraints, deploys can include 2 or 3 tickets at a time, depending on what is ready. We work in 2 week sprints and deploy as often as possible.

I wold like to track releases, grouping together the tickets that were deployed at the same time and was intending on using releases for this. It seems to me that releases are aimed at planning larger releases. Are there any good/common practices for our deploy goals? 

Thanks,

Colin.