415 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Had an item that was trending
  • Has sold $75,000+ on Envato Market and is now an Elite Author
  • Sells items exclusively on Envato Market
+4 more
BigBangThemes
says

Hi guys,

I’ve been trying to figure out how to get more organized with the names of item updates and I was curious how some of you do it.

I’ve seen that some stick to 1.0,2.0,etc but I’ve also seen that some use things like 1.2.3.1.15 :)) i’m just trying to get a bit more organized so any tip would help!

640 posts
  • Has referred more than 5000 members
  • Has sold $5M+ on Envato Market
  • Has collected 100+ items on Envato Market
  • Had an item featured in a magazine
+12 more
Kriesi
says

I usually use 1.0, 1.1, 1.2 etc when I add new features and 1.0.1, 1.0.2 etc for bugfixes

1088 posts Best-dressed man at PressNomics 2013
  • Became a Top 20 Author of the Month
  • Had an item that was trending
  • Has sold $1M+ on Envato Market and is now a Power Elite Author
  • Power Elite Author: Sold more than $1M on Envato Market
+12 more
Parallelus
says

I usually use 1.0, 1.1, 1.2 etc when I add new features and 1.0.1, 1.0.2 etc for bugfixes

We do the same.

782 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 5 years
+4 more
GravityDept
says

I use X.Y.Z also, except bug fixes always get rolled into a Z release and Y releases usually only happen when Z rolls over. X releases are complete rewrites (i.e. probably not able to migrate easily without starting over). See my item’s changelog in its demo for an example.

1867 posts The Last Man Standing
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Has been a beta tester for an Envato feature
  • Helped several times protecting Envato Market against copyright violations
+9 more
ImanGM
Moderator
says

I usually use 1.0, 1.1, 1.2 etc when I add new features and 1.0.1, 1.0.2 etc for bugfixes

I do the same too! But when I have both new features and bug fixes, I’ll ignore the third part :D

415 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Had an item that was trending
  • Has sold $75,000+ on Envato Market and is now an Elite Author
  • Sells items exclusively on Envato Market
+4 more
BigBangThemes
says

Thanks so much guys, the advice is golden, especially from authors as highly regarded. Thanks for taking the time to answer this. I’ll probably adapt the same method because it’s sounds much more organized and well thought than what I have now.

Cheers

44 posts
  • Made it to the Authors' Hall of Fame
  • Sells items exclusively on Envato Market
  • Has been part of the Envato Community for over 5 years
  • Has sold $10,000+ on Envato Market
+5 more
jdpowered
says

Also, be sure to have a look at semver.org.

It’s a nice guideline on versioning software. :)

1356 posts
  • Has been part of the Envato Community for over 4 years
  • Has sold $40,000+ on Envato Market
  • Has been a beta tester for an Envato feature
  • Has collected 50+ items on Envato Market
+4 more
Smartik
says

1.x- major update, critical bug fixes, new features.
1.x.x – small update, simple bug fixes.
from 1.x to 2.x – again, a major update but here we talk about a really big update, bug fixes, new features, code review, etc.

by
by
by
by
by
by