Java-Gaming.org    
Featured games (81)
games approved by the League of Dukes
Games in Showcase (489)
Games in Android Showcase (112)
games submitted by our members
Games in WIP (554)
games currently in development
News: Read the Java Gaming Resources, or peek at the official Java tutorials
 
    Home     Help   Search   Login   Register   
Pages: [1]
  ignore  |  Print  
  How do you guys name builds, betas, etc.  (Read 1250 times)
0 Members and 1 Guest are viewing this topic.
Offline Jacob Pickens
« Posted 2014-02-27 22:23:08 »

I usually name everything as 1.0 etc. So I'd have Pre-Alpha 1.0 and Beta 9.0 and stuff but i know that isnt correct. So how does Minecraft and all the other companies name their builds and stuff?
Offline Varkas
« Reply #1 - Posted 2014-02-27 22:31:31 »

Either I go with major.minor.patch, e.g. 1.83.2 or just count releases, e.g. r105 or v46

Lately I just count, because none of my projects are sophisticated enough to need a complex versioning scheme.

if (error) throw new Brick(); // Blog (german): http://gedankenweber.wordpress.com
Offline Jacob Pickens
« Reply #2 - Posted 2014-02-27 22:33:12 »

Thanx Varkas, +1
Games published by our own members! Check 'em out!
Legends of Yore - The Casual Retro Roguelike
Offline kingroka123

JGO Knight


Medals: 29
Projects: 5
Exp: 1 year


Gamer's Helmet


« Reply #3 - Posted 2014-02-27 22:34:33 »

What I do is count each major release and add a decimal each minor release. So a main release could be 2 but the next realese could be 2.1 because I just fixed some minor bugs or something.

Offline Jacob Pickens
« Reply #4 - Posted 2014-02-27 22:41:32 »

Thats currently what im doing now. I guess my method isnt that wrong after all!
Offline Rayvolution

JGO Kernel


Medals: 186
Projects: 2
Exp: 1 year


Resident Crazyman


« Reply #5 - Posted 2014-02-27 22:53:04 »

For me, I break the mold and do it all by build date. Whatever the date is when I compile it for release is the "version number". If I release 2 copies in the same day, the second becomes a B copy (IE: InDev-2-27-2014b)

Assuming we use today's date..

While the game is in pre-alpha, and really not a playable game yet:
InDev-2-27-2014

Once in Alpha (Meaning there are some functional, actual game play elements at this point and the game is starting to actually become a "game")
Alpha-2-27-2014

Beta (majority of the core mechanics are completed, just lacking content):
Beta-2-27-2014

...and Release, I just call them "Builds".
Build-2-27-2014

- Raymond "Rayvolution" Doerr.
Retro-Pixel Castles - Survival Sim/Builder/Roguelike!
LIVE-STREAMING DEVELOPMENT: http://www.twitch.tv/SG_Rayvolution
Offline Jacob Pickens
« Reply #6 - Posted 2014-02-27 22:57:28 »

I like the way that looks... Maybe i just have a number fetish idk, but i think i might use your way of doing things it looks nice!
Offline opiop65

JGO Kernel


Medals: 154
Projects: 7
Exp: 3 years


JumpButton Studios


« Reply #7 - Posted 2014-02-27 22:58:36 »

I personally find that very ugly to look at. Sure, its a decent way to label your builds, but it's A2.1 or B0.1 or something much simpler to read? A - Alpha, number for the version.

Offline Rayvolution

JGO Kernel


Medals: 186
Projects: 2
Exp: 1 year


Resident Crazyman


« Reply #8 - Posted 2014-02-27 23:44:51 »

I personally find that very ugly to look at. Sure, its a decent way to label your builds, but it's A2.1 or B0.1 or something much simpler to read? A - Alpha, number for the version.

I agree, it can look messy sometimes. But it's a much better option than having something like V3.352.22b2 eventually. Of course, on smaller scales that will never happen really. But I've seem some wild patch numbers in some of the bigger budget titles out there Cheesy

