Adding support for the new Sourceforge trackers (Allura)

[Olivier Berger]

Hi.

I think I've now some much better solution, which includes the new
AlluraTracker remote, for forwarded URL directly of the form
http://sourceforge.net/p/PROJECT/bugs/ID/, and the handling of redirects
between sourceforge2 urls and allura.

I've pushed to the allura branch.

I guess there are probably bugs or unnecessary bits, but I won't work on
it until tomorow (sleep, now if the babies permit ;)

In the meantime, if you have some comments...

Best regards,

Olivier Berger <olivier.berger at telecom-sudparis.eu> writes:

> Hi.
>
> Some time ago, SourceForge migrated some (or all of its ?) projects to
> Allura, whose trackers have changed.
>
> I wonder whether anyone has noticed and/or is working on that...
>
> In any case, I've started some code to try and support it (hopefully not
> reinventing another wheel).
>
> You'll find my intial code in the 'allura' branch.
>
> FYI, the trackers have a nice API, easily parseable with json.
>
> However, I'm wondering how to better integrate this in the bts-link
> architecture.
>
> The SF Allura trackers are backward compatible : the old URL redirect to
> the new ones.
>
> For instance, the URL of
> https://sourceforge.net/tracker/?func=detail&aid=3614186&group_id=21935&atid=373747
> (a forwarded bug of #710513) is redirected to
> http://sourceforge.net/p/docbook/bugs/1300/ (whose JSON variant is at
> http://sourceforge.net/rest/p/docbook/bugs/1300/
>

-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)