A delivered site is not a finished site. Aurora is a versioned package: a client site depends on it, and receives fixes and additions through an update rather than a rebuild.
A version, end to end
An Aurora version passes its tests, its migrations and its deployment before reaching each site, always under a number that says what changed.
The version number tells what changes
Aurora's versions follow one another on a timeline. The last digit goes up for a fix, the middle one for an addition or an improvement, the first one when the site needs action on its side. Every version has release notes, written from the point of view of what changes on screen.
What happens with every version
- More than 26,000 automated tests pass before every version.
- Database changes are applied automatically at deploy time.
- Going live is one command, and it checks afterwards that the site answers.
- The client's data stays with the client: their server, their domain, their accounts.
- This is the part nobody sees and everything depends on: a site that cannot be updated starts ageing on the day it ships.