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
