1. Bazaar for GNOME
This page is to track what needs to be done for GNOME to move to bzr.
1.1. TODO
Server side hooks.
- Must have ability to reject the commit / push
- Must have ability to explain rejection via custom message
- MAINTAINERS file check
- svn-commits-list
- CIA (via email, not xml-rpc)
- Able to determine affected branch(es) and send short email to library.gnome.org and l10n.gnome.org
- PO file sanity check
1.2. In Progress
Server side hook to check for known email address / $USERID@rcs.gnome.org
- Server side audit log hook
1.3. Done
- Imports of all GNOME modules to Bazaar
- User branch area
- User area available read-only for other users to branch from
- Branch viewer
Loggerhead (http://bzr-playground.gnome.org)
1.4. Later options
- PQM to allow robotic landing of branches
- GPG signing of revisions
1.5. Malicious or unintended corruption protection
Anyone that has write access to the offical branch area has the ability to remove files or break the code. However there are ways that Bazaar can enforce that the history is still there, and corrupt revisions can be removed.
Branches can be configured to be append only, so existing history cannot be removed (reference needed).
By limiting access to the trunk branches through the smart server (bzr protocol) Bazaar can provide even more protection. The smart server currently has VFS functions for parts that are not yet written as "smart verbs". To avoid corruption using VFS functions we are proposing to disable VFS writes (but leave VFS for reads) and implement the required smart functions for the write operations.