As part of the release of 7.0.14, I've closed the ticket [feature-requests:#248], and the 7.0 release branch is back to a clean state. However, you may want to continue work on the elimination of warnings. If so, feel free to reopen the ticket.
Note that the trunk is the primary place to do development work, and the release branches should only be updated in preparation for a new release. If you prefer to continue this work on version 7 of the code, we can set up a development branch (e.g. "branches/7-warning-elimination"), so that the release branch doesn't get stuck in prerelease state.
Dear @jogybl and @luigibianchi, good work on this!
As part of the release of 7.0.14, I've closed the ticket [feature-requests:#248], and the 7.0 release branch is back to a clean state. However, you may want to continue work on the elimination of warnings. If so, feel free to reopen the ticket.
Note that the trunk is the primary place to do development work, and the release branches should only be updated in preparation for a new release. If you prefer to continue this work on version 7 of the code, we can set up a development branch (e.g. "branches/7-warning-elimination"), so that the release branch doesn't get stuck in prerelease state.
Related
Feature Requests:
#248