Tag Info

New answers tagged

5

Beware that if CakePHP 3 is changing its plugin API (and your plugin adapts to that change), you probably should increase your major number. BTW, in MELT I am explicitly naming the version(s) of GCC for which that release is made. So I am naming them MELT-1.1.3 for GCC 4.8 or 4.9 Plugins are a corner-case of semantic versioning, because what usually ...


18

It's never explicitly spelled out, but careful reading of semver.org suggests that a version is associated with a proper release, not a VCS commit. So naturally, if you make one release that has multiple bug fixes, you increment the patch component once. Leaving large gaps to account for intermediate states that don't have a version (not even in principle, ...


3

There are pre-release phases for software products: alpha, beta, and release candidate. It depends on how mature your product is. An alpha release would tend to indicate that the application is still relatively unstable and perhaps buggy. This would be anything up to a feature-complete release. As you move toward feature-complete, you may want to consider ...


0

You may follow the: major.minor[.build[.revision]] schema, which means that the version 2.0.0 will be the first build of the rewritten project. It doesn't matter if it is released in production, given to the testers or kept in secrecy. Then, an actual pre-release may be, for instance, 2.0.19.527, and the actual public release may be 2.0.37.692. This ...



Top 50 recent answers are included