There already important changes. And fixes like for https://bugs.kde.org/show_bug.cgi?id=371765.
Feature freeze in (roughly) one week, final release in two weeks - if nobody disagrees.
Somebody has an idea for a release name?
Description
Description
Comment Actions
How about "Stiff Challenges"? It's more or less meaningless but matches with the previous release names;)
And I will better name it 2.6.0. There are obviously not that many changes as between 2.4 and 2.5 but it is also not a "bugfix-only" release.
Comment Actions
Tomorrow or Tuesday - hopefully.
@palant If you want to be included in the author list, add yourself to the main.cpp.
And FYI: https://phabricator.kde.org/w/krusader/#commit-patch-guidelines
Otherwise creating a changelog is really a pain.
Comment Actions
After considering "Developer," "Developer (retired)" and "Code contributor" I decided to wait until next release - if I manage to keep contributing :)
Great to see a new release being planned. Sorry about the changelog, I wasn't aware of the special commit message format for that.
Comment Actions
Done. Somebody has to add 2.6.0 to the release list on bugzilla. I still don't have permission.
Sorry about the changelog, I wasn't aware of the special commit message format for that.
Don't worry, nobody was. I forgot it myself a lot of times.