Managing hot fixes

Question

We are using fixVersion for tracking versions. This is fine. However I would like to know what is the best practice for tracking hot fixes etc. For example we have released version 1.0 and we are currently working on version 2.0. We have discovered a bug in 1.0, so we want to make HotFix on version 1.0. One way would be to create version 1.0.0.1 for first hot fix and so on... but then releases page is overpopulated with versions and there are too many versions. Any ideas how to handle this?

Damjan Music · Answer

Tnx. Stephen

Ste Wright · Answer

Hi @Damjan Music

Honestly, I'd do what you recommended - and have sub-versions alongside the main versions.

If this is crowding your releases page - I'd ensure you are marking them as "Released" - so you can filter for Unreleased versions only, making the page cleaner.

Ste