Reorganisation of the desktop wiki pages

[Cesare Tirabassi]

On Monday 22 September 2008 13:04:39 Baptiste Mille-Mathias wrote:
> One problem I see is that the page suggest future unstable version as
> upstream - for instance metacity maintainers have already release a
> version 2.25.x for next cycle (2.26) and I'm not sure we want to stick
> with that version for intrepid :). Perhaps this is a corner -case that
> should be ironed-out; but this is not a showstopper.

OK, I modified the script so that it accepts as an optional argument a Gnome 
release number. For the generated web page I use now 2.23 which is the Gnome 
release to which we sync for Intrepid.

On Monday 22 September 2008 16:40:49 Didier Roche wrote:
> The missing thing for me is to link to a bug that wait for sponsor

Seems a good idea.

> - Maybe making a "bugs linkage" or "updater" editable field?

Hmmm, that would require some modifications to the html page to allow inputs 
via javascript. This will be anyhow pointless as the page is regenerated 
daily so that information will be overwritten unless we could somehow save 
it. I think this will be too cumbersome to implement.

> - or using the LP API to grep for bug title for this ubuntu package
> containg the sponsor + correct numbering version to automate this?

The problem is how do we decide if a given bug waiting for sponsorship is an 
update?
For instance:

https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/250290

This is an update, but there is no keywords that would lead this to be picked 
up.

So, for the time being I added a link to all bugs in the sponsoring queues 
about a given source package. Those bugs should then be manually checked to 
see if they contain an update or not.

Cesare