We have collected here some recurrent questions about the KDE release process.
No, that is a new dependency anyway.
Application version numbering is up to you as app maintainer.
Again, versioning is up to you but having a .80/.90 at the end is more in line with what we do with the rest of apps.
YY.(MM+4)-1.70 is the version in master, which will become YY.(MM+4).00 after YY.MM.00 release.
New release branches are created by the release team. Run a 'git pull --all' to update your local repository.
Because people depend on unreleased versions of libraries and stuff and the release manager have to make sure distros can actually build things from tarballs. One week is the bare minimum it takes the release manager to try to build everything and eventually have luck chasing people to make sure their dependncies are released.
Because if beta and RC have important bugs, noone really cares, we can just fix them in final release. Having a week for people to actually find important bugs in final release and retagging the packages is much more important.