There's a few benefits to my system, but yeah, it can cause a bit of a mess to look at. I just like being able to quickly load up "Build 7-21-2013" (for example) and see where I was 6 or 7 months ago. I don't have to do any real extra work to figure out what version I was on 6 months ago. I just load up the build from that date and go. Wink

- Raymond "Rayvolution" Doerr.
Retro-Pixel Castles - Survival Sim/Builder/Roguelike!
LIVE-STREAMING DEVELOPMENT: http://www.twitch.tv/SG_Rayvolution
Offline Longarmx
« Reply #9 - Posted 2014-02-28 00:10:08 »

A, B for development state and then major.minor.build

Games published by our own members! Check 'em out!
Legends of Yore - The Casual Retro Roguelike
Offline SwordsMiner

JGO Coder


Medals: 3
Projects: 2
Exp: 1 year


The one and only.


« Reply #10 - Posted 2014-02-28 01:00:40 »

Honestly I think its just personal preference, thats atleast what ive seen. However I do it like Notch/Mojang does minecraft, Major.Minor.Patch

If I made you laugh, helped you at all, or did something cool, I only ask that you smash that appreciate button with your nose.
Offline Rayvolution

JGO Kernel


Medals: 186
Projects: 2
Exp: 1 year


Resident Crazyman


« Reply #11 - Posted 2014-02-28 01:09:25 »

Honestly I think its just personal preference, thats atleast what ive seen. However I do it like Notch/Mojang does minecraft, Major.Minor.Patch

yeah, Major.Minor.Patch is a very common method. Although I'd argue Mojang doesn't do it right. For example, they have "beta 1.7" and "release 1.7". Sort of confusing.

What they really should have done is 0.x.x for beta and then 1.x.x for release.

Now they have an odd problem with beta and retail patches overlapping, makes it really confusing when you read posts about "1.7" and unless you check the date, you might end up getting info on 1.7 *beta* from 3 years ago instead. ;P

- Raymond "Rayvolution" Doerr.
Retro-Pixel Castles - Survival Sim/Builder/Roguelike!
LIVE-STREAMING DEVELOPMENT: http://www.twitch.tv/SG_Rayvolution
Offline Gibbo3771
« Reply #12 - Posted 2014-02-28 05:53:52 »

I use 0.0.0-1.0.0 for alpha/beta. For patching I've just went with something like 0.4.5.1 (extra decimal for patch) then usually if needed, a letter if different patches for different is/hardware etc

"This code works flawlessly first time and exactly how I wanted it"
Said no programmer ever
Offline SilverTiger

Junior Member


Medals: 4
Exp: 2 years


がんばってください!


« Reply #13 - Posted 2014-02-28 07:12:19 »

At the moment I usually do it like this:
1  
@version Major.Minor[.Build] (Day.Month.Year)

So I have the version and the build time. Smiley

You could also get more information about Versioning here. Interesting to read Cheesy

By the way in Visual Studio Versioning is like this:
1  
Major.Minor.Build.Revision
Offline ctomni231

JGO Wizard


Medals: 99
Projects: 1
Exp: 7 years


Not a glitch. Just have a lil' pixelexia...


« Reply #14 - Posted 2014-03-01 01:22:48 »

I love using the dates for versioning in my personal projects. But for big projects, (major)(minor)(patch) is the easiest for users to understand and causes less confusion for the team when we talk about it :-)

Offline kpars

JGO Wizard


Medals: 77
Projects: 4
Exp: 3 years


Extreme Typist.


« Reply #15 - Posted 2014-03-01 01:28:35 »

I always call my development builds 'DevMo' builds, 'DevMo' being short for 'Developer Demo'. Never saw the point in naming builds 'Pre-Alpha', 'Alpha', 'Beta', and so on.

As for numerical versioning, I always use this:
[Month] Major.Miner.Patch[.Fix]
.

- Jev

Offline HeroesGraveDev

