LoginSign Up
← Back to all sparks
V

Virto Commerce

E-COMM
Velocity6.3

Open source B2B commerce platform on .NET

virtocommerce.com ↗

Three maintained branches, one cache bug, and very little else moving.

ecommercecachingpatch releasesmulti-branch maintenanceaccess control
◆Current state
The feed is a patch stream across three concurrently maintained branches — 3.1007.x, 3.1039.x, and 3.1058.x — with the same defect frequently released to all three within minutes. Entries are single-line bug references with issue numbers and no narrative. Cache correctness dominates the window: corruption on update, stale reads from a late change-token capture, and a new content-hash scheme for cache keys.
◆Where it's heading
Engineering attention is concentrated on the caching layer and on access control, not on new commerce capability. The parallel-branch release pattern indicates a customer base pinned across several versions, which constrains how much can change in any one release and explains a feed made almost entirely of backported fixes.
◆Prediction
Expect continued triplicate patch releases as fixes are backported across the three branches, with further cache-layer follow-ups to the streaming content-hash change.

◆Recent moves

  1. 4d ago

    Fixes null credential fields (3.1059.0)

    A single null-handling fix for credential fields on the head branch. Routine defect work, consistent with a feed that is almost entirely backported patches.

    View source ↗
  2. 11d ago

    Fixes user cache corruption on update (3.1007.24)

    The oldest maintained branch gets the user cache corruption fix, released within two minutes of the same fix on the other two branches.

    View source ↗
  3. 11d ago

    Fixes user cache corruption on update (3.1039.9)

    The middle branch's copy of the same cache corruption fix. One defect, three simultaneous releases.

    View source ↗
  4. 11d ago

    Fixes user cache corruption on update (3.1058.0)

    The head branch's copy of the cache corruption fix, closing out the third of three identical releases.

    View source ↗
  5. 12d ago

    Streaming JSON content hash for cache keys (3.1057.0)

    A streaming JSON content hash for cache keys — the only structural change in the window, and the piece of cache work that alters behaviour rather than repairing it.

    View source ↗
  6. 14d ago

    Capture cache change token before load (3.1056.0)

    Captures the cache change token before the load rather than after it, closing a stale-read window. Part of the same cache-correctness push.

    View source ↗