SLC #1 - Multiple Statement Types

[g105b]

Our first release! This marks the first simple, lovable, complete release containing the following features:

Simple:

• ProductAggregations list: build entities automatically
• EarningsData: Product Table

Lovable:

• ProductAggregations list: Album cover art
• DataImporter: Animation during import

Complete:

• ProductAggregations list: show aggregate earnings against each item
• DataImporter: Handle Cargo statement types

---

This discussion was created from the release SLC #1 - Multiple Statement Types.

[g105b]

This will be deployed to production soon. I'll update here when it is live.

As a quick note about version numbers, I'd been planning on how we should keep things in line with semantic versioning and I've decided on the following. Let me know what you think of it.

vX.Y.Z

X is the major release number, containing a number of minor releases. This is the kind of milestone we'll make an announcement for, show off to labels, and use to track our overall progress towards the product's end goal. Any backwards breaking changes will have to be released as a major release, and if/when the product becomes complex with many new major releases, users should be able to switch between major versions, at least for a while.

Y is the minor release number - we've just released our first - which we're calling SLCs. Minor versions should introduce small units of functionality and never introduce backwards breaking changes. It's so satisfying to work with SLCs in mind because it keeps these releases atomic and isolated on things that matter, preventing us from getting lost in the weeds of database stuff.

Z is the patch release number - used for when we need to deploy to production a bug fix or other important tweak. I'm glad we took an extra day to form our first release, because we've avoided having to create a number of patch releases by having the extra time to check over the code and usability of things.

[g105b]

🎉 https://www.trackshift.app 🎉