Versions Compared

Old Version 30

changes.mady.by.user Claudia Malzer

Saved on

compared with

New Version 31

changes.mady.by.user Ethan Freestone

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
titlePre-release Info

For each module, update changelog to reflect changes since last release:

  1. Check release ticket for corresponding linked issues since last release date
  2. Check filter page for each component
    1. update resolutionDate 
    2. update component
  3. Check commit history since last release (from example)

...

  1. FIRST: stripes-erm-testing

  2. SECOND:

    1. stripes-erm-components

    2. ui-handler-stripes-registry
  3. THIRD: ui-service-interaction
  4. FOURTH (in any order)
    1. ui-plugin-find-agreement
    2. ui-plugin-find-eresource
    3. ui-plugin-find-license
  5. FOURTH FIFTH (in any order)
    1. ui-dashboard

    2. ui-agreements

    3. ui-licenses

    4. ui-local-kb-admin

    5. ui-erm-comparisons
    6. ui-serials-management

We follow the FOLIO version-numbering scheme to version our apps/plugins. This is the same as the official semver documentation.

...

  1. raise a PR when necessary
  2. set the related Jira ticket from DRAFT to OPEN to indicate they are ready for any dependency changes and release completion

At this point the modules are ready to be released

...