Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/19823.doc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Document that the SQLite version included in Ubuntu LTS, aside from ESM-only versions, is included in our support policy.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to explain the context here for where this is spawning from.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not right sure how you mean; the context was whether I can use exciting new stuff in sliding sync, but it doesn't really feel worthwhile putting that in the changelog.
IMO the support policy is standalone and would be valid no matter what I was working on at the time to query.

But maybe you had something else in mind?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Explain it in the issue description / in this thread

IMO the support policy is standalone

Yes, but it's good to understand why we're making this change without having to look at the internal document to figure out the conversation which doesn't even encompass the entire context. For example, I just cross-linked some more conversation in the doc. And even that isn't fully linked to the relevant issues/PRs (#19452 and #19487)

Given you were the original author, I think you could give a great summary.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep that makes sense, so the motivation for wanting to not do this was that for support for SQLite's JSON operators, which is currently not present in the SQLite version found in Ubuntu's oldest supported LTS.

The JSON operators were used in some of the sticky events work (thank you for reminding me I opened #19452).

Our ruling was that we should support Ubuntu oldest LTS equally to Debian oldstable, so support the oldest of the two versions from those.

That makes some kind of sense as it would be difficult to do otherwise without dropping support for that version of Ubuntu altogether, given if we kept publishing packages intended for use with Postgres, there's a risk that an innocent sysadmin would update their SQLite deployment without realising that it is no longer supported.

2 changes: 1 addition & 1 deletion docs/deprecation_policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ people building from source should ensure they can fetch recent versions of Rust

The oldest supported version of SQLite is the version
[provided](https://packages.debian.org/oldstable/libsqlite3-0) by
[Debian oldstable](https://wiki.debian.org/DebianOldStable).
[Debian oldstable](https://wiki.debian.org/DebianOldStable) or the oldest maintenance/security-supported [Ubuntu LTS](https://endoflife.date/ubuntu) (Ubuntu versions with only Expanded Security Maintenance are not included).


### Context
Expand Down
Loading