Open Stack

Okay, thanks Jeremy.

I'm also wondering if my definition of partial-fix within docs would match
what the rest of the OpenStack world does. In doc-land, I do what I can to
fix, within my reach, but probably can't close it out without more patches.
That seems to match. But then the disconnect might be that often I can't
fix it the rest of the way, that I'd want someone else to pick it up. Is
that logical to other teams in your view?

Anne


On Mon, Jan 6, 2014 at 11:55 AM, Jeremy Stanley <fungi at yuggoth.org> wrote:

> On 2014-01-06 08:54:06 -0600 (-0600), Anne Gentle wrote:
> [...]
> > I think the Bug nnnnnn should become unassigned at the point when
> > the patch gets merged. Does that sound correct? How can I fix?
>
> The desired behavior would need to be added to
> <URL:
> http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/update_bug.py>
> but I'm still not convinced on what the assignment behavior for
> Partial-Bug should be.
>
> While the meaning of that header is not clearly defined, most
> interpretations are that there are multiple changes needed to fix
> the bug and they might not all be in progress by the same
> contributor. Given that LP doesn't currently support multiple
> assignees for a single bugtask (project+series) this is a little
> hard to map between Gerrit and LP. I have hopes that with
> Storyboard, we might get rid of Partial-Bug entirely since we should
> have better control over multi-part bugs with arbitrary related
> tasks.
> --
> Jeremy Stanley
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Anne Gentle
annegentle at justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140106/0ab1d018/attachment.html>