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