Tag Info

New answers tagged

1

I'd say your best bet is to create some sort of pattern for either each mod, or a dictionary of all known patterns, and use that to parse each version. For mod1, Local: rv0-stable-10 Online: rv1-alpha-13, the pattern will be complicated. It looks like you'll need to first parse rvX- as a number, the middle part perhaps as an enum, and the last as a number ...


1

Seems you are in trouble, if missing a public API based on semantic versioning you must know the rules which govern the release update. Quote from Semantic Versioning 2.0.0 by Tom Preston-Werner In the world of software management there exists a dread place called "dependency hell." The bigger your system grows and the more packages you integrate ...


4

We have a similar situation, and I setup our build/release process like this: Our version numbers consist of four parts (major, minor, build, revision). The first two parts are only changed after a release, the other two change for every build. In our case, the major & minor version come from Jenkins build parameters, the revision number comes from ...



Top 50 recent answers are included