Documentation for PISM, the Parallel Ice Sheet Model

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
committing [2017/02/21 21:02]
Ed Bueler
committing [2017/02/21 21:03] (current)
Ed Bueler [Best practices]
Line 25: Line 25:
      make test</​code>​ Proposing and building additional fast-running software tests for the dev branch is //​strongly//​ encouraged.      make test</​code>​ Proposing and building additional fast-running software tests for the dev branch is //​strongly//​ encouraged.
    - Posting a task (= an [[https://​github.com/​pism/​pism/​issues?​labels=task&​sort=created&​direction=desc&​state=open&​page=1|issue with a ''​task''​ label]]) describing what you plan to do is always reasonable before doing it.  You can assign the task to yourself. ​ Creating a ''​git branch''​ with a name like ''​issue-XX''​ or ''​new-XX-model''​ is a good idea if you need to test before committing. ​ If you are hoping a UAF developer will do something to help you then you might mark it as a [[https://​github.com/​pism/​pism/​issues?​direction=desc&​labels=feature_request&​milestone=&​page=1&​sort=created&​state=open|''​feature request''​]] instead of a ''​task''​.    - Posting a task (= an [[https://​github.com/​pism/​pism/​issues?​labels=task&​sort=created&​direction=desc&​state=open&​page=1|issue with a ''​task''​ label]]) describing what you plan to do is always reasonable before doing it.  You can assign the task to yourself. ​ Creating a ''​git branch''​ with a name like ''​issue-XX''​ or ''​new-XX-model''​ is a good idea if you need to test before committing. ​ If you are hoping a UAF developer will do something to help you then you might mark it as a [[https://​github.com/​pism/​pism/​issues?​direction=desc&​labels=feature_request&​milestone=&​page=1&​sort=created&​state=open|''​feature request''​]] instead of a ''​task''​.
-   - Posting bug reports is always worthwhile! ​ You can email to [[help@pism-docs.org]], but even better is to post a bug report at the github site (i.e. an [[https://​github.com/​pism/​pism/​issues?​labels=bug&​sort=created&​direction=desc&​state=open&​page=1|issue with a ''​bug''​ label]]). ​ See [[reporting_bugs|How to report a bug]].+   - Posting bug reports is always worthwhile! ​ You can email to [[uaf-pism@alaska.edu]], but even better is to post a bug report at the github site (i.e. an [[https://​github.com/​pism/​pism/​issues?​labels=bug&​sort=created&​direction=desc&​state=open&​page=1|issue with a ''​bug''​ label]]). ​ See [[reporting_bugs|How to report a bug]].
    - Please post a bug report even if you already know how to fix it.  That way other developers may see that related matters are affected.    - Please post a bug report even if you already know how to fix it.  That way other developers may see that related matters are affected.
    - When in doubt about adding spaghetti code because of existing/​bad PISM design choices, please consider posting a task asking UAF developers for abstraction or modularization. ​  You might be asking us to do something we want to do anyway, but it raises the priority.    - When in doubt about adding spaghetti code because of existing/​bad PISM design choices, please consider posting a task asking UAF developers for abstraction or modularization. ​  You might be asking us to do something we want to do anyway, but it raises the priority.
committing.txt ยท Last modified: 2017/02/21 21:03 by Ed Bueler
© 2016 by PISM | webmaster