Release Cycle

How A Release Cycle Works

Each website release cycle is led by one (or more) of the core Exodus developers.

A release cycle usually lasts around 1 month from the initial scoping meeting to launch of the version.

Phase 1: Planning

This is done on numerous communication channels. The release lead discusses features for the next release of the website. Contributors may get involved with that discussion. The release lead will identify focus leads for each of the features.

Phase 2: Development

Development leads will assemble teams and work on their assigned features. Regular chats are scheduled to ensure the development keeps moving forward.

Phase 3: Beta

Betas are released and beta-testers are asked to start reporting bugs. No more commits for new enhancements or feature requests are allowed for the rest of the release.

Phase 4: Release Candidate

There is a string freeze from this point on. Work is targeted on regressions and blockers only.

Phase 5: Launch

Website version is launched and made available to the public.

The launch is often followed soon after by a minor release (also known as a point release) or a security release as bugs are reported and squashed. A minor release is intended for general bugfixes, small new features and enhancements that do not add major new deployed files. A security release will be deployed at the discretion of the release lead with suggestions/input from component maintainers and committers.

Version releases from 1.0.0 – 2.0.0 seen a short length between push outs because we wanted to get the website to an optimal build in preparation for the public release build [2.0.0]. Future update releases will be less frequent moving forward.