> On Dec 2, 2015, at 7:42 PM, Leif Hedstrom wrote:
>
> Hi all,
>
> I’d like to branch 6.1.x in about 1.5 weeks. In preparation for this, I’d ask
> everyone with open issues to look at your Jiras and PR’s, and do
>
> 1) If they truly need to be fixed for 6.1.x, mark it as “Blocker” or
>
Hi all,
I’d like to branch 6.1.x in about 1.5 weeks. In preparation for this, I’d ask
everyone with open issues to look at your Jiras and PR’s, and do
1) If they truly need to be fixed for 6.1.x, mark it as “Blocker” or
“Critical”.
2) If you know it doesn’t need to go to 6.1.x,
Just out of curiosity is the only way to close a github pull request still
to just make a phantom commit?
Brian
On Wed, Dec 2, 2015 at 4:41 PM, Luca Rea wrote:
> Hi,
> about... "To answer Bcall’s email, yes, Github comments ends up on the
> Jira, but not the other way around. So people reading
I've prepared a release for 6.0.1 (RC0) which is the next bug fix version of
Apache Traffic Server. This is detailed in our Release Management document:
https://cwiki.apache.org/confluence/display/TS/Release+Management
Release notes for 6.0.1:
https://issues.apache.org/jira/secure/ReleaseNote.
I've been exploring the implementation of the hook architecture in preparation
for some work on it I want to do. The issue that has come up is how hooks at
the various scopes (global, session, transaction) interact with regard to
locking. If you look at (for instance) the HttpSM logic to invoke
Github user sudheerv commented on the pull request:
https://github.com/apache/trafficserver/pull/350#issuecomment-161377617
Uri - I agree with your point in general as well, but, I think it's
arguable whether to treat this as a *feature* that isn't needed in the core. I
can say, with
Github user bryancall commented on the pull request:
https://github.com/apache/trafficserver/pull/350#issuecomment-161370254
@ushachar I added support for debugging in header_rewrite and it has the
ability to do client ip matching. As @SolidWallOfCode pointed out there may be
some us
GitHub user jrushf1239k opened a pull request:
https://github.com/apache/trafficserver/pull/359
TS-3418: Second hash ring for consistently hashed parent selection
This pull request is to add an optional secondary hash ring to parent
selection and is based upon feedback from James Pe
Github user SolidWallOfCode commented on the pull request:
https://github.com/apache/trafficserver/pull/350#issuecomment-161358854
Uri - it is not the case that header_rewrite can support the required use
case. There is no hook that is sufficiently early to enable pre-SSL accept
debug
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/358
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user zizhong commented on the pull request:
https://github.com/apache/trafficserver/pull/301#issuecomment-161340071
@jpeach you are right. Coping SSL related files can cause secure issues. In
my opinion, all the child files should not be copied. what do you think
handling it in
GitHub user Kenny690 opened a pull request:
https://github.com/apache/trafficserver/pull/358
Update getting-started.en.rst
Link update.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Kenny690/trafficserver patch-1
Alternatively
Hi,
about... "To answer Bcall’s email, yes, Github comments ends up on the Jira,
but not the other way around. So people reading and commenting there see the
entire thread, whereas people only reading the Github PR only sees “half” the
thread." ... perhaps you can try to enable email notificatio
13 matches
Mail list logo
