I was curious to know what software versioning method are you using for your project?
Major.Minor.Revision.Build?
Enderal Software Versioning
Moderator: Moderatoren
7 Beiträge
Seite 1 von 1
-
stuemper
Enderal Team
- Schwarzer Wächter
- Beiträge: 3298
- Registriert: 14.07.2015 11:43
- Hat sich bedankt: 127 Mal
- Danksagung erhalten: 1240 Mal
Ehm.
Major.whatever
whatever == every patch contains different fixes: script fixes or master fixes or launcher fixes etc. and each different fix increases the version by 0.0.0.1
E.g the first english version of Enderal was 1.1.0.0 and the first english patch was 1.1.0.3, since it contains some Script (1.1.0.1), some master (1.1.0.2) and finally Launcher fixes (1.1.0.3).
Major.whatever
whatever == every patch contains different fixes: script fixes or master fixes or launcher fixes etc. and each different fix increases the version by 0.0.0.1
E.g the first english version of Enderal was 1.1.0.0 and the first english patch was 1.1.0.3, since it contains some Script (1.1.0.1), some master (1.1.0.2) and finally Launcher fixes (1.1.0.3).
-
stuemper
Enderal Team
- Schwarzer Wächter
- Beiträge: 3298
- Registriert: 14.07.2015 11:43
- Hat sich bedankt: 127 Mal
- Danksagung erhalten: 1240 Mal
No, not really. Like I said, we just increase the number. Currently we are at 1.1.7.1, the next patch will probably be 1.1.7.5 (excluding hotfixes - like 1.1.7.2) After the patch 1.1.7.5 we will have 1.1.8.0. Sometimes we just skip digits, if big patches arrive. It's only a rough order
Ah, good. I am just asking because I learnt that different companies use their own way to increment their software progression. Your method is new to me since I am used to seeing semantic versioning. That way I know what your patch sequence is when your release versions of your module and what you mean by the numbers. Just a personal thing I like to look at since I'm a software engineer. Thanks again.
7 Beiträge
Seite 1 von 1
Wer ist online?
Mitglieder in diesem Forum: 0 Mitglieder und 5 Gäste