search

duckdb / community-extensions

https://duckdb.org/community_extensions
148 stars 27 forks source link

Road to v1.1.0 #85

Closed carlopi closed 2 months ago

carlopi commented 3 months ago

Hi all (@hafenkran, @lmangani, @rustyconover, @Dtenwolde, @JAicewizard, @arjenpdevries, @isaacbrodsky, @ywelsch, @pdet, and @Maxxen)!

We are getting very close to the next release, and we have now a mechanism for testing community extensions versus the latest duckdb branch, using that as approximation of the status of the release.

Recent changes

Changes that happened recently:

This pieces together should allow extensions developers/maintainers to check whether extensions are compatible with changes that happened in DuckDB between version v1.0.0 and now.

Once v1.1.0 will be released, as part of the release processes ref_next (if present) would become ref, and extensions built and (when successful) published on v1.1.0.

Testing results

extension detected problem status
bigquery compilation error
chsql compilation error
lindel compilation error fixed via https://github.com/duckdb/community-extensions/pull/86
prql compilation error fixed in https://github.com/duckdb/community-extensions/pull/89
scrooge test failing

Other extension looks to be working fine. Complete results are at https://github.com/duckdb/community-extensions/actions/runs/10619930977/job/29438643392

How to fix detected incompatibilities

quack, the demo extension, had also a problem when tested vs main duckdb, so that now also work as a demo of the intended workflow:

  1. problem is detected while compiling vs main
  2. in the extension repository the problem is fixed (and potentially duckdb submodule is updated to a recent duckdb commit)
  3. a PR is sent to add a ref_next (or possibly changing ref, if the changes are backward compatible) (see the commit: https://github.com/duckdb/community-extensions/commit/dc86e730709ce60245ee68ddde1e062e01161bb8)
  4. CI tests this, and once merged the extension is properly set

We are super grateful for the involvement, and we plan on iterating on this to make it even smoother, feedback is very welcome.

Thanks everyone!

carlopi commented 3 months ago

Minor update: DuckDB v1.1.0 is now penciled in for next Monday, 9th of September: https://duckdb.org/docs/dev/release_calendar#upcoming-releases

carlopi commented 2 months ago

Update: DuckDB v1.1.0 is out, and most extension have been build / updated yesterday.

It was the first change in version, and I think it went relatively smooth.

I am aware of 3 extensions not successfully working on v1.1.0 at the moment:

If assistance is welcome, please do ping.

carlopi commented 2 months ago

I guess we are set, thanks, closing this.

Now up to bugfix in v1.1.1, currently planned for next Monday