Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #403

Closed
Open
Created Dec 02, 2019 by snuverink_j@snuverink_jDeveloper0 of 1 task completed0/1 task

Description of the procedure to release a new version

The following discussion from Manual-2.1!23 should be addressed:

  • @kraus started a discussion: (+1 comment)

    A new version of the binary of Opal and in consequence of the manual as well. A few items that need to be done:

    • increase the version string in CMakeLists.txt
    • setup a repository for the new version of the manual
    • setup the regression-tests to run the new version
    • add links to the binaries in the wiki
    • compile the change log and publish it in the wiki
    • correct (the links to) the example input files, field maps aso in the manual
    • write e-mail to mailing list

    I guess there's a lot more to be done and as long as we don't write these steps down in a procedure that we follow we'll always have problems. We just had two e-mails from potential users of Opal that tried to run examples from the manual. Unfortunately they weren't updated when we released new versions.

\cc @gsell

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking