Minor versioning

[Robert Zelník]

Ryan, do you have any news regarding minor versioning of ProcessWire? It's somewhat difficult to maintain multiple ProcessWire installations in the current state, if the information about minor version is missing, so I actually don't know which version of PW2.2 is used. I suggested earlier to do that by adding tags in git (like 2.2.1, 2.2.2 etc.). It would also be great to add the minor version info in README.txt or in VERSION text file. Would be that the right way for ProcessWire, or do we need to find another method?

[diogo]

Ryan is on vacations, maybe he will answer only in one week...

[Robert Zelník]

Ok, no problem. Thanks for notice.

[ryan]

I still plan to go the tags route, at least when it comes to version numbers like 2.2.1, 2.2.2, etc. Just haven't gotten to it yet, but will soon.

I don't think this is what you are looking for, but also wanted to mention how you can access the version number from the API. $config->version; holds the version number in a string, like '2.2.0'. You can also access the individual components as integers from ProcessWire::versionMajor; ProcessWire::versionMinor; and ProcessWire::versionRevision;

[Robert Zelník]

This is great news, I didn't know about that. Thanks Ryan. Later I realized that I can use git to keep the code up-to-date (it isn't a revolutionary idea ).