[RFC] use cases for 'projects'...

Robert Collins robertc at robertcollins.net
Mon Nov 5 13:46:16 GMT 2007


Jelmer writes in his blog:

      * Tags should ideally be shared amongst a set of related branches.
        This has come up often during discussions about where tags
        belong.
      * Management of sets of bzr branches is hard
              * It seems to make sense for the configuration of several
                plugins to be project-specific:
                      * bzr-pqm-submit's pqm address
                      * bzr-email target address
                      * bzr-cia's project setting
                      * ...
              * may be useful to override whoami
              * having a way to group branches allows mass-pushes/pulls
      * I often find that the public_location I set is almost the same
        for related branches, with only the last part of the url
        differing and containing the branch nick
      * It would be nice if "bzr register-branch" could automatically
        determine what product to register as

I don't think a 'project' concept addresses this because at least for
me, groups of branches to push/pull are more often coupled by what I'm
working on not by what project that comes from - e.g. it might be a
couple of bzr branches and two or three plugin branches.

However, perhaps thats too specialised.

Here are some use cases that I run into:

      * bzr commit-notify would be nicer if it could filter on project.
        e.g. 'I am interested in only bzr commits'.
      * the hypothetical bzr irc-notify would be nice, one reason I
        haven't written it yet is filtering and performance - it would
        be nice to be config-free - that is to connect to one known irc
        channel, to send enough data to that channel on each commit that
        not every bzr client in the world suddenly DOS's the target url;
        rather interested clients should be able to determine *some*
        degree of interest without connecting to the server; or only
        downloading a couple of tiny files.

Some discussion - we can filter already on e.g. URL's - but this works
only so-so when one is doing local-area notifications as the url is
often just bzr://hostname/basename.

I don't think working with groups of branches is really a 'project'
object - but working with groups of branches today should be
straightforward if someone extends our url lookup logic to understand
something like URL;tag=foo or URL#tag=foo.

-Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20071106/f1c98656/attachment.pgp 


More information about the bazaar mailing list