Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v1.6.0 #198

Closed
25 tasks done
tobolar opened this issue Jun 20, 2023 · 1 comment
Closed
25 tasks done

Release v1.6.0 #198

tobolar opened this issue Jun 20, 2023 · 1 comment
Assignees
Milestone

Comments

@tobolar
Copy link
Collaborator

tobolar commented Jun 20, 2023

  1. Git

    • create new branch
  2. Modelica and an text editor
    a. Check current year and version number in

    • file "LICENSE".
    • file "README.md".
    • file "libraryinfo.mos".

    b. Release Notes (PlanarMechanics.UsersGuide.ReleaseNotes)

    • check version number and date.
    • check whether all relevant changes, updates, bug fixes of the version are noted.

    c. Check/update in library's package.mo the following annotations

    • version.
    • versionDate - shall be "YYYY-MM-DD".
    • dateModified - shall be "YYYY-MM-DD".
    • conversion from the previous version (use noneFromVersion="A.B.C", if no conversion needed).
  3. Git

    • commit changes: "Version release preparation steps"
    • push changes
  4. GitHub: generate release; follow the documentation on https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository.

    • tag v1.6.0-alpha
    • name Version 1.6.0-alpha (2023-06-21)
    • target is the release branch.
    • description "Release 1.6.0-alpha of the PlanarMechanics library" or similar. Optionally, a content of library's Release notes can be copied here.
    • check "Set as a pre-release"
    • generate Draft release to perform regression tests prior to publication.
  5. Modelica: perform tests

    • download release zip-archive, unpack
    • perform tests
  6. GitHub

    • if tests are successful, publish the draft release (button Publish release).
  7. Git

    • repeat the abovementioned steps for "beta" (optional) and "final" release.
  8. Text editor

    • file "LICENSE": update link to the latest release.
  9. Git

    • merge release branch into master.
    • delete release branch(es).
@tobolar tobolar added this to the next_MINOR-version milestone Jun 20, 2023
@tobolar tobolar self-assigned this Jun 22, 2023
@tobolar tobolar pinned this issue Jun 22, 2023
@tobolar
Copy link
Collaborator Author

tobolar commented Sep 12, 2023

Released: v1.6.0

@tobolar tobolar closed this as completed Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant