Re: [PATCH weston 1/2] releasing: how to handle libweston

2016-08-15 Thread Pekka Paalanen
On Mon, 15 Aug 2016 17:06:02 +0800 Jonas Ådahl wrote: > On Wed, Aug 10, 2016 at 03:01:12PM +0300, Pekka Paalanen wrote: > > From: Pekka Paalanen > > > > libweston has separate version numbering from weston because of > > development needs. > > > > During development, weston version is major.mi

Re: [PATCH weston 1/2] releasing: how to handle libweston

2016-08-15 Thread Jonas Ådahl
On Wed, Aug 10, 2016 at 03:01:12PM +0300, Pekka Paalanen wrote: > From: Pekka Paalanen > > libweston has separate version numbering from weston because of > development needs. > > During development, weston version is major.minor.90 which will never be > a release version number. While developin

Libweston release blockers (Re: [PATCH weston 1/2] releasing: how to handle libweston)

2016-08-10 Thread Pekka Paalanen
Hi all, please mind that this patch is a weston release blocker. We cannot make any release until we have agreed and documented how the weston vs. libweston versions work. I believe this is the last libweston release blocker. If you have any further concerns, now is the time. Thanks, pq On We

[PATCH weston 1/2] releasing: how to handle libweston

2016-08-10 Thread Pekka Paalanen
From: Pekka Paalanen libweston has separate version numbering from weston because of development needs. During development, weston version is major.minor.90 which will never be a release version number. While developing, we may break the libweston backward-compatibility, in which case libweston_