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
  • #1934

Closed
Open
Created Nov 01, 2017 by James Willenbring@jmwilleMaintainer

Announcement of develop-to-master promotions?

Created by: mhoemmen

@trilinos/framework How does Trilinos announce develop-to-master promotions?

I'm asking because a colleague who works on an app said that they find this out by pulling master by hand, and seeing if new commits arrived. Is that the recommended procedure? Given that #1154 is still open, users won't normally expect nightly updates of master. Thus, it might be helpful to have some kind of announcement on each promotion, like an e-mail to trilinos-users or a post on the website. Kokkos posts an issue for each develop-to-master promotion, then closes the issue when it's done.

Assignee
Assign to
Time tracking