Versions Compared

Key

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

...

Note

The subject of the commit message should start with the Jira ticket number, in the appropriate Jira project corresponding to the repository at hand.

  • All code changes must belong to a Jira ticket, even if it's "only" considered refactoring. If a ticket does not exist in the current project, please create it and link it as appropriate.
  • Please avoid cross-referencing Jira projects from other repositories. This makes it hard to track changes with the changelog, and know when a module should effectively be released, or know in which ticket/version an issue has been introduced or fixed.
  • Commits only updating internal versions in webapps/bundles may use the motivating Jira ticket from that module, or simply no prefix at all, e.g. "Bump personalization to 2.1-SNAPSHOT".
  • QA prefix may be used, but exclusively for 100% cosmetic changes, e.g. formatting, Javadoc.

...