Skip to main content
Version: 2.x

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. This page explains our release philosophy so you know when to upgrade an existing application.

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 :)

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?

We release a minor version of Front-Commerce every 6 weeks with 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 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

Our release calendar

2023 releases

  • 2.21:
    • 23 december (2022): 2.21.0-beta.0
    • 6 january: 2.21.0-beta.1
    • 19 january: 2.21.0
  • 2.22:
    • 3 february: 2.22.0-beta.0
    • 17 february: 2.22.0-beta.1
    • 2 march: 2.22.0
  • 2.23:
    • 17 march: 2.23.0-beta.0
    • 31 march: 2.23.0-beta.1
    • 13 april: 2.23.0
  • 2.24:
    • 28 april: 2.24.0-beta.0
    • 12 may: 2.24.0-beta.1
    • 25 may: 2.24.0
  • 2.25:
    • 9 june: 2.25.0-beta.0
    • 23 june: 2.25.0-beta.1
    • 6 july: 2.25.0
  • 2.26:
    • 21 july: 2.26.0-beta.0
    • 4 august: 2.26.0-beta.1
    • 17 august: 2.26.0
  • 2.27:
    • 1 september: 2.27.0-beta.0
    • 15 september: 2.27.0-beta.1
    • 28 september: 2.27.0
  • 2.28:
    • 13 october: 2.28.0-beta.0
    • 27 october: 2.28.0-beta.1
    • 9 november: 2.28.0
  • 2.29:
    • 24 november: 2.29.0-beta.0
    • 8 december: 2.29.0-beta.1
    • 21 december: 2.29.0

Note: in order to follow Semantic Versioning, we'll very likely switch to a 3.x major version during the year. We'll update the versions accordingly and of course communicate as soon as we'll have more details.

2022 releases