|This page needs a review and probably holds information that needs to be fixed.
Parts to be reviewed:Check for outdated infformation.
We have collected here some recurrent questions about the KDE release process.
No. A run-time dependency is a new dependency.
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 in 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
git pull --all to update your local repository.
Because people depend on unreleased versions of libraries and stuff and the release manager has to make sure distributions can actually build from tarballs. One week is the bare minimum it takes the release manager to try to build everything and eventually contact people to make sure their dependencies are released.
Because if beta and RC have important bugs, often not enough bug reports come in, because 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.