Workflow for Reviewing Proposed Changes

After each proposed change

1. Local jurisdictions propose changes via the 'pull request' mechanism
2. Repository Owners (Marshall/Landon) field change
3. assign change to appropriate jurisdictional rep.
4. move change to In Review milestone
5. Jurisdictional rep follows up with any missing information

Weekly review

1. All changes are merged into the proposed branch
2. GeoJSON files with changes are merged into a single shapefile for desktop GIS review/analysis
3. Changes are flagged for preliminary approval or rejection
4. GDOT asked to provide comments on any changes
5. Brief staff meeting held to discuss any cross-jurisdictional or other noteworthy changes
6. Issues are updated accordingly (approved, rejected, etc.)

Final review

1. Change submission period is closed
2. Final desktop review of changes is performed
3. Final shapefile with proposed changes submitted to GDOT for full review