LightBurn Release Candidates



In order to improve the quality and stability of official releases, we offer a Release Candidate period for upcoming releases.

Release Candidates are versions of LightBurn that have been through internal testing, and are now ready for a short period period of public testing before official release. We use the Release Candidate stage to gather user feedback and fix issues before the official release.

In other words, we want you try out all the cool new features and let us know what you think!

While Release Candidates are generally very stable, be sure to use them with a little extra caution — save projects frequently, and be mindful of the potential for unexpected results. If you're under a deadline or working with expensive material, now is not the best time to try a Release Candidate. 

Reporting Bugs

If you encounter a bug, please let us know by sending an email to BetaSupport@LightBurnSoftware.com, or by making a post in the latest Release Candidate thread on our support forum. Please include as much information as you can recall about what you were doing, so we can reproduce and fix the issue.

Using Release Candidates

You can install LightBurn Release Candidates side-by-side with the full release version.

The standard licensing rules apply — you'll need to have a current license key to run these (or be in an active trial period). 

On Windows, all Release Candidate builds install to a directory with a _PreRelease suffix by default.

The application will also appear in your Start Menu as LightBurn (PreRelease)

image

On Mac, the app has the _PreRelease suffix added to its name.


Just as with the installation directory, the preferences are stored in a directory with a _PreRelease suffix. The first time installing a pre-release version of LightBurn, you'll be prompted to import the preferences from your full release install.

You can also use the User Bundles feature later on to transfer your existing release preferences to your pre-release instance of the software.