We have some release blockers for 2.0. Specifically: TC-119: traffic_ops/client dependency license issue We cannot ship with Category-X LGPL software, so I’m waiting for this to be resolved before cutting a release branch "TC-185 post install doesn’t run due to missing perl module” We shouldn’t ship a release in which the install process is broken in this way. *There’s no assignee yet for this, any volunteers?*
I think if we can get those two taken care of we can cut an RC0 later this week. Major bugs we will ship with (unless someone objects): TC-203: Mojo doesn’t set cachable headers on public files” TC-190: TTL type mismatch in CrConfig TC-189: ssl_multicert.config too slow —Eric > On Apr 4, 2017, at 1:13 PM, Dave Neuman <neu...@apache.org> wrote: > > Good question. I would also like to see us try to get some release > candidates out for 2.0. I am pretty sure the actual install and > postinstall need work. There are also a couple of issue that are still > assigned to 2.0 and unresolved: > https://issues.apache.org/jira/browse/TC/fixforversion/12338562/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel > . > > On Tue, Apr 4, 2017 at 11:05 AM, Jan van Doorn <j...@knutsel.com> wrote: > >> When are we planning to release 2.0? We at Comcast are running what we >> call 2.0…. So we are +1, I am pretty sure. >> >> Eric: are you waiting for something? Which cats need herding? >> >> Rgds, >> JvD >> >>