Merge lp://qastaging/~mabac/launchpad-work-items-tracker/linaro-config-1112 into lp://qastaging/~linaro-automation/launchpad-work-items-tracker/linaro-config

Proposed by Mattias Backman
Status: Merged
Approved by: Fathi Boudra
Approved revision: 24
Merge reported by: Fathi Boudra
Merged at revision: not available
Proposed branch: lp://qastaging/~mabac/launchpad-work-items-tracker/linaro-config-1112
Merge into: lp://qastaging/~linaro-automation/launchpad-work-items-tracker/linaro-config
Diff against target: 133 lines (+129/-0)
1 file modified
11.12.cfg (+129/-0)
To merge this branch: bzr merge lp://qastaging/~mabac/launchpad-work-items-tracker/linaro-config-1112
Reviewer Review Type Date Requested Status
Fathi Boudra Approve
David Zinman Pending
Linaro Infrastructure Pending
Review via email: mp+83286@code.qastaging.launchpad.net

Description of the change

Hi,

This branch adds a status.linaro.org config for 11.12 which we probably need. Should we look at trunk for all projects now or has that change not happened yet?

Thanks,

Mattias

To post a comment you must log in.
Revision history for this message
Fathi Boudra (fboudra) wrote :

Most of the projects switched to trunk serie. We have some exceptions like CI, using engineering.
Does it means, we need to create a new config for each monthly cycle?

note: my understanding is that status.linaro.org will redirect to the current monthly cycle
e.g http://status.linaro.org/11.12/, http://status.linaro.org/12.01/, http://status.linaro.org/12.02/, etc...

it needs fixing anyway. The current mapping doesn't reflect next series.

review: Needs Fixing
Revision history for this message
Mattias Backman (mabac) wrote :

> Most of the projects switched to trunk serie. We have some exceptions like CI,
> using engineering.
> Does it means, we need to create a new config for each monthly cycle?

Yes, as the work-items-tracker is built. It will harvest data and generate reports for each of the config files. Which means that there has to be a config per cycle. It also means that we can shorten the time for updates by removing old ones (11.05 looks like a good candidate to kill).

>
> note: my understanding is that status.linaro.org will redirect to the current
> monthly cycle
> e.g http://status.linaro.org/11.12/, http://status.linaro.org/12.01/,
> http://status.linaro.org/12.02/, etc...

There is a redirect to 11.11 atm, but I haven't found out where that is configured yet. It should be moved to 11.12 but that content is not generated yet since there is no config for it.

>
> it needs fixing anyway. The current mapping doesn't reflect next series.

We'd need everyone involved to handle the updates to this file then.

Revision history for this message
Mattias Backman (mabac) wrote :

> > note: my understanding is that status.linaro.org will redirect to the
> current
> > monthly cycle
> > e.g http://status.linaro.org/11.12/, http://status.linaro.org/12.01/,
> > http://status.linaro.org/12.02/, etc...
>
> There is a redirect to 11.11 atm, but I haven't found out where that is
> configured yet. It should be moved to 11.12 but that content is not generated
> yet since there is no config for it.

Aha, it's in /etc/apache2/sites-available/status.linaro.org:
    RedirectMatch ^/$ http://status.linaro.org/11.11/

This needs to be changed every cycle as well.

Revision history for this message
Fathi Boudra (fboudra) :
review: Approve
Revision history for this message
Fathi Boudra (fboudra) wrote :

let's land as is and update the config file today.

review: Approve
Revision history for this message
warmcat (andy-warmcat) wrote :

Guys while wishing you the best of luck I have a wild intuition that everyone in 'linaro' group is not the ideal audience for these considerations and deliberations.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches

to all changes: