We had a big push on hottest100 last week, and it was good. A fairly
recent copy of the hottest100 results are below.
To summarize where we got to: most of the upstream branches are now
working; there are a few not correctly registered but that could
probably be fairly easily fixed. In package
On Wed, 3 Feb 2010 16:40:12 +, Martin Pool m...@canonical.com wrote:
* help james_w with some of the bugs opened against the package
importer (assuming he wants it)
I would love it.
Thanks,
James
--
ubuntu-distributed-devel mailing list
ubuntu-distributed-devel@lists.ubuntu.com
Modify
We're hacking a bit more on this script (in
http://code.launchpad.net/~canonical-bazaar/udd/hottest100) to make it
do things including
* check both the package and upstream branch for freshness and existence
* cross check the package branch against Madison
* understand some of the branches that
On January 26, 2010, Martin Pool wrote:
We're hacking a bit more on this script (in
http://code.launchpad.net/~canonical-bazaar/udd/hottest100) to make it
do things including
* check both the package and upstream branch for freshness and existence
* cross check the package branch against
On Tue, 2010-01-26 at 05:38 -0500, Francis J. Lacoste wrote:
On January 26, 2010, Martin Pool wrote:
and in passing we're fixing some misregistration. At the moment the
biggest problem we can't fix is that some Launchpad projects have
branches but no development focus (ie default branch)
2010/1/26 Jelmer Vernooij jel...@canonical.com:
I've fixed those I can up myself, since I'm already a member of the
Registry Administrators somehow.
There's quite a few that seem to be owned by community members or teams
but haven't actually been touched in a while. The following projects we
2010/1/26 Martin Pool m...@canonical.com:
lp:accerciser - lp:~vcs-imports/accerciser/main
lp:at-spi - lp:~vcs-imports/at-spi/git-trunk
lp:ekiga - lp:~vcs-imports/ekiga/git-trunk
lp:gconf - lp:~vcs-imports/gconf/trunk
lp:glib - lp:~jjardon/glib/trunk
all done
lp:gnome-common -
On Tue, 2010-01-26 at 11:46 +0100, Jelmer Vernooij wrote:
On Tue, 2010-01-26 at 05:38 -0500, Francis J. Lacoste wrote:
On January 26, 2010, Martin Pool wrote:
and in passing we're fixing some misregistration. At the moment the
biggest problem we can't fix is that some Launchpad projects
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Pool wrote:
2010/1/15 Andrew Bennetts andrew.benne...@canonical.com:
Martin Pool wrote:
[...]
The definition of 'working' here may be a bit loose; I'm working on a
script to scan them and report those which are stale. This will also
I
2010/1/16 Francis J. Lacoste francis.laco...@canonical.com:
On January 15, 2010, Martin Pool wrote:
In case people are wondering how far this has come.
When we started focussing on the hottest100 a month ago we had about
90 of the hottest100 packages linked to products, and about 52 of them
On Thu, 2010-01-14 at 18:07 +1100, Andrew Bennetts wrote:
Import exists but fails (even after retry):
---
gnome-control-center
This was a broken import - I've removed it and created it again to force
it to import from scratch.
gnome-power-manager
I
On Fri, 2010-01-15 at 09:49 +1100, Andrew Bennetts wrote:
Jelmer Vernooij wrote:
On Thu, 2010-01-14 at 18:07 +1100, Andrew Bennetts wrote:
Import exists but fails (even after retry):
---
gnome-control-center
This was a broken import - I've
In case people are wondering how far this has come.
When we started focussing on the hottest100 a month ago we had about
90 of the hottest100 packages linked to products, and about 52 of them
had working branches. Now we have 94 of them linked to products,
which must be just about all that
Martin Pool wrote:
[...]
The definition of 'working' here may be a bit loose; I'm working on a
script to scan them and report those which are stale. This will also
I suspect that most of the gnome ones are currently stale (hopefully my
mail from yesterday is a good step towards correcting
2010/1/15 Andrew Bennetts andrew.benne...@canonical.com:
Martin Pool wrote:
[...]
The definition of 'working' here may be a bit loose; I'm working on a
script to scan them and report those which are stale. This will also
I suspect that most of the gnome ones are currently stale (hopefully
Andrew SB wrote:
On Tue, Jan 5, 2010 at 2:33 AM, Martin Pool m...@canonical.com wrote:
To be useful, this query needs some measurement of whether the branch is
fresh.
This is especially true for GNOME products. A number of branches
currently marked as working are still pointed at old svn
Here are some specific things people can do to help with hottest100:
* work out how to make package-product links (explain that here :-)
and create them when they're missing
* update the branches pointing to obsolete imports (gnome etc)
* write a script that checks the date of the last
2010/1/8 James Westby jw+deb...@jameswestby.net:
On Fri, 8 Jan 2010 10:58:04 +1100, Martin Pool m...@canonical.com wrote:
Here are some specific things people can do to help with hottest100:
* work out how to make package-product links (explain that here :-)
and create them when they're
On Wed, 06 Jan 2010 17:39:02 Jonathan Lange wrote:
On Wed, Jan 6, 2010 at 12:46 PM, Tim Penhey tim.pen...@canonical.com
wrote:
On Wed, 06 Jan 2010 13:38:53 Jonathan Lange wrote:
So the associating development focus does not seem to have been done.
Again, I don't think I have access to
On Tue, 5 Jan 2010 18:33:29 +1100, Martin Pool m...@canonical.com wrote:
I put jml's query output into a Google spreadsheet, so that we can
annotate lines with the relevant bug etc.
http://spreadsheets.google.com/ccc?key=0Ag3S65cphSMHdG1VckNSRXI4OHBmVmxGaklGVW4tcWchl=en_GB.
I'll put another
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Westby wrote:
On Tue, 5 Jan 2010 18:33:29 +1100, Martin Pool m...@canonical.com wrote:
I put jml's query output into a Google spreadsheet, so that we can
annotate lines with the relevant bug etc.
On Tue, 05 Jan 2010 10:32:08 -0600, John Arbash Meinel j...@arbash-meinel.com
wrote:
So... how do we do that? Who gets assigned that task? I certainly don't
feel like I have any ability to make that change.
I think it's normally the job of the LP CHR. I was hoping one of the LP
people on the
On Tue, Jan 5, 2010 at 2:33 AM, Martin Pool m...@canonical.com wrote:
To be useful, this query needs some measurement of whether the branch is
fresh.
This is especially true for GNOME products. A number of branches
currently marked as working are still pointed at old svn repos while
the
I put jml's query output into a Google spreadsheet, so that we can
annotate lines with the relevant bug etc.
http://spreadsheets.google.com/ccc?key=0Ag3S65cphSMHdG1VckNSRXI4OHBmVmxGaklGVW4tcWchl=en_GB.
Some observations:
Some aren't linked to products; that's probably easily fixed.
In some
24 matches
Mail list logo