Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #1740

Closed
Open
Created Sep 15, 2017 by James Willenbring@jmwilleMaintainer

Discuss, refine, and document subteam/subproject development branches

Created by: bartlettroscoe

CC: @dridzal, @jwillenbring, @maherou

Description:

This story is to document a discussion about the subteam/subproject development workflow that I helped the ROL team to set up and how to generalize it and document it for the benefit of other Trilinos development subteams.

Definition of Done:

ToDo: Fill in once discussion is farther along so we can better scope this out

Tasks:

  • Have initial discussion ...
  • Decide on concrete "definition of done" and set of tasks to complete ...
  • ???
Assignee
Assign to
Time tracking