0

We use the following scheme for versions:

major.minor.build

where

  • each breaking change increments major (resets minor)
  • each new feature increments minor
  • each commit increases build

Is there a way/tool to automatically check if there is

  • no breaking change (e.g. changing interface) when there's only a change in minor
  • no new features (e.g. no new interfaces) when there's only a change in build ?

A tool that automatically creates major/minor would also be ok.

Onur
  • 5,017
  • 5
  • 38
  • 54
  • 1
    You'd need an AI to detect whether there are new features or not. – dymanoid Jun 22 '16 at 09:22
  • I would say no. Even an unchanged interface signature can have a changed implementation that changes behaviour. A valid call in the previous version now throws an execption. No interface change but still a breaking change. If you have a contracts based application that might be a good indicator if they change but that would still be far from perfect. – Ralf Jun 22 '16 at 09:24
  • Rethinking it. Unittests are what you are asking for ;) – Ralf Jun 22 '16 at 09:26
  • I found another question (http://stackoverflow.com/a/652459/1254743) and the solution (NDepend) looks promising. Especially since I can define the rules. Checking itself may be only on the CI, but that's fine. – Onur Jun 22 '16 at 09:59

0 Answers0