Re: Eternal X 1.1 digression


	/-/S'pht-Translator-Active/-/

Re: Eternal X 1.1 digression

Posted By: Tycho Date: 1/9/15 5:07 p.m.
In Response To: Eternal X 1.1 digression (Forrest of B.org)

Simply to address your last question:
in general, in software development, the iterations are known by their build number. You keep making builds until you decide you have a beta build, meaning ready for serious testing. Once you have the beta build you can give it a version, and then keep iterating that beta build version with additional build numbers (so beta 1.1 build 31337, beta 1.1 build 31338 etc). As for the version or revision number itself...if you use a three point system, the first number is a major re-writing or change of the whole codebase, new features, new story etc...the second number is generally adding features to the same codebase that don't affect the overall functionality of the codebase, but adds major improvements, the third number generally indicates a maintenance release with patches, bug fixes and compatibility fixes.
None of these are hard and fast rules, but it can help...so your build number is always iterating...start with 1, and rolling along..forever. The version number is issued depending on the nature of the release. In this case 1.1 doesn't seem that bad of a choice, but if there is sufficient content added and changed (all the textures, shapes and weapons) there might be reason to bump it up a number for each major change. Depending on what you release, you might end up at 1.5 just naturally.
Incidentally, congrats for sticking with your project and being stubborn enough to get to "final". That's fantastic.

[ Post a Reply | Message Index | Read Prev Msg | Read Next Msg ]
Pre-2004 Posts

Replies:

Return to Marathon Adam Ashwell 1/4/15 6:20 a.m.

Re: Return to Marathon VikingBoyBilly 1/4/15 10:16 a.m.

Re: Return to Marathon Forrest of B.org 1/5/15 9:19 a.m.

Re: Return to Marathon Adam Ashwell 1/8/15 9:47 a.m.

Eternal X 1.1 digression Forrest of B.org 1/9/15 8:58 a.m.

Re: Eternal X 1.1 digression Tycho 1/9/15 5:07 p.m.

Re: Return to Marathon Spartan 1/5/15 1:31 p.m.

Re: Return to Marathon *LINK* President People 1/5/15 7:54 p.m.

Re: Return to Marathon Adam Ashwell 1/8/15 10:12 a.m.

Re: Return to Marathon *LINK* President People 1/10/15 10:19 p.m.

Re: Return to Marathon Adam Ashwell 1/11/15 8:47 a.m.

Re: Return to Marathon VikingBoyBilly 2/2/15 11:27 a.m.

Re: Return to Marathon Dr. John Sumner 2/4/15 7:17 a.m.

Re: Return to Marathon VikingBoyBilly 2/4/15 8:33 a.m.

Re: Return to Marathon Philtron 2/4/15 9:00 a.m.

Re: Return to Marathon VikingBoyBilly 2/4/15 10:34 a.m.

Re: Return to Marathon Philtron 2/4/15 12:41 p.m.

Re: Return to Marathon VikingBoyBilly 2/4/15 1:36 p.m.

Re: Return to Marathon VikingBoyBilly 2/5/15 5:26 a.m.

Re: Return to Marathon President People 2/5/15 1:40 p.m.

Re: Return to Marathon President People 2/5/15 1:42 p.m.

Re: Return to Marathon VikingBoyBilly 2/5/15 4:10 p.m.

Re: Return to Marathon treellama 2/6/15 3:25 a.m.

Re: Return to Marathon VikingBoyBilly 2/6/15 9:23 a.m.

Re: Return to Marathon Philtron 2/4/15 1:02 p.m.

Re: Return to Marathon Tonix777 2/8/15 9:10 a.m.

Re: Return to Marathon Tonix777 2/8/15 9:27 a.m.

Re: Return to Marathon Dr. John Sumner 2/8/15 1:58 p.m.

Re: Return to Marathon Tonix777 2/8/15 7:07 p.m.

Re: Return to Marathon Dugit 6/14/18 11:35 p.m.

Re: Return to Marathon Dr. John Sumner 6/15/18 2:54 a.m.

Re: Return to Marathon Forrest of B.org 6/15/18 7:51 a.m.

Re: Return to Marathon Dr. John Sumner 6/15/18 8:31 a.m.

Re: Return to Marathon Godot 6/15/18 12:21 p.m.

Re: Return to Marathon Dr. John Sumner 6/15/18 3:03 p.m.

Re: Return to Marathon General-RADIX 6/16/18 2:31 a.m.

Re: Return to Marathon Dr. John Sumner 6/16/18 4:59 a.m.

Re: Return to Marathon Tonix777 2/8/15 9:24 a.m.

[ Post a Reply | Message Index | Read Prev Msg | Read Next Msg ]
Pre-2004 Posts

Your Name:
Your E-Mail Address:
Subject:
Message:
: Simply to address your last question: in general, in software development, : the iterations are known by their build number. You keep making builds : until you decide you have a beta build, meaning ready for serious testing. : Once you have the beta build you can give it a version, and then keep : iterating that beta build version with additional build numbers (so beta : 1.1 build 31337, beta 1.1 build 31338 etc). As for the version or revision : number itself...if you use a three point system, the first number is a : major re-writing or change of the whole codebase, new features, new story : etc...the second number is generally adding features to the same codebase : that don't affect the overall functionality of the codebase, but adds : major improvements, the third number generally indicates a maintenance : release with patches, bug fixes and compatibility fixes. : None of these are hard and fast rules, but it can help...so your build number : is always iterating...start with 1, and rolling along..forever. The : version number is issued depending on the nature of the release. In this : case 1.1 doesn't seem that bad of a choice, but if there is sufficient : content added and changed (all the textures, shapes and weapons) there : might be reason to bump it up a number for each major change. Depending on : what you release, you might end up at 1.5 just naturally. : Incidentally, congrats for sticking with your project and being stubborn : enough to get to "final". That's fantastic. :

