Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • SMTK SMTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 166
    • Issues 166
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 39
    • Merge requests 39
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CMBCMB
  • SMTKSMTK
  • Issues
  • #210
Closed
Open
Issue created Nov 19, 2018 by T.J. Corona@tjcoronaReporter

Break sessions out of SMTK core and into plugins

As more SMTK sessions and extensions are created, it is difficult to track how modifications to SMTK core will affect plugins and extensions that are not part of the SMTK project. One step towards fixing this issue is to extract non-SMTK core components out of SMTK and into separate repositories. This way, our testing of these components will be on equal footing with the testing of other out-of-core plugins/extensions.

Assignee
Assign to
Time tracking