Hi Eric.
On Fri, 26 Jan 2018 11:29:50 +0100, Eric Barnhill wrote:
First of all, AFAICT, none of the issues I worked on have ever been
marked
"resolved".
As a matter of principle, no issue can be "resolved" if it would
imply a code change and said change was not merged into the "master"
branch.
My understanding was that you had been working on a separate branch
for the porting work, and I was assuming that you were going to
merge it into "master" whenever you deemed it right.
We discussed a few things and I don't recall that we disagreed on
anything for "Complex"; IIRC, I only had some reservation about the
performance of the numerous methods in "ComplexUtils". When nobody
objects within say 2 weeks, then no need to wait forever before
merging since you have committer access!
I don't believe I have the power to mark them this way myself.
If further progress is blocked by something beyond your reach, you
should not hesitate to ping this list as many times as necessary. ;-)
I remember that there was a problem with changing the state of JIRA
issues; I also seem to recall that I relayed it here since I didn't
have the privilege for fixing it. If the problem persisted, would
you please post again here a message that describes it?
Best regards,
Gilles
Eric
On Fri, Jan 26, 2018 at 1:49 AM, Gilles
<[email protected]>
wrote:
Hello.
JIRA lists 12 unresolved issues for the v1.0 target.
After quite a lot of nice work, nearly zero activity in
the last 6 months...
Regards,
Gilles
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
