search

FlexTradeUKLtd / jfixture

JFixture is an open source library based on the popular .NET library, AutoFixture
MIT License
105 stars 22 forks source link

Update version to latest SNAPSHOTs #49

Closed rsingh-flx closed 5 years ago

rsingh-flx commented 5 years ago

Local development is difficult without using valid SNAPSHOT versions as this will pollute the local maven repository

richkeenan commented 5 years ago

Thanks @rsingh-flx, the reason why the version isn't set on master is that we don't know what the next version will be - if we introduce a major change the major version (first number) will increase, if it's a bug fix then the patch will increase (third number). So basically I just leave it and only set the version when tagging a release

It sounds like this is causing problems so I'm happy to change it

TWiStErRob commented 5 years ago

@richkeenan that's a common problem, most of the time what I saw is that the assumption is a minor change (pretty good assumption), so after each (x.y.?) release there's an (x.y+1-SNAPSHOT) then at release they would set it to whatever is appropriate, if it was a patch (x.y.z), if it was minor just remove the SNAPSHOT, and if it was major then it's a bigger work anyway, so one would just change the snapshot version when introducing the first major change. With this system, in all cases, the SNAPSHOT version will be the latest under-development version and it also follows semantic versioning for snapshots.

richkeenan commented 5 years ago

@TWiStErRob thanks, that's good explanation - also glad I'm not the only one who thought it was a bit weird!