Skip to content

v3.0: rename Kuestenlogik.Bowire.* -> Bowire.* (assemblies, namespaces, NuGet ids) #421

Description

@thomas-stegemann

Decision

For the v3.0 breaking-change release, rename the Bowire .NET surface from Kuestenlogik.Bowire.* to Bowire.* — assembly names, root namespaces, and NuGet package ids (e.g. Kuestenlogik.Bowire.Ai → Bowire.Ai). This is Option A (full rename), chosen over "package-id only" (Option B) and status quo.

Why

  • Removes an existing inconsistency: the sibling repos are already Bowire.* (Bowire.Protocol.Amqp, Bowire.Sdk.Go, Bowire.Protocol.Kafka, Bowire.Templates, Bowire.Bootcamp) and the CLI assembly is already bowire; only the core is Kuestenlogik.Bowire.* — the odd one out. Bowire.* is the consistent end state.
  • Brand + discoverability: product is Bowire, domain bowire.io, CLI bowire. The vendor prefix hides the product name and adds friction on NuGet search + in every using.
  • Shorter names / shallower paths (Windows path-length matters given the current tree depth).
  • Positions Bowire as a standalone Apache-2.0 product, not "a Kuestenlogik thing".

Accepted trade-off: diverges from the org convention Kuestenlogik.<Product>.* (Surgewave/Sealbolt). Justified because Bowire is the most community-facing/standalone product.

Scope of the break (why v3.0 only)

  • Every assembly name, root namespace, using, InternalsVisibleTo, and NuGet package id changes.
  • Plugins: PluginManifestProbe.IsContractCompatible gates on the plugin's AssemblyRef to Kuestenlogik.Bowire (same-major). Renaming the core assembly to Bowire invalidates every existing .NET plugin — all Bowire.Protocol.* siblings must rebuild against the new core. Sidecars are unaffected (JSON-RPC, no assembly ref).
  • NuGet identity can't be renamed in place: publish new Bowire.* packages; mark the old Kuestenlogik.Bowire.* ids deprecated with an "alternate package" pointer.

Migration plan

  • Reserve the Bowire. NuGet ID prefix now (no-regret; prevents squatting) — tracked separately, do before 3.0.
  • Mechanical rename across the main repo: assembly names, RootNamespace, namespaces, using, InternalsVisibleTo, <PackageId>, project/folder names, .slnx, Directory.Build.props.
  • Update the plugin-compat check + any hardcoded Kuestenlogik.Bowire assembly-name strings (PluginManifestProbe, registry, sidecar hostVersion/expectedProtocolId unaffected).
  • One transition release: ship Kuestenlogik.Bowire.* 3.0 shim packages with [assembly: TypeForwardedTo] to the new Bowire.* assemblies, so embedders get runtime type resolution while they do a find/replace Kuestenlogik.Bowire → Bowire on their usings. (Namespaces still change → source-breaking; forwarders only cover runtime binding.)
  • Rebuild + re-tag every sibling Bowire.Protocol.* / SDK repo against the renamed core (release cascade).
  • Sweep docs, Bootcamp, Samples, dotnet new Templates, and the marketing site code references from Kuestenlogik.Bowire.* → Bowire.*.
  • Deprecate old NuGet packages with alternate-package metadata; update install docs.
  • CHANGELOG / release-notes: prominent migration section (docs/release-notes/v3.0.0.md).

Acceptance

  • Core + all in-repo projects build/publish as Bowire.*
  • Plugin-compat check targets the new assembly; sibling plugins rebuilt via cascade
  • Transition shim packages (type-forwarders) shipped for one release
  • Old NuGet ids deprecated with alternate-package pointers
  • Docs / bootcamp / samples / templates / site swept
  • Bowire. NuGet prefix reserved

Related

Metadata

Metadata

Labels

No labels
No labels

Projects

  • Status
    Backlog

Relationships

None yet

Development

No branches or pull requests

Issue actions