Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Alessandra Forti said:
> it seems that the problem is also that the updates are becoming 'fat'
> i.e. they contain too many different things.
What actually happens is that changes are in units of "patches":
https://savannah.cern.ch/patch/?group=jra1mdw
Those normally are pretty self-contained, although there is some
tendancy for developers to put more than one change in a patch as it
tends to make the process go faster. However, certainly things like
lcg-voms (patch #1156) and DPM (#1121) are kept separate. The patches
all progress through certification/PPS/PS independently, and what gets
seen as an "update" in the PS is just whatever bundle of patches happens
to make it out of the PPS stage that week. However, the patch structure
seems to vanish in that final step, presumably in the cause of
simplicity, but even looking at the detailed docs for the updates the
patch information seems not to be there. Perhaps we need to request that
patch-level information is preserved so that sites can choose to install
individual patches if they want (in general it would not make sense to
install part of a patch).
One other procedural point is that if you look at the patches you can
see that they get closed once they go to production - the assumption is
that they must be working to have got that far! I think we probably need
some extra piece of the release process which allows for the possibility
that patches may need to be pushed back even after they get to
production.
Stephen
|