Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

  • keep test case doc and test script in a separate branch that never merge with the master. Test case doc needs not be browsable. Do the same as User Guide…keep Word Doc?

  • User Guide

    • Use another repo, i want user guide to be browsable without score deployment, so it should be Github Pages. I looked at Gitbook a bit. I am not sure if I want the user guide content to be hosted somewhere else not inside the application. In interest of time, we can keep user guide with the application for now.  We can look into other benefits Gitbook may bring later. At this point, we upload the Word doc to a Wiki page and the generated HTMLs to the repo. If Sakis can help me move User Guide to Gitbook b/f he leave, I think I might be fine. I don’t know how to sync the release though.

    • User Guide needs to be in another repo because I want Contribution Guide to be browsable as well but I don’t want Contribution Guide to be included in the release. But GitHub Pages can only point to one root.

  • Contribution guideline should be browsable as well, but don't want it in the release. So it should be Github Pages as well. Contribution Guide should be in a separate branch call GithubPages branch. ReadMe file can have a link to that. 

  • How about the Release Detail page? Need to be browsable. Move content of the Release Detail page into ReadME? Another option is to still keep it as wiki. The content is so far cumulative and typically written at the end when the release is already done, it doesn't benefit much from the version control system. 

  • No labels