linaro-release team mailing list archive

[Loïc Minier <loic.minier@xxxxxxxxxx>]

On Fri, Sep 09, 2011, Paul Larson wrote:
> No, but I don't think this is going to be sufficient.  Fathi wanted me to
> make ~linaro-release a member so that the release team could have full
> control over blueprints, bugs, etc.  I think the better solution in this
> case would be to make linaro-drivers the driver for all projects.  Would
> that still cause issues with bug spam though?

 Hmm isn't that exactly what I did for lp:linaro-validation?  I do think
 it avoids bug spam, but I didn't verify.  I fully agree that if this is
 needed for other projects, then we should also arrange for
 ~linaro-release to be ultimately a driver for that project, perhaps
 with a more specific drivers team (e.g. linaro-toolchain-drivers with
 linaro-release as a member).

> In the of the bug that was pointed out, it was not supposed to be marked
> private and that state has been fixed a while back.

 Yup; just seemed a good occasion to fix this until a really private
 bugs follows the same path  :-)

-- 
Loïc Minier