Hi,

Disclaimer first: This is not about KDE or its code, but about how the project handles its Subversion repository.

I'm usually following KDE's release schedules, and I noted that KDE seems to always tag the release, fix a few additional bugs and then release. I'm wondering what happens to the tag in that process; do you update the tag after fixes for this release are comitted? What if something not intended for this release has been comitted in the mean time?

I'm wondering because I tried to do the same recently, and I wasn't able to find a way to do so in Subversion. I could delete the tag and tag again, but this is not really elegant. Furthermore, adding selected changes from the trunk to a tag seems to be possible only when checking all the respective changes out and then tagging the working copy. How does KDE handle that?

As far as I know we never move tags.
At some point before a release a branch is created in which all bugfixing happens during betas and RC stages.

Each beta and RC is just a tag.

But I guess the best way to be sure is to ask on the release team mailinglist:
https://mail.kde.org/mailman/listinfo/release-team

Cheers,
_

That's enough information, thank you. I thought KDE was moving tags and I was interested in how that'd be possible in Subversion

Not related to KDE SVN

If you want to make a tag point to another revision, the easiest way is to delete the tag and create a new one with the same name.