Need to commit documentation to master #151
Labels
documentation
Improvements or additions to documentation
post release
issues that will be fixed after the release
The UFS MRW App v1.0 User's Guide is located at: a) branch ufs-release-v1.0, b) tag ufs-v1.0.0, c) branch documentation (branch of master). Can the documentation be committed to the master branch so it is part of the main code? Are there any concerns about that? Should I submitted a PR?
And for continued development of documentation, I suggest we continue to use branch documentation (and commit to public release branch or master once we have a chunk of documentation completed). Let me know if there are other perspectives.
The text was updated successfully, but these errors were encountered: