With 9 binding +1, 4 non-binding +1, and no other votes, this vote
passed. I'll get the artifacts uploaded as soon as I can.
--
Warm regards,
Michael
On 07/25/2018 12:16 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.11.3.
>
> sha1:
With 9 binding +1, 3 non-binding +1, and no other votes, this vote
passed. I'll get the artifacts uploaded as soon as I can.
--
Warm regards,
Michael
On 07/25/2018 12:17 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.17.
>
> sha1:
With 9 binding +1, 2 non-binding +1, and no other votes, this vote
passed. I'll get the artifacts uploaded as soon as I can.
--
Warm regards,
Michael
On 07/25/2018 12:17 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 2.2.13.
>
> sha1:
It is useful to have a historical record. However, it could definitely be
better (huge diffs are pointless).
Thanks,
Dinesh
On Monday, July 30, 2018, 1:27:26 AM PDT, Stefan Podkowinski
wrote:
Looks like we had some active PRs recently to discuss code changes in
detail on GitHub,
Hi,
I really like having it mirrored. I would not be in favor of eliminating
automated mirroring. What we are seeing is that removing the pain of commenting
in JIRA is encouraging people to converse more in finer detail. That's a good
thing.
I have also seen the pain of how various github
I agree this is a mess. I think we have previously taken the view that JIRA
should be the permanent record of discussion, and that as such the git
conversation should be duplicated there.
However, I think it would be better for JIRA to get a summary of important
discussions, by one of the
On 30.07.2018 02:04, Scott Andreas wrote:
> I’m curious on the dev community’s thoughts on how best to organize
> information like this. My thinking is that by having a space to share this,
> the community can be more informed on each others’ work toward testing, build
> health, and active
Looks like we had some active PRs recently to discuss code changes in
detail on GitHub, which I think is something we agreed is perfectly
fine, in addition to the usual Jira ticket.
What bugs me a bit is that for some reasons any comments on the PR would
be posted to the Jira ticket as well. I'm
