Re: Speaking of PRs...

Ed -

What would be the most helpful thing for people to take on?

It seems like there are some already-merged issues in -develop that might
need some build testing.

And those issues probably need a 2.2.1 tag, for change note sanity sake.

And then there's the task of identifing what to merge in next, tagging
those issues, merge, and test.

Is the first step to identify all the 2.2.1 issues, both resolved and
pending?

Karl

On Friday, April 15, 2016, Ed Hanway <[email protected]> wrote:

> Yes, I know they've been backing up and am looking at clearing a bit of
> time to process at least the obvious ones.  Anyone with some time who can
> help?
>
>
>
> -Ed
>
>
>
> *From:* Openexr-devel [mailto:openexr-devel-bounces+ehanway
> <javascript:_e(%7B%7D,'cvml','openexr-devel-bounces%2Behanway');>=
> [email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');>] *On
> Behalf Of *Karl Rasche
> *Sent:* Friday, April 15, 2016 12:50 PM
> *To:* [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>
> *Subject:* [Openexr-devel] Speaking of PRs...
>
>
>
>
>
> There's a fair number of little things which have come in since the 2.2
> release. Should we be thinking of trying to put together a 2.2.1 release at
> some point?
>
>
>
> Karl
>

_______________________________________________
Openexr-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-devel