Thanks Brennan.

We need one more binding vote from one of the 13 PMC members, and we can cut 
this release.

Derek

On 2/22/19, 3:48 PM, "Fieck, Brennan" <[email protected]> wrote:

    +1
    All the RPMs build and install properly, rudimentary operations in a toy 
environment seem to indicate everything's working fine.
    
    RE documentation concerns; this is missing quite a bit I'd wager, but I 
don't recommend we try to make the docs for 3.0.0 actually correct - it would 
mean duplicating work because some changes that are in master don't actually 
reflect the functionality of 3.0.0 and are, in general, inseparable from those 
that do.
    ________________________________________
    From: Dave Neuman <[email protected]>
    Sent: Tuesday, February 19, 2019 8:56 AM
    To: [email protected]
    Subject: Re: [EXTERNAL] [VOTE] Release Apache Traffic Control 3.0.0-RC6
    
    +1
    I verified:
    Signatures
    Sha512sum
    Built all components using the pkg command.
    
    On Mon, Feb 18, 2019 at 8:50 AM Gray, Jonathan <[email protected]>
    wrote:
    
    > +1
    >
    > Known Issues I had to adapt for:
    > The documentation for the API endpoint POST
    > /api/1.3/deliveryservices/sslkeys/add doesn't match TO, however TO and TP
    > match so I'm not -1.
    >
    > I verified:
    >     Using the RC6 tarball, I was able to produce a full set of RPMs
    >     Using those RPMs and normal external sources, I was able to install
    > the following topology inside VMs using global IP and DNS
    >     1 Traffic Ops
    >     1 Traffic Portal
    >     2 Traffic Routers
    >     4 Traffic Monitors
    >     1 Traffic Stats
    >     2 Traffic Vaults
    >     3 ATS Edges
    >     2 Grove Edges
    >     2 ATS Mids
    >
    > These were arranged in 1 CDN spanning 4 cachegroups with proper
    > configuration.
    > I also created 29 Delivery services spanning each Content Routing, each
    > Protocol, each steering/client steering target type, each QString, and
    > various combinations surrounding MSO.  Each of which returned a 200
    > response on a curl through the environment and observable via traffic 
stats
    > and the traffic portal dashboard.
    >
    > Jonathan G
    >
    >
    > On 2/13/19, 9:48 AM, "Gelinas, Derek" <[email protected]> wrote:
    >
    >     Hello All,
    >     I've prepared a release for v3.0.0-RC6
    >     The vote is open for at least 72 hours and passes if a majority of at
    > least 3 +1 PPMC votes are cast.
    >     [ ] +1 Approve the release
    >     [ ] -1 Do not release this package because ...
    >     Changes since 2.2
    >
    > https://github.com/apache/trafficcontrol/compare/2.2.x...RELEASE-3.0.0-RC6
    >     This corresponds to git:
    >     Hash: eca5d609dc5877e9abc075c0228e6e400473f564
    >     Tag: RELEASE-3.0.0-RC6
    >     Which can be verified with the following: git tag -v RELEASE-3.0.0-RC6
    >     My code signing key is available here:
    >     http://keys.gnupg.net/pks/lookup?search=0x05BE71D9&op=vindex
    >     Make sure you refresh from a key server to get all relevant 
signatures.
    >     The source .tgz file, pgp signature (.asc signed with my key from
    >     above), and sha512 checksums are provided here:
    >     https://dist.apache.org/repos/dist/dev/trafficcontrol/3.0.0/RC6/
    >     Thanks!
    >     Derek
    >
    >
    >
    >
    

Reply via email to