Patterns have a different level of maturity. At the moment we are keeping track of this via some manual activity (e.g., table in an md file) and little scripts creating the pattern tables in the main readme file.
Everytime an important change is done in a pattern, those pattern table would only be changed if the table in the specific pattern review issue is also modified.
This is thus difficult to maintain.
Proposed changes
However, when we do a pattern review we act on the json files of that pattern anyhow, so we could control there the version by adding a version field.
Problem statement
Patterns have a different level of maturity. At the moment we are keeping track of this via some manual activity (e.g., table in an md file) and little scripts creating the pattern tables in the main readme file.
Everytime an important change is done in a pattern, those pattern table would only be changed if the table in the specific pattern review issue is also modified.
This is thus difficult to maintain.
Proposed changes
However, when we do a pattern review we act on the json files of that pattern anyhow, so we could control there the version by adding a
version
field.@SoheilKhodayari: what do you think?