You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@johcarter I agree with removing the suggested v1 specs for cyber and liability. In regards to reviewing the current documentation, where is best to do this? As discussed, the updating of the documentation for cyber and liability will likely occur during the three month RC release window. So is the RC branch the best place to update documentation?
Thanks @MattDonovan82 , I suggest waiting until after the repo restructure and final release candidate is ready, and then perhaps branching off that for the documentation updates. @sambles might also have a view on how best to go about this.
johcarter
changed the title
Update general documentation for Cyber and Liability
[Specification] Update general documentation for Cyber and Liability
Aug 21, 2024
This is on my list for the next couple of weeks. Do you think we still need the pdf docs? If the 'read me' get updated these pdf seem unnecessary? @johcarter
Description
The documentation for Cyber and Liability needs to be reviewed and updated to reflect the integration into the main spec.
The text was updated successfully, but these errors were encountered: