Re: [VOTE] Release Apache Traffic Control 2.0.0-incubating (RC4)

you're right -- it shouldn't.. thanks! On Thu, Jun 8, 2017 at 10:39 AM, Hank Beatty wrote: > I just realized it is our cdn.conf that doesn't have the secrets in it not > the default. Still don't think it should error. I'll fix it and submit the > PR. > > On 06/08/2017 11:30

Re: [VOTE] Release Apache Traffic Control 2.0.0-incubating (RC4)

I just realized it is our cdn.conf that doesn't have the secrets in it not the default. Still don't think it should error. I'll fix it and submit the PR. On 06/08/2017 11:30 AM, Dan Kirkwood wrote: not that I'm aware of... please do file an issue for it, though and attach that to the PR.

Re: [VOTE] Release Apache Traffic Control 2.0.0-incubating (RC4)

postinstall might still be broken: Password for database server admin: Re-Enter Password for database server admin: Download Maxmind Database? [yes]: Download Maxmind Database?: yes ===/opt/traffic_ops/app/conf/cdn.conf=== Generate a new secret? [yes]: Generate a new secret?: yes

Project Management for Issues and Releases

All, I wanted to open up a dialogue on how we consistently manage issues and releases. This is a fairly broad topic covering things like: workflow, fields, reporting and release management. I have summarized key topics here:

Re: Data patches during upgrade

This seems to make sense to me but honestly, I'd probably defer to Dewayne. In theory, it would be nice if migrations only included "structural" changes (new tables, columns, changing column types or not null, etc) and seeds focused on the "base" (or the minimum required) static data required of