[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-scm-interest
Subject:    Re: [Kde-scm-interest] Proposal for branching policy towards KF5
From:       Aurélien_Gâteau <agateau () kde ! org>
Date:       2013-07-29 20:09:38
Message-ID: 9777746.Z0IsJD9azy () trinity
[Download RAW message or body]

Le mercredi 24 juillet 2013 23:05:55 Michael Pyne a =E9crit :
> On Fri, July 19, 2013 00:21:21 you wrote:
> > After more live discussion with Sebas and Marco plus Aaron over a video
> > chat, we came up with the following setup for the workspace repos (*) :
> > =

> > - the development branch for their next feature release (based on Qt5/K=
F5)
> > will be "master".
> > - *before* this happens, however, kdesrc-build / kde-build-metadata /
> > projects.kde.org will need to be improved so that tools (kdesrc-build a=
nd
> > possibly build.kde.org) can automatically select "the latest Qt4-based
> > branch" (i.e. master everywhere and 4.11 for the workspace repos), on
> > demand. This would also be the opportunity to implement "latest *stable*
> > branch" which is 4.11 for most modules right now, but could be at some
> > point 4.12 for most and 4.11 for workspace repos.
> > Adding a similar generic selection for qt5/kf5, we would end up giving 3
> > options to people who compile from sources: stable, latest-qt4, or
> > qt5/kf5-
> > based.
> =

> First note: There's a lot of different mailing lists with at least some
> interest in this discussion, so I've mailed them all for informational
> purposes... but let's keep the discussion limited to the kde-core-devel
> mailing list!
> =

> Back on topic, I have made an initial draft specification [1] for what th=
is
> logical module group layer would look like.
> =

> In addition, there is a sample JSON file in the kde-build-metadata git
> repository, called "logical-module-structure" that one can view to get a
> feel for the proposed syntax/semantics.
> =

> I didn't want to write another parser, but JSON has no native comment
> support, so the documentation [1] is on community.kde.org (though perhaps
> that's for the best).

Slightly off-topic: I probably arrive a bit late, but have you considered =

using YAML instead of JSON? YAML is as light to write (if not lighter) than =

JSON, widespread enough to have parsers in many languages and does support =

comments.

Aur=E9lien
_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
[prev in list] [next in list] [prev in thread] [next in thread]