[seam-dev] question about issue workflow

Stuart Douglas stuart.w.douglas at gmail.com
Tue Oct 19 01:37:03 EDT 2010


I have been marking it as resolved when I add the pull request URL,
and Pete has been closing them after the changes have been merged.

This seems to work fairly well. I don't think we need to go 'Pull
Request Available' -> 'Resolved' -> 'Closed', as you will generally
want to close the issue after the code has been accepted into trunk.

Stuart

On Tue, Oct 19, 2010 at 4:23 PM, Dan Allen <dan.j.allen at gmail.com> wrote:
> When a contributor has submitted a pull request as a candidate resolution to
> an issue, what issue state should the issue be put into?
> I'd like to suggest that we introduce a new state that indicates a pull
> request is pending and a review and, if accepted, merge is necessary. This
> state could be interpreted as a soft "Resolved".
> -Dan
>
> --
> Dan Allen
> Principal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>



More information about the seam-dev mailing list