I propose we make a bugfix release in v2.7 branch in about 3 months after initial release. We've got several fixes in master, I backported most of them to the branch and will backport the remaining later. Let's do a feature freeze on 2018-07-22. Since it's a bugfix release, it should be trivial, I just mean we won't add bugfixes that modify any behavior (even shortcuts) after this point.
Do you have any bugs you want to fix before the release?
Do we have any reported regressions for v2.6.0 to v2.7.0 upgrade?
I can't recall any.
Do you have any unpublished work?
For the active code reviews:
> I propose we make a bugfix release in v2.7 branch in about 3 months
> after initial release. We've got several fixes in master [...]
I agree that a bugfix release after three months is a good idea. Also, as the last release was not too long ago, the knowledge about releasing still remains :-) and it's also a good chance to test and improve Krusader's [Release Howto](https://phabricator.kde.org/w/krusader/release-howto/) :-)
I just thought it would be easier to wire against a fixed branch with a general name. I pushed 'stable' branch which we can set to the current stable sources. Currently it's the same head as 2.7. Please ask to add this branch as stable branch of translation.