Den 26. aug. 2013 kl. 15:24 skrev Andreas Lauser: > Hi, > > this issue appeared in PR 335 for opm-core, but it is a more "political" > problem, so I push it to the mailing list: What version should be used for > the > master branches? As far as I can see, there are three alternatives: > > (1) keep the version number of the previous release for the master branch. > That's the current OPM approach > (2) after a release, immediately increase the version number of the master > branch to the one of the next release (the current Dune approach) > (3) after a release, use the version that release for the development branch, > but increment the point release level to something unrealistically high for > the normal maintenance releases (99, say). This is the approach KDE takes. > > Since (1) and (2) come with severe compatibility issues which are hard to > spot, I'm inclined to (3), but this is approach also has some conceptual > impurities (i.e., misuse of the point release level)…
Our version numbers are more like strings than number sets, so can we use something like (3) with a string instead of a large number? For example: 2013.09-nextrelease Otherwise, I think what we do now (1) would be the least confusing. Atgeirr > > Are there any options? Should the current state of affairs be changed after > 2013.09? > > cheers > Andreas > > -- > A programmer had a problem. He thought to himself, "I know, I'll solve it > with > threads!". has Now problems. two he > -- Davidlohr Bueso_______________________________________________ > Opm mailing list > [email protected] > http://www.opm-project.org/mailman/listinfo/opm _______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
