Development Workflow

Jump to bottom

Dom Heinzeller edited this page Jan 22, 2019 · 19 revisions

Table of Contents

Open an Issue
Develop new feature or bug fix
Test! Test! Test!
Submit Pull Request
Code Merged to Master
Post-merge Testing

Open an Issue

All development, whether for a new feature, bug fix, re-engineering task, or documentation or data update, MUST begin with opening an issue. An open issue allows for transparency, developer and community input, assignment of the task, and progress tracking.

To open an issue, follow these steps

Develop new feature or bug fix

Coding should take place in a branch, or ideally, in a fork

Test Test Test

NEMSfv3gfs regression testing on Cheyenne (work in progress)

Prerequisites:

access to public repositories ccpp-framework, ccpp-physics and FMS (all under http://www.github.com/NCAR)
access to private repositories FV3, NEMS, NEMSfv3gfs (all under http://www.github.com/NCAR)
password-less GitHub access via https from Cheyenne

Submit Pull Request

Code Merged to Master

Post-merge Testing