[kdenlive] Kdenlive compilation

[Vincent PINON]

Hello,

As I understood KDE policy, master should always remain in "releasable
state",
without developments that breaks things for day-to-day use (like our
current refactoring).
==> we should keep master as it is, receiving bug fixes and trivial new
features.

Ttguy's test is showing that "frameworks" is beeing automatically built
for KF5 distro,
and I think our refactoring in this branch is not appropriate to be
exposed to users yet (right?)
==> I would continue refactoring in "next", that in common habits is the
unstable dev trunk.

old branches I would keep :
"v0.9.x" for KDE4 version bugfix
"refactoring" as reference for new design, as it contains Till's work,
"movit" until we get it to work again with refactored monitor.

Once agreed on this, I can submit sysadmin ticket to remove unneeded
branches,
and we should write this on wiki...

Vincent.

Le 03/03/2015 23:15, jb a écrit :
> If you get the warning about experimental version on open/save project in 
> Kdenlive, that means you are using the "frameworks" branch, which contains the 
> Qt5/KF5 code with refactoring code. 
>
> The branch that will be released as part of KDE Applications 15.04 is now:
> * Applications/15.04
>
> All fixes / patches should go there (but no string change and no new 
> features).
>
> We need to make some cleanup with the other branches, here is a brief 
> explanation of them:
>
> * master
> Currently contains the same code as Applications/15.04 but we should merge all 
> changes from the "frameworks" branch so that master will be the branch 
> containing the refactoring stuff where new features should be added
>
> * frameworks
> Should be merged in "master" then removed
>
> * 15.04
> That is an obsolete branch, should be removed
>
> * stabilize, movit, next, jogshuttle, movit contain some stuff that might be 
> at some point merged into master.
>
> Hope it helps,
>
> regards
> jb