dbt-fusion changelog entries in release notes is confusing

[joshuataylor]

According to https://docs.getdbt.com/docs/fusion/about-fusion?version=2.0&name=Fusion

Fusion is written in Rust and has a native understanding of SQL across multiple engine dialects. Fusion will eventually support the full dbt Core framework, a superset of dbt Core capabilities, and the vast majority of existing dbt projects.
dbt Core v2 is the open-source Apache 2.0 foundation that Fusion builds on. dbt Core v2 delivers a faster, Rust-based runtime for dbt projects; Fusion extends it with SQL comprehension, column-level lineage, and richer development capabilities. It is currently in alpha.
dbt Core v2 is published as Apache 2.0 open source in the dbt-core repository, the single canonical home for issues and contributions. Fusion, which includes the dbt Fusion engine’s richer capabilities, is proprietary.

Reading the https://github.com/dbt-labs/dbt-core/releases/tag/v2.0.0-alpha.3 is confusing. If dbt-fusion release notes are going to be included in dbt-core, can it please have its own seperate section.

If a dbt-fusion feature is also in dbt Core (a crate under dbt-core, I guess), it should be listed as such.

Mixing in dbt Fusion changes into dbt Cores changelog is really confusing, especially figuring out if a change was actually in dbt Core or not.

[tauhid621]

Complete fusion changelog are present in a separate file.

We will improve the core v2 changelog to avoid fusion naming.

[joshuataylor]

I understand that there is another file.

To confirm:

1. CHANGELOG-fusion.md is from what I understand, for the dbt Fusion binary itself.
2. CHANGELOG.md is for dbt Core, this repository, with changes that were made in this repository.

So for CHANGELOG.md with fusion (or dbt-fusion), these are changes which were made in dbt Core to support a dbt Fusion feature?

How am I supposed to understand what "[dbt-fusion] DuckDB: read-write Horizon and Unity (Iceberg REST) catalogs via duckdb 1.5.4 / duckdb-iceberg#1017 write-compat ATTACH options (stage_create_tables, disable_multi_table_commit, etc.). Upgrades the read-only support from the base PR." is, or which issues (if any exist here, I guess) or commits correlate to it?