Things to graph for package-of-the-day work
Curtis Hovey
curtis.hovey at canonical.com
Tue Nov 17 23:03:22 GMT 2009
On Wed, 2009-11-18 at 09:20 +1100, Robert Collins wrote:
> On Tue, 2009-11-17 at 10:49 -0500, Curtis Hovey wrote:
>
>
> > I have not found any documentation. I have been reading the code, the
> > bug reports, and trying the UI to understand what it does. I have fixed
> > many bugs that make the action easier to perform and prevents insane
> > data.
> >
> > I have been asking the similar questions as you. Package links do not
> > create notifications when upstream creates a release. The imported
> > releases may fix bugs that Ubuntu cares about, but there is no automatic
> > way to state that 10 fixed bug upstream are some other 10 bugs in
> > launchpad.
> >
> > I think packaging links (as they are implemented) are documentation
> > about the past. They are not a tool that helps contributors to know when
> > to create a package and where to get the code.
>
> The intent was to like 'upstream product release finder' through the
> packaging links to packages, to show a link / notification on the
> package side when upstreams make a release. The recently added downloads
> facilities can naturally do the same. In the fullness of time the
> further planned step was to allow merging via bzr.
>
> Its definitely vestigial at the moment.
Thanks. This coincides with my recent thought to add events to the core
registry objects so that I can hook notifications and karma to things
like the creation of a series or a release tarball.
--
__Curtis C. Hovey_________
http://launchpad.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-distributed-devel/attachments/20091117/8bd57421/attachment-0001.pgp
More information about the ubuntu-distributed-devel
mailing list