A destination is a project/ref combination. This change adds a
mechanism for users to categorize (i.e. tag, label, name...)
destinations. Gerrit has hashtags to categorize changes, and groups to
categorize accounts. Named destinations categorize project/ref
combinations. They make it possible to assign a name to sets of
destinations. Naming sets of destinations makes it easier to reference
them since you can just use a single name instead of enumerating the
whole set. Easier referencing can eventually make it easier to define
policies on sets of destinations (and to ensure that different
tools/users are using the same sets). This feature can be used to
allows users to define personal sets of destinations that interest them,
perhaps destinations that they would like to watch, or review, and it
may eventually allow them to share those sets with other users (not with
this change, that is a follow on feature).
This change makes it possible to search for changes based on those named
destinations. Eventually it might make sense to be able to apply ACLs
on named destinations, but this change does not attempt to do that.
Named destinations are currently defined at the user level. This change
parses user destinations named after files in the "destinations"
directory in the user's ref in the All-Users project. The
"destinations" file format is a simple text file with two tab separated
columns: REF and PROJECT. The named destinations are accessible via the
new "destination" operator: 'destination:<name>'
Change-Id: I41e65b10c98d4761b83e14c5e5e9698b64a9eec9
563a3e6a8f