naming the next major release

[Sebastian Kügler]

On Tuesday, August 20, 2013 10:56:41 Marco Martin wrote:
> On Tuesday 20 August 2013, Aaron J. Seigo wrote:
> >
> > That’s also what I see in the openSuse packages.
> >
> > So, yes, I got the # wrong .. it’s 3, not 5 currently .. so we’d end up
> > with 4 unless we skip it go to 5. Still, the “number used in the name
> > doesn’t match the version number of <insert component here>” comment
> > remains
> 
> uuh, right, build from master does a so.3..
> hmm, wonder where the 4 is gone, if was ever "decided" or just done by 
> mistake...
> so do we go for .4 (until we have time?)

Uhm, no, as ervin suggested, the so version should be 5, in line with other 
frameworks.

> > Basically, I’m suggesting that naming the product after the version of the
> > software isn’t a necessity and may not even be possible unless we elevate
> > one specific component to be the “defining” component, which I don’t think
> > we ought to do.
> 
> yes, more and more evident that things like library versions are to be seen
> as  a small implementation detail

and indeed not affect our communication. :)
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9