Welcome back to this blog series on Crunchy Postgres via Automation (CPA). We’re doing something a little different today; we’re going to discuss something that is merged in development but isn’t released yet: package pinning.
Prior posts in this series have discussed the Crunchy Postgres via Automation product, the team behind it, and some of our processes and tooling. This week, we’re going to dive into the collection itself.
read moreAs previously mentioned in this Crunchy Postgres via Automation series, we now use a Bill of Materials (BoM) to ship tested-together versions of the components that comprise the CPA product. Accordingly, when the PostgreSQL Global Development Group (PGDG) releases new versions of PostgreSQL as they did yesterday, we have to iterate our BoMs to include these releases.
read moreContinuing our series on Crunchy Postgres via Automation, we’re here this week to discuss the highlights of our latest release line, v2.2. If you haven’t already, you can catch up on the differences between v1 and v2 and then come back, we’ll wait for you.
read moreWelcome back to our blog series discussing Crunchy Postgres via Automation (CPA) and the team behind it. This week, we’re going to talk about the tooling used by the team and discuss some of the agile-lite processes we’ve adopted.
read more