Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,475
Community Members
 
Community Events
184
Community Groups

Fix version naming convention for multiple releases in a sprint?

What fix version naming convention do you follow if releasing multiple times a week within a 2 week sprint?

We are moving from monthly release to twice a week and figuring a fix version that won't cause confusion.

We use fix versions to communicate expected release of a feature or bug fix as well as progress.

1 answer

0 votes
Jens Schumacher - Released_so
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 14, 2023

Hi, 

I've seen teams use a number of different conventions. It really depends on your product and preference:

  • Major.Minor.Patch.Build

This is the most common versioning convention.

The major version number is incremented when there are major changes to the software, such as new features or breaking changes.

The minor version number is incremented when there are minor changes to the software, such as bug fixes or performance improvements.

The patch version number is incremented when there are small changes to the software, such as documentation updates or security fixes.

The build number (optional) is incremented for each build of the software, regardless of the changes that were made.

  • YYYYMMDD

This convention uses the year, month, and day of the release. This is a simple and easy-to-understand convention, but it does not provide any information about the changes that were made to the software.

  • YYYYMMDD-Build

This convention combines the year, month, and day of the release with the build number. This provides more information about the changes that were made to the software, but it is still a relatively simple convention. 

  • Sequence 

This convention simply uses sequential numbering for each release. It's simple and easy to follow, but the drawback is that unlike Major.Minor.Patch.Build it doesn't provide any information about the impact of the changes. 

Hope this helps,

Jens

@Jens Schumacher - Released_sothanks for responding

We were using major. minor but mapping that to 8+ releases a month will get tricky. Also thought that dates may get confusing in the event we did not push on a certain day and have to tweak it then.

Anyone hear of using sprint names for fix versions so you know what window the work is planned to be complete?

Jens Schumacher - Released_so
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 21, 2023

@bart no worries. 

You certainly can use sprint names for fix versions. The disadvantage of course is the lack of meaning, specifically if you use the version names publicly. 

Out of interest, what makes the major.minor mapping tricky? Most of the releases will simply increase the minor part of the version number. 

I think for every ticket it would be X.y.1, X.y.2, X.y.3....X.y.8. I can picture devs with 2 weeks worth of work in the sprint not knowing which goes to which

Suggest an answer

Log in or Sign up to answer