hottest100 (was Re: Bazaar focus for 2.1 and 2.2)

Martin Pool mbp at canonical.com
Thu Feb 4 10:42:35 GMT 2010


On 8 January 2010 01:12, James Westby <jw+debian at jameswestby.net> wrote:
> On Fri, 8 Jan 2010 10:58:04 +1100, Martin Pool <mbp at 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 missing
>
> Just a note that
>
>  https://edge.launchpad.net/ubuntu/+upstreamreport
>
> has live data to help with this.
>
> "Missing corresponding project" means that a package-product link needs
> to be created (and sometimes a product too). The lack of a Bazaar icon
> means there is no default branch.
>
> Note that I went over this list a few weeks back registered a bunch of
> imports, and created the LP question to have them set as the development
> focus. That's still not done, and that's why I keep bringing it up,
> because you will often be duplicating effort if you look in to them.

Kind of an old post, but our sprint efforts last week addressed some of these.

> This says nothing about how up-to-date all that information is though. A
> (preferably semi-automatic) check that everything is up-to-date would be
> good.

check-hottest now makes sure that the package branch is up to date
with the package publishing history, and that the upstream branch has
recent commits, unless it is specifically marked as being slow-moving.

>
> This does raise other questions in my mind. Are we excluding some
> packages before we really start? Is implementing bzr-monotone going to
> be something that falls under the hottest100 project? There are also a
> few cases where we have two packages for one upstream repo, and some
> where there isn't really an upstream (aside from things like
> update-manager, linux-restricted-modules for instance). What will be
> done about the KDE packages, their upstream is one mega-repo.

Now we have some data on this.  Some of them are marked as special
cases, like the ones you mentioned, and others are developed entirely
corporately and there is no public branch to pull from.  Monotone
imports (maybe via fastimport not bzr-mt) now have a bug, but they
block only one from the hottest100.  Jelmer has landed something to
support KDE.

Here's a visual breakdown of the same (slightly stale) output I posted
the other day.  To me it makes it fairly clear the best focus for now
is on package imports.

-- 
Martin <http://launchpad.net/~mbp/>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2010-01-29-hottest100-status.png
Type: image/png
Size: 91603 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/ubuntu-distributed-devel/attachments/20100204/fdb0a39e/attachment-0001.png 


More information about the ubuntu-distributed-devel mailing list