MegaGlest Forum
MegaGlest => MegaGlest => Topic started by: tomreyn on 8 March 2014, 16:47:29
-
Since Omega brought this up (https://forum.megaglest.org/index.php?topic=9451.msg90262#msg90262):
For two releases now, we use a semantic method of versioning, if not "semantic versioning".
We use MAJOR.MINOR.PATCH but their meaning is slightly different (and actually makes more sense to me). We increment the:
- MAJOR version when we make major changes, which may include incompatible API changes, or a major change in functionality or usability
- MINOR version when we make "normal" changes, which may include new or improved functionality and other changes, as well as non backward compatible bug fixes
- PATCH version when we make backwards-compatible bug fixes.
Softcoder, Titi, please correct me if I'm wrong.
As you know we migrated to Git and GitHub not too long ago, and have since started using the Git Flow (http://nvie.com/posts/a-successful-git-branching-model/) branching model, and (optionally) the Git Flow AVH Edition (https://github.com/petervanderdoes/gitflow) for managing the branches. Currently there are two feature branches, one (managed by Softcoder) introduces a new GUI (https://forum.megaglest.org/index.php?topic=9420.0) (thanks to CEGUI (http://cegui.org.uk)), the other holds Titi's light-weight (https://twitter.com/MegaGlest/status/435440680073453568) headless server (https://forum.megaglest.org/index.php?topic=9421.0) variant.
For the past months we used Travis-CI (http://travis-ci.org/MegaGlest/megaglest-source) for Continuous Integration. And just since yesterday our own Continuous Integration (Jenkins) (https://ci.megaglest.org) installation is back (but it needs yet to be configured), so we shall have snapshot builds for Linux and Windows again soon, too.
When I say we then I mean it inclusively, namely whoever regularly contributes to MegaGlest's development and the project as a whole, or will do so in the future.