My Notes
Release cadence/support
- At least a year of support for LTS releases
- Calendar versioning?
- What about marketing?
- Switch later, maybe at version 9
- 3 releases per year- every four months
- 3.0 is first LTS release
- Can releases slip?
- Revert features that cause issues
- Release can slip by 1 week if there’s a very good reason
- Aljaz: releases that slip shorten the following release cycle
- Schedule
- 2.5 months development to merge all major stuff
- Beta for 1 month
- Small features can come during the beta
- Need a roadmap on GitHub to expose RFCs for upcoming features
- Cloud support to track with LTS
Paid instances support old versions (to run; not with fixes)- Cull old versions in free tier
- Force upgrade 6 months after that version’s support ends
- applies to free and paid
- may need to deprecate free tier sooner
- need more data to understand tradeoffs
4.0 work
- full-text search
- extension support (postgis)?
- refactor config?
- start repaying technical debt?
- start working on functions
- make return annotation optional
- allow dml by inlining functions at call site
- (functions essentially become Elvis’ “callable” aliases)
Next work
Meeting Notes