SnoopyIndustries
SnoopyIndustries Recent Posts Threads Started
344 posts
  • Bought between 10 and 49 items
  • Exclusive Author
  • Football Contest Participant/Runner-up
  • Has been a member for 1-2 years
  • Referred between 10 and 49 users
  • Sold between 50 000 and 100 000 dollars
SnoopyIndustries 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!

615 posts
  • Power Elite Author
  • Referred more than 2000 users
  • Power Elite Author: Sold between 2 000 000 - 4 999 999 dollars
  • Austria
  • Bought between 100 and 499 items
  • Has been a member for 5-6 years
+4 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

1027 posts Best-dressed man at PressNomics 2013
  • Attended a Community Meetup
  • Author had a File in an Envato Bundle
  • Bought between 1 and 9 items
  • Contributed a Tutorial to a Tuts+ Site
  • Exclusive Author
  • Has attended an Envato Live event
  • Has been a member for 5-6 years
+5 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.

575 posts Magento Elite & Gravity Maker
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • United States
  • Has been a member for 4-5 years
  • Referred between 50 and 99 users
  • Bought between 1 and 9 items
  • Exclusive Author
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.

1124 posts The Last Man Standing
  • Elite Author
  • Author had a Free File of the Month
  • Has been a member for 3-4 years
  • Referred between 10 and 49 users
  • Exclusive Author
  • Bought between 10 and 49 items
  • Sold between 50 000 and 100 000 dollars
  • Football Contest Participant/Runner-up
+1 more
ImanGM 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

SnoopyIndustries
SnoopyIndustries Recent Posts Threads Started
344 posts
  • Bought between 10 and 49 items
  • Exclusive Author
  • Football Contest Participant/Runner-up
  • Has been a member for 1-2 years
  • Referred between 10 and 49 users
  • Sold between 50 000 and 100 000 dollars
SnoopyIndustries 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

23 posts
  • Football Contest Participant/Runner-up
  • Has been a member for 4-5 years
  • Exclusive Author
  • Sold between 10 000 and 50 000 dollars
  • Bought between 10 and 49 items
  • Referred between 10 and 49 users
  • Germany
jdpowered says

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

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

1081 posts
  • Forum Superstar
  • Most Wanted Bounty Winner
  • Envato Studio (Microlancer) Beta Tester
  • Author had a Free File of the Month
  • Bought between 50 and 99 items
  • Referred between 50 and 99 users
  • Europe
  • Has been a member for 3-4 years
  • Exclusive Author
+1 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