Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Decide versioning for libmypaint: separate from MyPaint, or not? #29
I guess it all depends if one project becomes much faster than the other. In particular if libmypaint becomes so used in third-party projects that it gets bug fixes faster than MyPaint itself is released, it may then be wised to release a version of libmypaint separately.
This said, libmypaint can start as following MyPaint's version and if the need arises some day, then you can always split later. Or you can split already now and make the separation as clean as possible.
I know: my answer is not helpful. :-P
I would vote starting off with same version as MyPaint currently is and
On Wed, Dec 23, 2015, 3:10 PM Sebastian Pipping firstname.lastname@example.org
-- Albert Westra
@hartwork Existing/deployed .pc files matter, so we won't go before those. Currently you'll get 1.1 in those.
Noting that even huge projects like GNOME basically even peg app versions to the main version number. It can be done. Let's do as @odysseywestra suggests initially, and bump libmypaint's .pc version forward to 1.2.0 at the upcoming MyPaint release so that GIMP can be sure it's getting the latest translations at least. When libmypaint goes independent (probably at 1.2.1), we'll start bumping both together and see what happens.
Oh, drat. I didn't bump brushlib_version for the MyPaint release as I said I would. That will have to change for the first release, in that case. Anyway, time to review milestones and suchlike.
libmypaint is now sharedlib-by-default, so we could call what we have v1.2.0 since it's basically what MyPaint v1.2.0 is using. Let's create a formal v1.2.0 release tag soon.
I would like to use Semantic Versioning for libmypaint: http://semver.org/, similar to MyPaint. I am happy for the versions to start drifting right away.
"Soon"... ahem, whoops. I got sidetracked by the MyPaint release and real life. Need to re-focus on this and make a decision.
I think MyPaint 1.3.0 will be the first to use the independent libmypaint, so maybe our initial independent release of libmypaint should match that version. Thinking about it again, it would be nice for us to avoid confusion while were doing the split. We can decide whether to let versions drift or keep them in step afterwards.
MyPaint has a