<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>:) 3x times a year, correct! <br><br>-------- Ursprüngliche Nachricht --------<br>Von: tsdgeos@yahoo.es <br>Datum: 18.06.2016 20:43 (GMT+01:00) <br>An: Harald Albrecht <harald.albrecht@gmx.net>, kdenlive@kde.org <br>Betreff: Re: [kdenlive] Kdenlive release cycles <br><br>Next will be 16.08 not 16.10, we're not Ubuntu. <br><br>Cheers, <br> Albert<br><br>Enviat des del meu telèfon intel·ligent BlackBerry 10.<br> Missatge original <br>De: Harald Albrecht<br>Enviat: dissabte 18 de juny de 2016 20.18<br>Per a: kdenlive@kde.org<br>Tema: Re: [kdenlive] Kdenlive release cycles<br><br>€.02:<br><br>1. git Applications/xx.yy is the recent stable version including bug <br>fixes. This branch follows the KDE Project's versioning scheme. <br>Currently, we see git Kdenlive Applications/16.04, with tags for 16.04, <br>16.04.1, 16.04.2. Next stable branch will be Applications 16.10. Normal <br>users please stay on these branches. These branches receive backported <br>fixes as we also find them in the main development branch. Jean-Baptiste <br>does an incredible good job on this!<br><br>2. git master is unstable. git master is unstable. git master is <br>unstable. git master is ... unstable!<br><br>It is currently in a mixed state, stability depends on what you intend <br>to do. Use at your own risk or to report bugs. Some bugs I've noticed <br>are duplicates of transitions that basically trash your project when <br>moving a clip group containing transitions. Another one is that sometime <br>keyframes cannot be set on effects, as the keyframe table view seems to <br>get completely out of sync with the MLT keyframes and messes up offsets.<br><br>Best regards,<br>Harald<br><br><br>Am 18.06.2016 um 19:17 schrieb Narcis Garcia:<br>> I think the releases strategy should change, to allow professional users<br>> to report bug reports in a "stable" production environment:<br>><br>> Mark at least one "supported" version as other projects do (LTS~ESR) and<br>> backport released bugfixes that concerns to that version.<br>> I know this implies to maintain a "testing" (git) + a "stable" version<br>> (LTS), but:<br>> 1. Some GNU/Linux distributions could package Kdenlive "stable" and<br>> maintain packaging of bugfixes updates.<br>> 2. Professional users could trust a concrete Kdenlive version for<br>> critical projects, without thinking in "other software issues".<br>> 3. Kdenlive "stable" version could help project to be known (even more)<br>> as reliable software for any time.<br>> 4. Bugfixes made for "LTS" version could improve the base for developing<br>> features in the "latest" version, because those features are written<br>> over a more solid and consistent source code.<br>> 5. Another consequence is to balance developer efforts between<br>> wide-known bugfixing and new features.<br>><br>><br>><br>> El 18/06/16 a les 18:50, Evert Vorster ha escrit:<br>>> Hi there, Narcis.<br>>><br>>> There really is just one main developer in Kdenlive, and it's not his<br>>> full time job, it's a hobby.<br>>> So, unless there is something seriously wrong with the latest released<br>>> version of kdenlive, all the development effort goes into the next release.<br>>><br>>> The latest release will be whatever your package manager installs.<br>>><br>>> If you want to build from git, you get the absolute latest version, but<br>>> also the potential to run into some serious bugs. This does give you the<br>>> opportunity to do some bug reports, though. If you are running Arch,<br>>> installing from git is easy, I would not know about the other<br>>> distributions.<br>>><br>>> :)<br>>><br>>> On 18 June 2016 at 17:23, Narcis Garcia <informatica@actiu.net<br>>> <mailto:informatica@actiu.net>> wrote:<br>>><br>>> Do you mean that, once a version is released, no bugfixing updates are<br>>> published for that version, and the focus is for next one?<br>>><br>>> If not, what are the currently maintained versions of Kdenlive?<br>>><br>>><br>>> El 18/06/16 a les 18:03, Evert Vorster ha escrit:<br>>> > Hi there, Narcis.<br>>> ><br>>> > There is only one branch of Kdenlive, and releases are synchronized with<br>>> > KDE. After a release, new features are added, and then before a release<br>>> > some time is spent sorting out bugs.<br>>> ><br>>> > Kind regards,<br>>> > Evert<br>>> ><br>>> > On 18 June 2016 at 17:00, Narcis Garcia <informatica@actiu.net <mailto:informatica@actiu.net><br>>> > <mailto:informatica@actiu.net <mailto:informatica@actiu.net>>> wrote:<br>>> ><br>>> > How does work Kdenlive's versioning and stabilization?<br>>> ><br>>> > Are there some kind of "major", "LTS" or "stable" versions that are<br>>> > feature-frozen and focused about updates for bug fixing?<br>>> ><br>>> > Thanks.<br>>> > _______________________________________________<br>>> > kdenlive mailing list<br>>> > kdenlive@kde.org <mailto:kdenlive@kde.org><br>>> <mailto:kdenlive@kde.org <mailto:kdenlive@kde.org>><br>>> > https://mail.kde.org/mailman/listinfo/kdenlive<br>>> ><br>>> ><br>>> ><br>>> ><br>>> > --<br>>> > Evert Vorster<br>>> > Isometrix Acquistion Superchief<br>>> > (Streamer Handling)<br>>> _______________________________________________<br>>> kdenlive mailing list<br>>> kdenlive@kde.org <mailto:kdenlive@kde.org><br>>> https://mail.kde.org/mailman/listinfo/kdenlive<br>>><br>>><br>>><br>>><br>>> -- <br>>> Evert Vorster<br>>> Isometrix Acquistion Superchief<br>>> (Streamer Handling)<br>> _______________________________________________<br>> kdenlive mailing list<br>> kdenlive@kde.org<br>> https://mail.kde.org/mailman/listinfo/kdenlive<br><br>_______________________________________________<br>kdenlive mailing list<br>kdenlive@kde.org<br>https://mail.kde.org/mailman/listinfo/kdenlive<br></body></html>