Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to commit documentation to master #151

Open
ligiabernardet opened this issue Jun 2, 2020 · 5 comments
Open

Need to commit documentation to master #151

ligiabernardet opened this issue Jun 2, 2020 · 5 comments
Assignees
Labels
documentation Improvements or additions to documentation post release issues that will be fixed after the release

Comments

@ligiabernardet
Copy link
Collaborator

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.

@ligiabernardet
Copy link
Collaborator Author

@arunchawla-NOAA
Copy link
Collaborator

All documentation and release updates should go back to the develop repos after the release. We should confirm that for all the repos

@ligiabernardet
Copy link
Collaborator Author

For this App. is there a code manager to update the

@ligiabernardet
Copy link
Collaborator Author

Closed by mistake. Apologies. Meant to say that we will submit a PR to develop to commit the v1.0 documentation.

@arunchawla-NOAA arunchawla-NOAA self-assigned this Aug 10, 2020
@arunchawla-NOAA
Copy link
Collaborator

I will assign a code manager for this app

@ligiabernardet ligiabernardet added documentation Improvements or additions to documentation post release issues that will be fixed after the release labels Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation post release issues that will be fixed after the release
Projects
None yet
Development

No branches or pull requests

2 participants