OFPEC Forum
Editors Depot - Mission Editing and Scripting => OFP - Editing/Scripting General => Topic started by: bored_onion on 15 Aug 2005, 17:41:26
-
When you release a beta/gold mission version what is the correct version number to start at? For example, were I to be releasing a beta in the beta testing forum would I call it 1.0b? 1.0? 0.5? Sorry if this isn't the right board this question but I just figured "If in doubt, post in the general board." :P
-
well a moderator will no doubt move this if it's in the wrong place.
the 'correct' answer is any system YOU choose that can abundantly make clear that the NEXT revision is newer than the older one.
version 'A' is earlier than version 'B'
although general practice starts versions with 1.00, it's flavour of the month. Other schemes have a dating system instead. The only important criteria is that it is always legibly obvious which version is the latest one.
In terms strictly ofp engine. versions are numeric entities (not strings) so, to conform you should keep all versioning numeric if you plan to detect and test the value.
I am not aware of any ofpec policy on this because you can write 'pink elephants' in the version line for anything you submit.
-
sounds groovy. I think itll start at one 1.0b and then ascend in hundreths or five hundreths. Then when the gold release comes itll go back to just 1.0 for submission.
cheers for the help - i'll leave the thread open for a bit in case anyone else has anything to offer
-
I think most people start with 1.00, because that is the first public version. But as Mikero says, it doesn't matter as long as it is clear what version is the latest.
I am not aware of any ofpec policy on this because you can write 'pink elephants' in the version line for anything you submit.
Neither am I aware of any policy
...pink elephants? :P
-Student Pilot
EDIT:
>See if anyone else has anything to offer
Well, forget this post, then ::)
-
No worries, this is on topic on this board.
I thought about this long and hard for my own missions and decided that the first full public release should be version 1. Therefore I number my betas 0-01 .... 0-36 etc. The hyphen is better than the dot because dots tend to have special meanings on occasion.
But as mikero says it's entirely up to you. The only important thing is that it's obvious.
-
I think starting with 0.xx for the beta versions is bets. I have got myself into a bit a muddle with my mission, shortly to be v 1.30 and not yet released. Doing it again I would aim for 1.0 to be the first public release.
-
yeah, maybe it would be better to not have a 1.0b (but then again a 0.01 beta would look a little pathetic...)
-
@onion
it is not, and never will be, abundantly obvious that version 1.98b is EARLIER than 1.00
also, please be aware that the bis engine, and you, can test for numeric version numbers but not alphanumeric strings. This has significance in multiplayer scripts that can check all missions are born equal, and in addons.
-
i dont have much intention of using this thing as part of a script - i was just interested to know whether there was any kind of established customs for submitted versions and stuff. i think ive got all the info i need now so thanks a bunch guys. ;D