Pelican Release Plan

Pelican makes feature releases containing the development team's latest work approximately once per month. These releases contain new features, code improvements and important bug fixes, which is why we recommend that you keep your Pelican installation up to date.

On the first Thursday of the month, Pelican will create a release candidate that contains a checkpoint of the work we plan to turn into a feature release. Release candidates can be identified by their version number, which is the same as the next feature release version but with a "-rc.X" suffix, such as "v7.18.0-rc.0". This release candidate is tested by our integration team until it meets our quality standards, at which point the "-rc.X" suffix is dropped and the official release is made (e.g. "v7.18.0"). Patches for that release series will be backported as needed if significant bugs are found. When this happens, we will increment the release number accordingly (e.g. "v7.18.1").

To download and install an official release, please see our Pelican Installation Guide. For a full list of Pelican releases and release candidates, please see our GitHub Releases page.