Skip to content

[Content] Extra process description on Idea Draft / Tech Design updates #7

@nemuiikiryou

Description

@nemuiikiryou

✏️ What’s the context or problem?

Given my personal experience, there are some times where the tech design, primarily, will be updated AFTER all parties have signed it. Either because things needed to change during development, or new things were requested to be added or removed. This isn't specified AFAIK.


💡 What would you like to see written?

It'd be great to have a process on how to handle those updates, if a new Tech Design doc would be needed (and new signatures required), or if a simple update and notice to relevant parties would be enough.

Not sure of the final process, but these are some I had in mind

  • Create a changelog/timeline section of signatures and re-request on the same document when needed, and from the interested parties.
  • Deprecate the previous signed document and request for a new signature on each change on a new document
  • Continue as-is and simply update the document, notify the relevant parties but no new signature required.

🧭 Any alternatives or related pages?

Maybe a sub-section or even a just a couple paragraphs on the Project Lifecycle section


⏱️ Urgency (if any)

No urgency

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions