Mambu Development and Release Flows Overview
  • Updated on 28 Dec 2018
  • 6 minutes to read
  • Print
  • Share
  • Dark

Mambu Development and Release Flows Overview

  • Print
  • Share
  • Dark

Release Trains

Major Release Trains

Major Releases contain new features and functionalities, as well as database changes and migration scripts. Most features and bugs or technical tasks that require a downtime for deployment are included in Major Releases. There are up 4 Major Releases in a year, without any fixed dates assigned.

Major release versioning is done incrementally, ie V5, V6, V7 and so on.

Minor Release Trains

Minor Releases are small releases that we do for issues that can't or shouldn't wait to be included in the Major Releases. In general, Mambu will release all defect fixes and improvements on Minor Release trains, unless the respective defect/improvement poses downtime to production, and is then included in a major release instead. Sometimes, Mambu will also include smaller features in Minor Release trains, with the same approach, as long as it does not cause a downtime on production.

Minor Releases are deployed every Tuesday to Sandbox and every Wednesday to Production. If there are no issues ready for the respective train, then no release is performed on that day.

Mambu may also perform minor releases outside above regular schedule, what we refer to internally as Urgent Minor Releases. This can happen when an issue in production is a Blocker / Critical and must be addressed asap.

Minor release versioning is done incrementally as well, based on major release version ie V5.1, V5.2, V5.3 and so on.

Release Candidates

Release Candidates are small releases that we do while a new major version of Mambu is on Sandbox. The scope is to improve any issues reported while the new version is on Sandbox, before the actual Production release.

Release candidates are deployed every Thursday, while the new version is on Sandbox. The same principle applies as for Minor Releases, if no issues are ready then no Release Candidate deployment is performed.

Release candidate versioning is done incrementally, based on major release version ie V5-RC01, V5-RC02, V5-RC03 and so on.

Release Updates and DB Changes Notifications

Mambu announces before each new release any new functional updates, DB changes, functionality changes, bug fixes etc. All the changes are documented in our Release Notes, and delivered to customers in advance, also depending on the type of release.

Minor Releases and Release Candidates, as can be seen above, occur at preset weekly intervals and Release Notes are shared on the day the release is happening. The same applies for any urgent fix deployment. Do note, new functionalities or upgrades, along with necessary DB changes for the new functionalit, may be released via Minor Releases and Release Candidates as well, not only via Major Releases.

For Major Releases, you can see below the standard notification updates timeframes:

Major Releases Timeframes:

  • Sandbox - 14 days
  • Production - 14 days

Major Releases Delay announcements:

If for any reason Mambu must delay an already announced release, Mambu reserves the right to reschedule and notify customers in advance by:

  • Sandbox - 1 working day
  • Production - 5 working days

Backwards Compatibility Changes

Mambu takes very seriously any change in terms of API parameters, DB changes etc. that may break your integrations and your usage of Mambu.

In the event Mambu will need to introduce such a change, Mambu will ensure backwards compatibility and we will send a separate email notification with a minimum of 4 months in advance, allowing your organisation to perform the changes in due time, before the backwards compatibility is completely removed.

Subscribing for Mambu Release Notifications:

Mambu notifies customers on upcoming releases via StatusPage.

To receive updates on Mambu releases and incidents please follow these steps:

1. Go to if your organisation is on a Shared Environment (for private environments, see note at the end)

2. Hit Subscribe to Updates


3. Choose how you wish to be notified (email, SMS, etc.)


4. After subscribing, you will receive an email confirmation. You can follow the link in that email for Managing Subscriptions in order to subscribe for the region (component) you need, otherwise you will be notified for all regions.


For Private Environments, please reach out to our support team, they will gladly provide you with the link to your dedicated Status Page, in order to receive notifications for your environment. The above link is only for shared environments.

Once your details have been submitted, you will be notified automatically on release dates and time. Anyone in your organisation will be available to subscribe to this page.

Where do I see feature statuses, on which release version they went, etc?

In MyMambu you can review all the features which are internally tagged with a unique id for your organisation. You will be able to identify as such the status of the feature, what status it has now in terms of planning, or on what release they were already released. See more details here related to MyMambu.

Aha Feature Planning

1. Current

Features which are in development phase and once ready will be released with one of the next release trains, which may be a Major or Minor release.

2. Near Term

Features which were analysed, but the development phase is planned to start soon, meaning in 1 to 3 months, after we have finished development on the current items.

3. Future

Features which were analysed, but the development phase is planned to start sometime in the next 6 to 12 months, while features which are currently in development or planned to work on near term are addressed.

4. Candidates

Features which were analysed, and which Mambu is considering to develop in the next period, once the items which are planned near term and future are addressed.

5. Backlog

​Under Backlog we hold all the features which we are considering for development but which are not planned or analysed in detail yet.

Please Note
Once a feature is developed, it may take additional time until it reaches production, especially if released via Major release. This is because any new feature will undergo Regression Testing first, which may take up to 2 weeks, and then we will deploy on Sandbox. As such, depending on the release type, major or minor, the feature will also stay on sandbox for a period of time (see more above, on release types).

Mambu Releases

Once a feature has reached Ready to Ship status (see below), you will be able to see the major version under which it will be included, this is regardless if the feature is released via Major or Minor release.

After the development phase is finished, the entire release is regression tested by our QA team. When the regression testing is done, the functionalities are deployed on Sandbox. If any issues are found while on Sandbox, the Support team collects feedback from you and raises it to the Product Management team.

Typically, Mambu keeps a version on Sandbox for about 4 weeks, after which the version will be released to all Production environments.

Aha Feature Statuses

The Aha! features are following a certain workflow and depending on the action which was taken on the feature the status will change accordingly. The following statuses are used for Mambu features:

Status Description
Under Consideration The product team is considering doing the feature in that release, but no commitment is taken.
Drafting The product team is at the design stage, requirements elicitation and defining with internal and external stakeholders.
Requirements Done All requirements are defined, design is ready and JIRA issues are raised.
In Development Development is in progress for the respective feature.
Ready to Ship Feature has been developed and is ready to be shipped to Production, awaiting either regression testing or is currently on Sandbox.
Shipped Feature has been shipped to Production.
Will not implement State used for features that were promoted from ideas (or created as features directly) which were considered in the past, but which are no longer considered for implementation.
Was this article helpful?