Re: Proposal for branching policy towards KF5

[Aurélien Gâteau]

Le mercredi 24 juillet 2013 23:05:55 Michael Pyne a écrit :
 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/KF5)
  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 and
  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 this
 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élien

Re: Proposal for branching policy towards KF5

[Michael Pyne]

On Mon, July 29, 2013 22:09:38 Aurélien Gâteau wrote:
 Le mercredi 24 juillet 2013 23:05:55 Michael Pyne a écrit :
  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.

I won't claim to have seriously considered it, but it seems we're using JSON 
elsewhere already, and Python at least appears to support it by default on all 
of the hosts where JSON may be necessary (e.g. l10n servers, build.kde.org, 
etc.).

The logic of the existing scripts is not very tied to the data interchange 
format so it's not like migrating to YAML would be traumatic at this point, 
but I don't think comments alone would warrant switching either now that we 
have some small amount of code supporting it.

And also, who wants to have to worry about code execution when you're just 
trying to parse a data interchange format? ;)

Regards,
 - Michael Pyne

signature.asc
Description: This is a digitally signed message part.