If you'd like to include a link to another page with your message,
please provide both the URL address and the title of the page:
Optional Link URL:
Optional Link Title:

If necessary, enter your password below:
Password:

Problems? Suggestions? Comments? Email maintainer@bungie.org
Marathon's Story Forum is maintained with WebBBS 5.12.

Return to Marathon	Adam Ashwell	1/4/15 6:20 a.m.
Re: Return to Marathon	VikingBoyBilly	1/4/15 10:16 a.m.
Re: Return to Marathon	Forrest of B.org	1/5/15 9:19 a.m.
Re: Return to Marathon	Adam Ashwell	1/8/15 9:47 a.m.
Eternal X 1.1 digression	Forrest of B.org	1/9/15 8:58 a.m.
Re: Eternal X 1.1 digression	Tycho	1/9/15 5:07 p.m.
Re: Return to Marathon	Spartan	1/5/15 1:31 p.m.
Re: Return to Marathon LINK	President People	1/5/15 7:54 p.m.
Re: Return to Marathon	Adam Ashwell	1/8/15 10:12 a.m.
Re: Return to Marathon LINK	President People	1/10/15 10:19 p.m.
Re: Return to Marathon	Adam Ashwell	1/11/15 8:47 a.m.
Re: Return to Marathon	VikingBoyBilly	2/2/15 11:27 a.m.
Re: Return to Marathon	Dr. John Sumner	2/4/15 7:17 a.m.
Re: Return to Marathon	VikingBoyBilly	2/4/15 8:33 a.m.
Re: Return to Marathon	Philtron	2/4/15 9:00 a.m.
Re: Return to Marathon	VikingBoyBilly	2/4/15 10:34 a.m.
Re: Return to Marathon	Philtron	2/4/15 12:41 p.m.
Re: Return to Marathon	VikingBoyBilly	2/4/15 1:36 p.m.
Re: Return to Marathon	VikingBoyBilly	2/5/15 5:26 a.m.
Re: Return to Marathon	President People	2/5/15 1:40 p.m.
Re: Return to Marathon	President People	2/5/15 1:42 p.m.
Re: Return to Marathon	VikingBoyBilly	2/5/15 4:10 p.m.
Re: Return to Marathon	treellama	2/6/15 3:25 a.m.
Re: Return to Marathon	VikingBoyBilly	2/6/15 9:23 a.m.
Re: Return to Marathon	Philtron	2/4/15 1:02 p.m.
Re: Return to Marathon	Tonix777	2/8/15 9:10 a.m.
Re: Return to Marathon	Tonix777	2/8/15 9:27 a.m.
Re: Return to Marathon	Dr. John Sumner	2/8/15 1:58 p.m.
Re: Return to Marathon	Tonix777	2/8/15 7:07 p.m.
Re: Return to Marathon	Dugit	6/14/18 11:35 p.m.
Re: Return to Marathon	Dr. John Sumner	6/15/18 2:54 a.m.
Re: Return to Marathon	Forrest of B.org	6/15/18 7:51 a.m.
Re: Return to Marathon	Dr. John Sumner	6/15/18 8:31 a.m.
Re: Return to Marathon	Godot	6/15/18 12:21 p.m.
Re: Return to Marathon	Dr. John Sumner	6/15/18 3:03 p.m.
Re: Return to Marathon	General-RADIX	6/16/18 2:31 a.m.
Re: Return to Marathon	Dr. John Sumner	6/16/18 4:59 a.m.
Re: Return to Marathon	Tonix777	2/8/15 9:24 a.m.



	Your Name:
	Your E-Mail Address:
	Subject:
	Message: : Simply to address your last question: in general, in software development, : the iterations are known by their build number. You keep making builds : until you decide you have a beta build, meaning ready for serious testing. : Once you have the beta build you can give it a version, and then keep : iterating that beta build version with additional build numbers (so beta : 1.1 build 31337, beta 1.1 build 31338 etc). As for the version or revision : number itself...if you use a three point system, the first number is a : major re-writing or change of the whole codebase, new features, new story : etc...the second number is generally adding features to the same codebase : that don't affect the overall functionality of the codebase, but adds : major improvements, the third number generally indicates a maintenance : release with patches, bug fixes and compatibility fixes. : None of these are hard and fast rules, but it can help...so your build number : is always iterating...start with 1, and rolling along..forever. The : version number is issued depending on the nature of the release. In this : case 1.1 doesn't seem that bad of a choice, but if there is sufficient : content added and changed (all the textures, shapes and weapons) there : might be reason to bump it up a number for each major change. Depending on : what you release, you might end up at 1.5 just naturally. : Incidentally, congrats for sticking with your project and being stubborn : enough to get to "final". That's fantastic. :
	If you'd like to include a link to another page with your message, please provide both the URL address and the title of the page:
	Optional Link URL:
	Optional Link Title:
	If necessary, enter your password below:
	Password: