Talk:Development Practices

Component versioning

If we specify that only major releases can contain breaking/backwards incompatible changes, do we also specify that each such version must change the major version part?

Currently it just seems to me that we are more into doing breaking changes while only incrementing the minor part of the version, which is obviously desirable from the developer's point of view when a component is in early stages of development. Otherwise developing components will quickly end up with version 10.0.0.

Version system and assumptions

OSGi specification states version is major.minor.service[.qualifier]. API breakage is allowed between major versions.

Issues:

Service is redundant as qualifier replaces it and is automatic

As there is a lot of API breakage within Incubating plugins, there would be a lot of major version updates