It is our effort to have always the git 'master' branch stable usable.
Big source code changes would be started in a separate branch and merged if they are stable.
Look at this website at the bottom. There is the version we used for this page:
Since 2012 we used this version number scheme:
|major||Very big milestone.|
|minor||backward incompatible changes -> admin actions needed|
|maintenance||Bugfixes and/or visible changes but backward compatible (Can be updated without admin actions)|
|build||Date of the last commit (Format: MMDD -> Month + Day)|
We create new blog articles about changes and developing. We tag those articles with development and used this tags, too:
The version number is stored in pylucid_project/__init__.py. Display it, e.g.:
1 2 3
~$ cd ~/PyLucid_env ~/PyLucid_env$ cat src/pylucid/pylucid_project/__init__.py | grep "__version__ =" __version__ = (1, 0, 3)
The script pylucid_project/__init__.py adds the last git commit date dynamic to the version number.
Yes, if on pylucid.org runs a newer version than your used version ;)
PyLucid used a rolling release / rolling update strategy. You can and should update to the next version.
Read How to update PyLucid.