Re: Unable to run test patchy - URI changed for tracker?

[Phil Holmes]

----- Original Message ----- 
From: "David Kastrup" <address@hidden>
To: <address@hidden>
Sent: Wednesday, July 17, 2013 10:22 AM
Subject: Re: Unable to run test patchy - URI changed for tracker?


> David Kastrup <address@hidden> writes:
>
> > I downloaded the current version of gdata from Google and dropped its
> > src/gdata directory into our gdata directory, completely replacing its
> > previous contents.  Doesn't help.
> >
> > Maybe just wait and see whether it will come live on its own again...
>
> Uh oh.
>
> <URL:http://googleblog.blogspot.de/2012/12/winter-cleaning.html>
>
>    Last January, we renewed our resolution to focus on creating
>    beautiful, useful products that improve millions of people’s lives
>    every day. To make the most impact, we need to make some difficult
>    decisions. So as 2012 comes to an end, here are some additional
>    products, features and services we’re closing:
>
> [...]
>
>  * The Issue Tracker Data API allows client applications to view and
>    update issues on Project Hosting on Google Code in the form of
>    Google Data API feeds. We’ll shut down the Issue Tracker API on
>    June 14, 2013.
>
> <URL:http://code.google.com/p/support/wiki/IssueTrackerAPI#Deprecated>
>
> Well, this was nice while it lasted.  What now?


Three options I can think of.  1) use something other than Google.  2) go 
manual for bug updating.  3) "Screen scrape".  For example, the following 
URL should provide a CSV listing of current patch-new bugs, which could be 
parsed:

http://code.google.com/p/lilypond/issues/csv?can=2&q=Patch%3Dnew%20&colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary

I think this will also affect our git-cl.  With both that and the updating 
of issues with patchy, we need to work out how to authenticate without the 
API.

--
Phil Holmes