Re: How many Ubuntu branches share history with upstream?
On Wed, 2010-02-10 at 13:58 +, Jonathan Lange wrote: In a previous discussion about Ubuntu distributed development, someone suggested that we graph the number of Ubuntu branches that share history with upstream. I think that's a very interesting thing to graph, but I have absolutely no idea on how to get that information -- even with access to Launchpad. How could we do it? The simplest thing to check would just be to see if the first revision of the upstream branch is part of the ancestry of the packaging branches' tip. Are you going to use the database for this or are you fine with calling out to Bazaar and using the branches on disk / remote servers? Cheers, Jelmer signature.asc Description: This is a digitally signed message part -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: How many Ubuntu branches share history with upstream?
On Wed, Feb 10, 2010 at 2:08 PM, Jelmer Vernooij jel...@canonical.com wrote: On Wed, 2010-02-10 at 13:58 +, Jonathan Lange wrote: In a previous discussion about Ubuntu distributed development, someone suggested that we graph the number of Ubuntu branches that share history with upstream. I think that's a very interesting thing to graph, but I have absolutely no idea on how to get that information -- even with access to Launchpad. How could we do it? The simplest thing to check would just be to see if the first revision of the upstream branch is part of the ancestry of the packaging branches' tip. Are you going to use the database for this or are you fine with calling out to Bazaar and using the branches on disk / remote servers? I'd like to use the database, since I think the other option would be grindingly slow. jml -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: How many Ubuntu branches share history with upstream?
On Wed, 2010-02-10 at 14:10 +, Jonathan Lange wrote: On Wed, Feb 10, 2010 at 2:08 PM, Jelmer Vernooij jel...@canonical.com wrote: On Wed, 2010-02-10 at 13:58 +, Jonathan Lange wrote: In a previous discussion about Ubuntu distributed development, someone suggested that we graph the number of Ubuntu branches that share history with upstream. I think that's a very interesting thing to graph, but I have absolutely no idea on how to get that information -- even with access to Launchpad. How could we do it? The simplest thing to check would just be to see if the first revision of the upstream branch is part of the ancestry of the packaging branches' tip. Are you going to use the database for this or are you fine with calling out to Bazaar and using the branches on disk / remote servers? I'd like to use the database, since I think the other option would be grindingly slow. So checking whether a revision is part of another branches' ancestry is not really possible then, if I understand the current database scheme correctly. You should be able to detect the common ancestry in most of the cases by just checking that the first revision of the upstream branch and first revision of the packaging branch have the same revid. This won't allow you to detect the situation where the packaging branch was created first and the upstream merged into it later, but as far as I can tell that's quite rare. Something related to this that has an open bug in lp-code - it is impossible to have common ancestry between upstream and debian packaging branches at the moment because it is impossible to register mirrors / imports for packaging branches. Cheers, Jelmer signature.asc Description: This is a digitally signed message part -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: How many Ubuntu branches share history with upstream?
On Wed, 10 Feb 2010 15:16:18 +0100, Jelmer Vernooij jel...@canonical.com wrote: So checking whether a revision is part of another branches' ancestry is not really possible then, if I understand the current database scheme correctly. You should be able to detect the common ancestry in most of the cases by just checking that the first revision of the upstream branch and first revision of the packaging branch have the same revid. This won't allow you to detect the situation where the packaging branch was created first and the upstream merged into it later, but as far as I can tell that's quite rare. Quite rare due to file id differences. I'd like to start encouraging developers to merge upstream in as a second root, but I don't want to do that until we can handle the file-id differences smoothly. So yes, I'd agree that would be a reasonable approximation currently, but it's not sure to hold over time. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: How many Ubuntu branches share history with upstream?
On Wed, 10 Feb 2010 08:46:37 -0600, John Arbash Meinel j...@arbash-meinel.com wrote: Where is this script going to be running? I wrote a trivial command that lets you run: bzr in-ancestry branch1 branch2 And reports back if the ancestry of branch1 is in branch2. lp:~jameinel/+junk/bzr-in-ancestry Running locally on bzr.dev trees, it takes less than 3 seconds to return true/false. Note also that the answer isn't symmetric. We've merged plugins into bzr.dev, but those plugins have not merged bzr.dev into them. Similarly for packaging branches. I would imagine that the packaging branch might merge upstream, but not the other way around. Comparing a mysql branch with a bzr.dev one seems to take 4s, which still isn't particularly long. I don't know what time scale you were hoping for Certainly less than a day to run. 3s * 10,000 ~= 8 hours. It wouldn't be near that to start with as we don't have anywhere near that number of packaging links, but it's always useful to look at what would happen if you scale. (but my experience with launchpad apis doesn't make it particularly faster than this ...) True, but graphs can be done against the DB directly, which would be much quicker as you don't have the https round trip overhead and it gives you scope for writing queries that act on all projects at once. Thanks, James -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
