> On Feb 28, 2017, at 7:44 AM, Susan Hinrichs <shinr...@yahoo-inc.com.INVALID>
> wrote:
>
> I agree with Bryan. I have been testing in production without H2 (waiting
> for an internal plugin to upgrade). With three patches I am able to run for a
> couple hours without crashing. That crash is reported as issues 1480 and
> 1476.
> Sadly due to delays in getting our internal plugins upgraded, I have only
> been able to seriously work the 7.x build that last couple weeks. But 7.x
> is the top priority for our team right now
Alright, sounds like we have 2 teams on board, so lets make another attempt.
We’re obviously way behind on releases, but lets aim for a 3/31/2017 release of
v7.1.0, I’ll adjust that as necessary. That is 1.5 months delayed, so we’ll
also have to adjust (or decide) what to do with v7.2.0 at the Summit.
Regardless, this means we have to have a release candidate in 2 weeks, 3 tops.
I have created this “Project” on Github, to track the showstoppers / critical
issues for a v7.1.0 release as well as backport requests. Please edit and
comment as necessary:
https://github.com/apache/trafficserver/projects/3
<https://github.com/apache/trafficserver/projects/3>
And please (I mean, seriously) get into the habit of not closing / merging PRs
which are not properly tagged:
* Every merged PR must have a Milestone, and a Label. Preferably a
Reviewer / Assignee as well.
* Every merged PR should be reviewed.
* Every closed PR should either have an Issues associated with it, that
described the problem. Or, if there’s no issue, it must have a descriptive
Summary and/or Description.
This is critical, because without this, it makes it near impossible to produce
releases with accurate release notes and documentation.
Cheers,
— Leif
