Mambu Release Flow
  • Updated on 15 Oct 2019
  • 8 minutes to read
  • Print
  • Share
  • Dark
    Light

Mambu Release Flow

  • Print
  • Share
  • Dark
    Light

Release Types

Here at Mambu we adopt the continuous delivery model, which allows us to seamlessly provide updates to our product and react faster if an issue should occur.

For added clarity, we divide our releases into three types based on its content and the impact it has on your operations, allowing you to know if you need to take any action when a new release is performed.

When will it start?

We have started making preparations for adjusting our release processes and also the release notes as to comply and support the new process. We aim at deploying globally starting Q1/2020.

Identifying the release type

The release type is specified in our release notes. We also follow the principle of semantic versioning for our releases, allowing you to easily identify the release type based on the version change.

Semantic versioning

Semantic versioning is a 3-component number in the format of X.Y.Z. Depending on the release type, we will increment the corresponding component number, as described below.

image

  • Increasing the value of X indicates a Breaking Change release.
  • Increasing the value of Y indicates a Feature release.
  • Increasing the value of Z indicates a Patch release.

Patch releases

The Patch release is a type that requires no action on your side, as it brings along only bug fixes and improvements that do not change the way Mambu features behave.

Patch releases will be rolled out to Sandbox environments as soon as available and on Production Environment shortly afterwards (it can even be on the same day).

Frequency: Very often ( > 1 per week)
Action required: None
Email notification: No

Please be Aware
Mambu will not give notice for Patch releases, as these will have an increased frequency and no impact on your operations; the corresponding release notes will be created and available on our community page.

Feature releases

The Feature release is a type that requires action on your side only if you plan to use the new features that are brought along with it. It has no impact on how existing Mambu features behave.

Feature releases will be rolled out to Sandbox environments as soon as available and on Production Environment shortly afterwards (it can be on the same day).

Frequency: Often (± 1 per month)
Action required: Optional
Email notification: Yes

Breaking Change releases

The Breaking Change release is a type that requires action from your side as to ensure that you are able to use the feature in its new form. By new form we refer to changes in the API contracts (i.e. definition of the API inputs and outputs and API specifications) or in the behaviour of existing functionality.

Frequency: Rare (on a need-basis)
Action required: Mandatory
Email notification: Yes

When planning for a breaking change, we will evaluate if we can keep backwards compatibility as to allow two behaviours of the feature in parallel. As there may be cases where this is not possible, we will approach things differently, as follows:

Scenario 1 - Backwards compatibility maintained

In this scenario, we will release a breaking change and will ensure that we will keep both the new and old behaviour running in paralel for a period of three months (or more, depending on the case). This will give you time to adapt your workflows/integration as to work with the new behaviour.

When the backwards compatibility period ends, the old behaviour will be removed.

Scenario 2 - No backwards compatibility

When backwards compatibility cannot be maintained due to technical constrains, we will send out an announcement three months ahead (or more, depending on the case), informing on what is going to be changed and an estimated date on when it will be released.

When the release will be done, the old behaviour will be replaced by the new one, and, as such, you should update your workflows/integration beforehand.

Please Note
It may be the case that you are not using the updated feature or API contract, and in this case, you won't have to perform any action in preparing for the release.

Release types inclusion policy

Betwen the release types there is an inclusion policy. A Feature release can include content from the Patch release (bug fixes and improvement), whilst a Breaking Change release may include the content from both Feature and Patch releases.

Release Inclusion


Database Changes

It may be that from time to time Mambu will update the database structure, as to accomodate new use cases or maintenance (e.g. updating to a newer version of the database engine).

Where are the changes published?

If updates are performed to the database data structure, we will publish these alongside the release notes, with a dedicated section labeled "Database Changes".

What impact would these changes have?

If the database structure would be changed, then this could impact the following areas:

  • Data Import
  • Jasper Reports

Rest assured, if we are to perform a change in the data structure, this would be promoted via a Breaking Change release.

Mambu Release/Incident Notifications

Mambu notifies customers on upcoming releases or possible incidents via StatusPage.

In order to make sure that you are always up to date with our releases and possible incidents, please ensure that at least one key person from your organisation is subscribed to our notifications, by following the steps below.

1. Go to https://status.mambu.com/ if your organisation is on a Shared Environment (for private environments, see note at the end)

2. Hit Subscribe to Updates

c5da3825-803b-4320-89ba-ca05c765b5d8.png

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

f692061b-e87a-4f89-ad41-fb391048363e.png

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.

27868902-bdba-4ac2-af53-10a03510ea53.png

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.

Please be Aware
For releases of type "Patch", we will operate under the "silent release" process, meaning we won't send out notifications when performing releases.

Aha! Ideas and Features

At Mambu we use Aha! to help us build an overview on what we're working on actively and also gather feedback under the form of ideas.

Submit new ideas, track progress on existing items

At Mambu we use Aha! to help us build an overview on what we're working on actively and also gather feedback under the form of ideas.

Ideas can be raised directly by you under our idea portal, available at https://mambu.ideas.aha.io or by contacting your assigned Customer Success Manager, whom will gladly pass your idea to our product team.

We highly encourage you to visit our idea portal, browse existing ideas and vote for the ones that are of interest to you.

This will also help our product team, as they periodically reviews ideas and, based on interest and applicability, it may select some to promote to features and plan for development in the upcoming period.

To view progress on ideas and features, you can use the public portal or the MyMambu admin page, where you can review all the features which are internally tagged with a unique identifier 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.

Please be Aware
The features availabe to you in your MyMambu account work on a customer tag base. This means that a tag is associated with your account and with the features that you've expressed interst in. To ensure you have all features, please request a tag on the desired ones.

Feature Planning

1. Current

All features that are found in the current lane have in the development process and should be released in the upcoming three months.

2. Next

Features in the next lane are already analysed and are to undergo development within the upcoming three to six months.

3. Future

The future lane holds feature that we plan on working in the upcoming six to twelve months. Considering the big time span, their priority may be subject to change.

4. Candidates

Here we hold all features which Mambu is considering to develop in the next period, once the items which are planned for the next and future term 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 as we might release it only to a couple of customers initially for beta testing.

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?