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
Given our emphasis on the monorepo, having documentation in the mev-commit repo would allow us to modify the documentation along with feature implementation and modification. A strategy will be needed to ensure that docs don't reflect features sets that are yet to be released. We can follow an approach that ensures we tag documentation that is net new with to be released tags, and in the release process, remove these tags.
Given the fast moving development, this will support tight correlation between the docs and mev-commit stack, and remove need for redundant operations function focused on aligning documentation.
The text was updated successfully, but these errors were encountered:
ckartik
changed the title
Merge Docs into monorepo
Merge documentation into monorepo
Jul 30, 2024
Given our emphasis on the monorepo, having documentation in the mev-commit repo would allow us to modify the documentation along with feature implementation and modification. A strategy will be needed to ensure that docs don't reflect features sets that are yet to be released. We can follow an approach that ensures we tag documentation that is net new with to be released tags, and in the release process, remove these tags.
Given the fast moving development, this will support tight correlation between the docs and mev-commit stack, and remove need for redundant operations function focused on aligning documentation.
The text was updated successfully, but these errors were encountered: