search

djay0529 / mdanalysis

Automatically exported from code.google.com/p/mdanalysis
0 stars 0 forks source link

use semantic versioning #200

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
PreparingReleases describes the policy for versioning, i.e. how we assign 
numbers to our releases. What we currently do seems reasonably close to 
Semantic Versioning http://semver.org/ , which looks like a very solid set of 
rules to me. We could probably be stricter about how we version and I suggest 
we start using Semantic Versioning as our policy.

The biggest issue is probably going to be when we declare our API stable and 
thus release 1.0.0. My feeling is that we could do this after the next (0.8.2) 
but feedback would be useful.

Original issue reported on code.google.com by orbeckst on 30 Oct 2014 at 6:35

GoogleCodeExporter commented 9 years ago 
http://wiki.mdanalysis.googlecode.com/git/pages/quality_control/cover/index.html

Looking at the coverage report, most of the core stuff looks pretty well 
covered, the worst offenders seem to be in .analysis.  

I could go back over this and make sure that everything in .core .coordinates 
and .topology has >95% coverage is being properly tested.

Original comment by richardjgowers on 4 Nov 2014 at 9:18

GoogleCodeExporter commented 9 years ago 
Hi Richard,

Improving/solidifying test coverage would be great!

Oliver

Original comment by orbeckst on 4 Nov 2014 at 4:57

GoogleCodeExporter commented 9 years ago 
Ok, pushed lots of tests to develop, core.AtomGroup test coverage is nearly 
100%.  

Found lots of little bugs and fixed them, raised 2 issues that aren't simple 
fixes.

Original comment by richardjgowers on 19 Nov 2014 at 12:58

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision 306c943ef962.

Original comment by orbeckst on 4 Dec 2014 at 12:34

GoogleCodeExporter commented 9 years ago 
Hi devs,

we are going to use semantic versioning http://semver.org/ to label releases, 
starting with the next release, which, according to this scheme, will then be 
0.9.0. I updated PreparingReleases to reflect this.

In the longer run this will probably lead to more frequent "patch" releases 
that only fix bugs.

Oliver

Original comment by orbeckst on 4 Dec 2014 at 12:40