JGO Kernel


Medals: 246
Projects: 11
Exp: 2 years


┬─┬ノ(ಠ_ಠノ)(╯°□°)╯︵ ┻━┻


« Reply #16 - Posted 2014-03-01 01:43:03 »

I like the major, minor, patch system, but not the format. X.X.X is a bit weird and implies there should be a few versions between x.(n).0 and x.(n+1).0, when really those are just for hotfixes.

So I use a letter for the patch instead, and patch 0 has no letter.

Eg: 1.1 is second minor version after 1.0 and 1.1c would be the third patch for that version (If that many bugs manage to slip through)

When I'm just hacking away at something with not much in mind I call it version X.X-Dev. Where X.X is the next proper version.
For alphas/betas, I use X.X-Beta and X.X-Alpha respectively.

It means version numbers can be kept separate from build types and both easily identified.

Offline SwordsMiner

JGO Coder


Medals: 3
Projects: 2
Exp: 1 year


The one and only.


« Reply #17 - Posted 2014-03-01 02:19:19 »

you might end up getting info on 1.7 *beta* from 3 years ago instead. ;P

*how I am when I dont realize the date* They added grass? I thought that was already implemented. But what a cool info.

If I made you laugh, helped you at all, or did something cool, I only ask that you smash that appreciate button with your nose.
Offline Agro
« Reply #18 - Posted 2014-03-01 04:09:32 »

1.0 or 1.1 works pretty good

Offline Mads

JGO Ninja


Medals: 26
Projects: 3
Exp: 6 years


One for all!


« Reply #19 - Posted 2014-03-01 10:44:19 »

If you simply count, it's really easy to auto-update the version number from inside your build-script. Tongue

Online SHC
« Reply #20 - Posted 2014-03-01 13:07:31 »

I made a post here. Game Versioning or Numbering

Offline mikoch
« Reply #21 - Posted 2014-03-01 18:55:17 »

Take a look at semantic versioning
http://semver.org/ describes it in details and explains why it matters.
It might be overkill for a game project which is never linked to by other binaries but it does not hurt to use standard that is widely accepted and uderstood. (Semantic versioning is suggested versioning by github)

Pages: [1]
  ignore  |  Print  
 
 
You cannot reply to this message, because it is very, very old.

 

Add your game by posting it in the WIP section,
or publish it in Showcase.

The first screenshot will be displayed as a thumbnail.

TehJavaDev (18 views)
2014-08-28 18:26:30

CopyableCougar4 (26 views)
2014-08-22 19:31:30

atombrot (39 views)
2014-08-19 09:29:53

Tekkerue (36 views)
2014-08-16 06:45:27

Tekkerue (33 views)
2014-08-16 06:22:17

Tekkerue (22 views)
2014-08-16 06:20:21

Tekkerue (33 views)
2014-08-16 06:12:11

Rayexar (70 views)
2014-08-11 02:49:23

BurntPizza (47 views)
2014-08-09 21:09:32

BurntPizza (38 views)
2014-08-08 02:01:56
List of Learning Resources
by Longor1996
2014-08-16 10:40:00

List of Learning Resources
by SilverTiger
2014-08-05 19:33:27

Resources for WIP games
by CogWheelz
2014-08-01 16:20:17

Resources for WIP games
by CogWheelz
2014-08-01 16:19:50

List of Learning Resources
by SilverTiger
2014-07-31 16:29:50

List of Learning Resources
by SilverTiger
2014-07-31 16:26:06

List of Learning Resources
by SilverTiger
2014-07-31 11:54:12

HotSpot Options
by dleskov
2014-07-08 01:59:08
java-gaming.org is not responsible for the content posted by its members, including references to external websites, and other references that may or may not have a relation with our primarily gaming and game production oriented community. inquiries and complaints can be sent via email to the info‑account of the company managing the website of java‑gaming.org
Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines | Managed by Enhanced Four Valid XHTML 1.0! Valid CSS!