You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by Suraj Acharya <su...@apache.org> on 2017/06/05 01:30:25 UTC

Closing out issues for the release.

As part of the release. I am to close all issues marked resolved in 1.8.2.
However, a few have been back ported to 1.7.8 and a few are on
master(1.9.0).
So i want to know if there is a better to close jira's marked as fixed in
1.8.2 only, other than going through each one of them and closing them
manually?

Thanks

S

Re: Closing out issues for the release.

Posted by suraj acharya <su...@gmail.com>.
I am not sure.
It was one of those steps on the guide.
It is the only one left for me to finish.

-Suraj Acharya

On Mon, Jun 5, 2017 at 4:50 PM, Sean Busbey <bu...@cloudera.com> wrote:

> what do we gain by marking them closed instead of leaving them resolved?
>
> On Sun, Jun 4, 2017 at 8:30 PM, Suraj Acharya <su...@apache.org> wrote:
> > As part of the release. I am to close all issues marked resolved in
> 1.8.2.
> > However, a few have been back ported to 1.7.8 and a few are on
> > master(1.9.0).
> > So i want to know if there is a better to close jira's marked as fixed in
> > 1.8.2 only, other than going through each one of them and closing them
> > manually?
> >
> > Thanks
> >
> > S
>
>
>
> --
> busbey
>

Re: Closing out issues for the release.

Posted by Sean Busbey <bu...@cloudera.com>.
what do we gain by marking them closed instead of leaving them resolved?

On Sun, Jun 4, 2017 at 8:30 PM, Suraj Acharya <su...@apache.org> wrote:
> As part of the release. I am to close all issues marked resolved in 1.8.2.
> However, a few have been back ported to 1.7.8 and a few are on
> master(1.9.0).
> So i want to know if there is a better to close jira's marked as fixed in
> 1.8.2 only, other than going through each one of them and closing them
> manually?
>
> Thanks
>
> S



-- 
busbey