3 types of users

[kkozmic]

I think it would be helpful to think of how ConventionTests is going to be used.

I think we can split the usage scenarios roughly into three categories:

1. Tests writers (people who write tests using the existing OOTB API and functionality only)
2. Conventions writers (people who create their own Conventions and ConvenionDatas
3. Extension writers (people who extend/customise CT beyond the two groups above

From my experience with other OSS libraries/tools I'd say at least 90% of people will end up in the first category, and less than 1% in the third.

When making changes/designing API I find it helpful thinking about how it will impact any of the three groups, and when I have to make trade-offs I optimise for the first group (make it super-simple for them to use) and the second (make it super simple to implement new conventions).

[JakeGinnivan]

Sounds logical. I think we have a good first cut of the v2 API. I suggest we keep iterating to try and get 2.1 out soon, or if we come up with good updates which are breaking, we start the v3 branch soon :)

[JakeGinnivan]

Adding to this

Should semver versioning for CT should only apply to user type 1, maybe type 2. But not 3. For example, changing the reporting internals, the number of users who write custom test reporters will be very minimal, should it be a major version bump?

[kkozmic]

It depends how often we want to release. I'm not too religious about it