ABPSC 3.4b1 NO IDEA Avatar
  1. OMG Issue

ABPSC — The Specification Lifecycle lacks transparency

  • Key: ABPSC-40
  • Status: open  
  • Source: 88solutions ( Mr. Manfred R. Koethe)
  • Summary:

    We need a timeline for each specification and submission, indicating the actual state a submission/specification is in at a given point of time to allow traceability.

    While being a submission, revised submission dates provide some information about its state, same is true while in FTF. But after that are several steps until the spec ends up in the Formal Specification Catalog, and sometimes it takes significant time for these last steps, and nobody can give an answer why it takes so long and what can be done. A simple "State Machine Display" would be very helpful to see the state a document is in, and what could be done to help accelerate its processing.

  • Reported: ABPSC 3.3 — Tue, 15 Feb 2022 03:45 GMT
  • Updated: Tue, 15 Feb 2022 03:45 GMT