On Thu, Jan 07, 2010 at 02:36:38PM +, Daniel Pocock wrote:
then you are going to need either 2 public resources for all release
managers
to use consistently or a coordinate release process were the package is
generated and then independently binary packages are added to it before
I've just looked at r2133.
I notice that there is a call to load_metric_modules() within the first
conditional block (args_info.metrics_flag).
Therefore, to solve the problem addressed by r2133, I believe one of the
following alternatives is needed:
a) put a call to load_metric_modules()
I've just done some backports for 3.1.6 (see log below), there may be a
couple of others to come too
- are there any more backports that people would like?
- it's probably time for people to start testing the monitor-core-3.1
branch with the view that we will tag 3.1.6 in the next 1-2 weeks
