and are not
necessarily cumulative. In the idea of reducing overhead it makes sense to
mention that case explicitly.
Have fun,
JensG
-Ursprüngliche Nachricht-
From: James E. King III
Sent: Sunday, February 17, 2019 6:17 PM
To: dev@thrift.apache.org
Subject: Re: [DISCUSSION] JIRA-Tickets vs. Patches &
I don't think a ticket per pull request is appropriate for things like
typos, modifications to documentation, simple modifications to the CI
environment, or to code comments.
For example if I move the bionic build jobs from go 1.11.4 to 1.11.5, that
should not require a ticket. It's just noise in
Hi all,
a few days ago Jim raised the question about the policy regarding JIRA tickets.
As I am not fully happy with either solution we practiced so far, I gave it a
second thought.
So here’s my proposal:
1. We have one ticket per patch or pull request.
2. Minor changes may
