Principles and Release Cycle
The development approach is built around stability and predictability. Since subscriber essentially mirrors production data, we follow the principle that data structures and standard views should remain consistent unless absolutely necessary for product evolution. This gives customers confidence that their reports, exports or analyses won’t break unexpectedly. We only expand the information available, we don’t change existing structures unless the underlying product logic requires it. This methodology ensures that subscriber remains a reliable platform for customer analytics while allowing for necessary evolution as the core Dawiso product grows and improves.
Releases are directly tied to Dawiso product releases. This component don’t include independent releases - every update comes as part of a Dawiso product release. This keeps everything synchronized and ensures that changes in the product are immediately reflected in the analytical layer. Please note that not each Dawiso release includes dedicated release so it is necessary to follow release notes that cover all relevant changes, new features or any impacts on existing functionality.
Change Management
Dawiso responsibility is to keep data structures and standard views consistent unless it is absolutely necessary for product evolution to change it.
- Safe Changes - Adding new columns to existing tables, creating new views, adding new Source Tables. These don’t break anything existing and just give you more data to work with.
- Structural Changes - Changes to primary keys, foreign keys, column names, or data types. These happen when the underlying product changes require them. We document these carefully since they might impact custom customer objects.
- Business Logic Changes - When Dawiso changes how it handles enums, calculations, or business rules. For example, if we change the key values for database technology types, that could impact customer views that specifically reference those values.
If any of these changes happens, Dawiso provide all fixes necessary so the Source Tables and Standard Views keeps its functionality and Dawiso also notifies customers regarding these changes in advance via release notes. if we make changes to Source Tables, customers are responsible for updating their custom objects to work with the new structure. We’ll provide detailed information about what changed, but the adaptation work falls to the customer.
Emergency Fixes
Sometimes we need to make urgent fixes outside the normal release cycle. These are rare and only happen for critical issues that significantly impact data quality or system stability. When emergency fixes are necessary, we immediately notify all affected customers with details about what was fixed and any potential impact on their usage. We keep these interventions to an absolute minimum and document them thoroughly.