Damjan Jovanovic wrote:
[-1] Disapprove
That's bad! Let's see if we can manage to explain it and at least get a
0, since I don't see anything really blocking in your reports (I mean,
we do not require that the release has no issues at all, and we agree
that what we are releasing is better
Ok, I am changing my vote to:
[0] Abstain
See below for details.
On Sun, Oct 25, 2015 at 10:10 AM, Andrea Pescetti
wrote:
> Damjan Jovanovic wrote:
>
>> [-1] Disapprove
>>
>
> That's bad! Let's see if we can manage to explain it and at least get a 0,
> since I don't see
Damjan Jovanovic wrote:
Ok, I am changing my vote to:
[0] Abstain
Thanks for your understanding.
I suppose since the file is generated, unused, and was present in previous
releases, it shouldn't stop this release. ...
since the file is a generated file and not a source file, that may not
I don't see the "...Env.Set.sh" file as code file and therefore the
rules don't apply here. But to be super-sure just delete the generated
file(s) from the source tar balls and rebuild only these new.
And +1 for extending the release notes with the other issues that affect
the binaries.