PyLucid CMS Logo

Update a old PyLucid installation.

↑ FAQ  #

↑ stable / development versions of PyLucid?  #

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.

↑ Which is the last "stable" version of PyLucid?  #

Look at this website at the bottom. There is the version we used for this page: PyLucid v1.5.1.1031
This is the most recent stable version in production ;)

↑ Version scheme of PyLucid ?  #

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)

↑ How to get information about the developing?  #

We create new blog articles about changes and developing. We tag those articles with development and used this tags, too:

↑ How is the PyLucid version number stored?  #

The version number is stored in pylucid_project/__init__.py. Display it, e.g.:

Bash
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.

↑ How to get your installed PyLucid Version number?  #

Read the page about package version information.

↑ Should i update my installation?  #

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.

↑ How to update?  #

Read How to update PyLucid.

↑ sub pages  #

0 comments for 'update PyLucid':
    there exist no comment for 'update PyLucid'
Leave a comment
tag navi update

django-processinfo: 7.4 ms of 120.4 ms (6.1%)