Create develop-WaterQuality for work on non-hydrolic modules
#29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@rheaphy, it seems that we might need to park all the in-development model modules from commit LimnoTech@989a096 into a feature branch, so that we use the
developbranch to first work on our other priorities to merge intomasterwhen complete.So this PR is part of creating that structure, so that we can use a Feature Branch workflow similar to:

I created this
develop-WaterQualityfrom @rheaphy'sDevelopmentbranch, and this PR merges in all the commits that @rheaphy since made tomaster.I'm thinking that we might use the
developbranch to work on these first set of tasks in our Collaborative Work Plan:Meanwhile, we might use this
develop-WaterQualitybranch to work on these development objectives, perhaps even in parallel.We'll continue to merge into all updates from
developormasterinto thisdevelop-WaterQuality.cc: @PaulDudaRESPEC, @steveskrip, @ptomasula