Feature changed by: Adrian Schröter (adrianSuSE) Feature #311765, revision 3 Title: Freeze option for projects (and packages?) - Buildservice: New + Buildservice: Done Milestone: 2.3 Priority Requester: Mandatory + Projectmanager: Mandatory Requested by: Dirk Mueller (dirkmueller) Requested by: Ruediger Oertel (oertel) Project Manager: (Novell) Engineering Manager: (Novell) Technical Contact: (Novell) Partner organization: openSUSE.org Description: We got requests from various sides (maintenance, autobuild team and from Intel) to have a way to freeze entire projects. This means no builds, no source and meta changes are possible anymore. The first idea was to introduce a "freeze" flag. Similar to the "sourceaccess" flag. With freeze enable, the only action which is allowed to remove the freeze flag again. That means, all maintainers can remove the freeze flag again and change something afterwards. But they are blocked on doing anything else first. An open questions is what should happen when do a submit request from these projects (or single packages). Usually this requires also to update also the source when submitting to the branch target. In the maintenance case, we should find a way to freeze the source revision (eg. via using xsrcmd5) before creating the release request. So this would not affect us here. Discussion: #1: Adrian Schröter (adriansuse) (2011-03-16 10:55:37) We could bind the "freeze" flag handling permission to a special role. In that way we could define release managers beside the maintainers. + #2: Adrian Schröter (adriansuse) (2011-03-22 08:44:47) + To avoid name clashes, this option got implemented as "readonly" flag + for projects. Not yet for packages until we really need it and can + describe the use case. -- openSUSE Feature: https://features.opensuse.org/311765