Skip to content

List view

  • The 3.3 release will follow immediately from 3.2, but contain the items that would have otherwise substantially delayed 3.2's release. It will be strictly compatible with both 3.1 and 3.2. At the time this milestone was created, 3.3 is expected to have more comprehensive updates to parameters, form data modeling, and security configurations. These new approaches will be created alongside the older, complex approaches, which will be frozen (but still supported). The intent is for the new approaches to be incremental steps towards Moonwalk, where the older approaches will be dropped.

    Due by September 1, 2025
    1/20 issues closed
  • 3.1 patch release to incorporate any clarifications added to 3.2.0. The due date should stay in sync with the 3.2.0 milestone.

    Overdue by 2 month(s)
    Due by April 1, 2025
    18/22 issues closed
  • The 3.2 release is intended to be small, incremental release, strictly compatible with 3.1. It will prioritize a quick schedule, with a plan of immediately proceeding to a slightly larger incremental 3.3 to address issues that would have significantly delayed 3.2.

    Due by August 1, 2025
    112/130 issues closed