This page describes the release process from Spencer.
It will answer the questions:
- When can I expect a new release from Spencer?
- How will the new Spencer release be provided?
- Until which version does Spencer provide support?
- What should I do as the responsible person for Spencer inside my company?
When can I expect a new release from Spencer?
Spencer release cadence works on a Monthly basis.
Every 2nd week of the month, we'll ship a new version of Spencer. The release will contain fixes (logged from previous version) and new features.
We don't name our release after a cat species (Apple) or candy (Google Android).
Our release carry the name of the month it get's released in .. simple right?!
So in April, we'll release the April release...
In the app, the version will be displayed as followe year - month - build number.
Example - 20.04.1235
Schedule of 2020
Below the scheduled releases till the end of the current year (2020):
- April release - Wednesday (15/04)*
- May release - Tuesday (12/05)
- June release - Tuesday (09/06)
- July release - Tuesday (07/07)
- August release - Tuesday (04/08)
- September release - Tuesday (15/09)
- October release - Tuesday (13/10)
- November release - Tuesday (12/11)
- December release - Tuesday (08/12).
* Exception because of easter Monday.
How will the new Spencer release be provided?
As a customer you'll receive an e-mail with the announcement of the new release and the features/fixes or improvements.
Update Backoffice and Backend
The backoffice and backend are automatically updated by Spencer, you won't notice anything specific unless some new features or improvements.
Updating the stores
If your company opted to have Spencer inside the App and Play Store, Spencer will take care of the upload and the roll out. After 2 or 3 days after the release you can expect an updated version inside the App(*) or Play store.
* Depends on the speed of the approval process from Apple.
Update MDM solutions & Desktop clients
If your company opted to have Spencer distributed through an MDM solution or if the client is a desktop you'll receive an automatic e-mail that a new release file is uploaded to a company specific Google Drive folder.
The customer is responsible of wrapping* the file and distribute it through the choosen MDM solution of the company or distribute the desktop client.
An example of the e-mail shown below.
title - New Release file has been uploaded
sender - firstname.lastname@example.org
*Spencer will deliver a "naked" file as our build pipeline is streamlined towards multiple client delivery and this will give the customer the flexibility to pick any MDM software.
Until which version does Spencer provide support?
How many versions?
Spencer supports to 2 client* versions below the current version.
As an example,lets say the current version is June. That would mean Spencer provides support for the March and May release.
If you're more than 2 versions behind, you won't receive support from email@example.com anymore.
So it is important to follow the release cadence.
*Spencer will automatically updated backend and back-office to the most recent version. For the clients (Apple/Android/desktop), the customer can decide to skip a release.
What should I do as the person responsible for Spencer inside my company?
- Check the agreement with Spencer towards supported clients & distribution
- Communicate to firstname.lastname@example.org if you want to skip a version 1 week upfront.
- Communicate to email@example.com at startup if you want to rollout every month, every 2 months.
- Q: Do I as a customer need to rollout every release?
- A: No, Spencer allows you to skip 2 versions before you current version becomes unsupported. Mail to firstname.lastname@example.org if you have questions towards your current release cycle or if you want to skip a version.