Yes, the main help I could use is testing the develop branch across various platforms.
My plan is to keep 2.2.1 limited to build failures and low risk bug fixes, where "low risk" means that there's essentially no risk of a regression when moving from 2.2.0 to 2.2.1 in any application. I've made a pass at updating the open issues targeted at the v2.2.1 milestone. Please let me know if there are some others worth including that meet these criteria. If we can't get test coverage for a platform, like MinGW, we may not be able to close out an issue. Somebody reported a failure on m68k last week. I was a big fan of the 680x0 back in its day, but today I can't even find one being used as a doorstop, so I'm not optimistic about that one. Also, if anybody has -- or wishes to -- submit a pull request, and has not sent a Contributor License Agreement to ILM, please fill out the appropriate (individual or corporate) form from http://www.openexr.com/documentation.html and send/email/fax per the instructions in the form. Email me if you're unsure if your company has already done so. Thanks, -Ed From: Karl Rasche [mailto:[email protected]] Sent: Saturday, April 16, 2016 8:34 AM To: Ed Hanway Cc: [email protected] Subject: 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]<mailto:[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
