Release process

Front-Commerce is built around the motto “Make it work, then make it better”. This means that it is possible today to develop and deploy your website to production.

Our mission of making your life easier, and your customers happier is an ongoing process. Front-Commerce will thus regularly evolve. Our main strength is our flexibility. We do take into account our clients needs and adapt our Roadmap to match theirs. If you have any particular needs, feel free to contact us and we will see what we can do to help you :)

This page explains our release philosophy.

Semantic Versioning

We aim at releasing often and follow Semantic Versioning to clearly communicate our advancements to developers. We document each migration process (changelog, release notes and documentation updates) and add deprecation warnings while keeping backwards compatibility to keep upgrades as seamless as possible.

TL;DR: (from the Semantic Versioning documentation)

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make incompatible API changes,
  2. MINOR version when you add functionality in a backwards compatible manner, and
  3. PATCH version when you make backwards compatible bug fixes.

Additional labels for pre-release can (and in our case will) be added to the MAJOR.MINOR.PATCH format.

Release pace

When to expect a new release?

At Front-Commerce, the team has been growing a lot! (as part of our fundraising notably 👀)

We are now able to implement a lot of new elements between two minor releases, every 6 weeks (new features, tech improvements, bug fixes …)

In order to follow the pace of our users, we have decided to release 2 intermediate pre-releases between 2 minor releases, to allow our early-adopters to integrate the features as soon as possible and to give us feedback.

Therefore, here is the theoretical rhythm of a cycle (Front-Commerce is currently in MAJOR version 2):

Front-Commerce’s release pace and cycles

The 2022 release calendar

  • 2.12.0: 6 january
  • 2.13.0: 17 february
  • 2.14:
    • 4 march: 2.14.0-beta.0
    • 18 march: 2.14.0-beta.1
    • 31 march: 2.14.0
  • 2.15:
    • 15 april: 2.15.0-beta.0
    • 29 april: 2.15.0-beta.1
    • 12 may: 2.15.0
  • 2.16:
    • 27 may: 2.16.0-beta.0
    • 10 june: 2.16.0-beta.1
    • 23 june: 2.16.0
  • 2.17:
    • 8 july: 2.17.0-beta.0
    • 22 july: 2.17.0-beta.1: 22-07-2022
    • 4 august: 2.17.0
  • 2.18:
    • 19 august: 2.18.0-beta.0
    • 2 september: 2.18.0-beta.1
    • 15 september: 2.18.0
  • 2.19:
    • 30 september: 2.19.0-beta.0
    • 14 october: 2.19.0-beta.1
    • 27 october: 2.19.0
  • 2.20:
    • 10 november: 2.20.0-beta.0
    • 25 november: 2.20.0-beta.1
    • 8 december: 2.20.0
Edit on GitHub  or  Send us a feedback