Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

[Dan Kirkwood]

Dave,  did you mean for this to be for 2.1.0 RC2?You replied to
the wrong email..

-dan

On Mon, Nov 20, 2017 at 11:13 AM, Dave Neuman  wrote:
> +1 However
> We need to add a release note suggesting that traffic stats works best with
> influxdb version < 1.3.x.  As of 1.3.x InfluxDB now returns a 400 response
> when the client attempts to write points that are outside of the retention
> policy.  When this happens, Traffic Stats seems to hold on to the "old"
> points and attempts to write them again on the next POST.  This causes what
> is essentially a memory leak in Traffic Stats since it continues to hold
> onto and tries to write stats that are outside of the retention policy.
> This may or may not affect a user, depending upon which stats they are
> trying to write to influxdb.  For example, we write the wrap_count to
> influxdb, this is a stat that does not often change within 24 hours, so we
> see the memory leak with stats not written on each poll of traffic stats.
>
> In versions < 1.3.x InfluxDB would still not write the point, but it would
> accept the write request and just drop the points outside of the retention
> policy on the floor.
>
> This is fixed here:
> https://github.com/apache/incubator-trafficcontrol/pull/1289 and will be in
> the next release of traffic control.
>
> Also, we should note that you need to set selinux to "unenforcing" in order
> to get the build to work, otherwise you fail on permissions erros.  You can
> do this with
> `setenforce 0` as root.
>
>
> Thanks,
> Dave
>
> On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
> efrie...@cisco.com> wrote:
>
>> Dear IPMC Community,
>>
>> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6 of
>> Apache Traffic Control (Incubating) for release as “Apache Traffic Control
>> (incubating) 2.0.0"
>>
>> The vote has passed with:
>> - three binding "+1" votes
>> - no "0" votes
>> - no "-1" votes
>>
>> The votes were (https://lists.apache.org/thread.html/
>> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
>> 3Cgeneral.incubator.apache.org%3E> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@> neral.incubator.apache.org>>):
>> - +1, Justin Mclean (binding)
>> - +1, John D. Ament (binding)
>> - +1, Phil Sorber (binding)
>>
>> Thank you, for your support!
>>
>> —Eric
>>
>> On Jun 30, 2017, at 5:27 PM, Phil Sorber mailto:sorb
>> e...@apache.org>> wrote:
>>
>> Checksums match.
>>
>> GPG sig verifies, but is untrusted:
>> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
>> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
>> incubating.tar.gz'
>> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
>> 9AB7BDD5
>> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
>> fri...@apache.org>"
>> gpg: WARNING: This key is not certified with a trusted signature!
>> gpg:  There is no indication that the signature belongs to the
>> owner.
>> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7 BDD5
>>
>> No signatures:
>> $ gpg --list-sigs 9AB7BDD5
>> pub   4096R/9AB7BDD5 2017-04-25
>> uid  Eric Friedrich (CODE SIGNING KEY) > >
>> sig 39AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
>> fri...@apache.org>
>> sub   4096R/F445ABB1 2017-04-25
>> sig  9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
>> fri...@apache.org>
>>
>> I won't -1 on that, but we should try to have every RM make sure their keys
>> are trusted. I've already spoken with Eric about this.
>>
>> Build also works, with one caveat. You have to set selinux to unenforcing,
>> otherwise you fail from permissions errors. You can do this with
>> `setenforce 0` as root. I won't -1 for this either, but we should add that
>> to the build documentation.
>>
>> -rw-r--r--. 1 phil phil  51M Jun 30 15:12
>> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
>> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
>> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil  22K Jun 30 15:10
>> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil  21K Jun 30 15:10
>> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
>> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
>> traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil  17M Jun 30 15:12
>> traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 417K Jun 30 15:11
>> traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
>> traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>>
>> +1 binding.
>>
>> Thanks!
>>
>> On Wed, Jun 28, 2017 at 5:20 PM Justin Mclea

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

[Dan Kirkwood]

Justin,  the build instructions are there in BUILD.md,  which
references the above non-existent link (it will exist once we release)
and the rst file local to the source tree:
docs/source/development/building.rst

Those few copyright issues did slip by us -- filing an issue to get
that corrected for the next release.

thanks.. Dan

On Tue, Jun 27, 2017 at 6:56 PM, Justin Mclean  wrote:
> Hi,
>
> +0 binding as I can’t build from source and no instructions provided.
>
> I will change to +1 when I can compile/ you raise a JIRA to add instructions 
> on how to build.
>
> I checked:
> - signatures and hashes good
> - DISCLAIMER exists
> - LICENSE good
> - NOTICE OK . You can remove the information about the fonts in there it’s 
> not needed.
> - No unexpected binary files
> - All source files have headers (there's a few script files and other files 
> that could also have headers)
> - can't build from source
>
> when running the build.sh script it eventually fails with this error
>
> cp: ./build/*.spec: No such file or directory
> Could not copy spec files: 1
> traffic_stats failed:
> The following subdirectories had errors:
>traffic_monitor
>traffic_monitor_golang
>traffic_ops
>traffic_portal
>traffic_router
>traffic_stats
>
> Has perhaps something not been included in the release or is my environment 
> not set up correctly?
>
> It would be nice to include the build instructions in the build itself. I 
> believe this has come up before. By providing a URL it means that the content 
> of that URL may change for future releases and people would be unable to 
> build this release. In fact the URL in the documentation is incorrect [1] and 
> currently 404s which is less than helpful.
>
> There a few file still copyright comcast I assume these need to be removed? 
> [2][3][4][5][6]
>
> Thanks,
> Justin
>
> 1. 
> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
> 2. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
> 3. 
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
> 4. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
> 5. 
> ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/github.com/jheitz200/test_helper/http.go
> 6. 
> ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/github.com/jheitz200/test_helper/test.go
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Dan Kirkwood]

actually,   I take that back..   the "dist" directory contains all the
rpm artifacts and a log file for each of the components.

I think ./pkg needs to point that out,  and perhaps even display the
contents of that directory.   Filing an issue for that..

-dan

On Wed, Jun 28, 2017 at 1:30 PM, Dan Kirkwood  wrote:
> unfortunately,  no log  -- -v is the only way to get it.  That's
> something I'd like to have,  so I'll put in a Jira issue for that as
> well.
>
> On Wed, Jun 28, 2017 at 1:28 PM, John D. Ament  wrote:
>> On Wed, Jun 28, 2017 at 3:26 PM Dan Kirkwood  wrote:
>>
>>> Thanks John and Justin..Eric's out for a few days,  but I can work
>>> on getting some of these things addressed.
>>>
>>> The build instructions will be put in place once the release is done
>>> -- catch-22..  but I should be able to add a reference to the local
>>> rst file as well.   Would Jira issues for the copyright and build
>>> instruction issues be sufficient?  Or would you prefer to see another
>>> RC to address those?
>>>
>>> The `./pkg` is the simplest way to build.   If you give that a `-v`,
>>> it will spill all the output to stdout so you can see where it's
>>> erroring out.   We are able to build it,  so not sure where the issue
>>> lies with building the traffic_portal.
>>>
>>
>> Is there a log to look at the failure?
>>
>> Either way I'm fine with releasing as is, so +1.
>>
>>
>>>
>>> -dan
>>>
>>> On Tue, Jun 27, 2017 at 6:59 PM, John D. Ament 
>>> wrote:
>>> > On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean 
>>> > wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> +0 binding as I can’t build from source and no instructions provided.
>>> >>
>>> >
>>> > I struggled with this a bit as well.  The BUILD.md indicates:
>>> >
>>> > See the build instructions at ./docs/source/development/building.rst or
>>> at
>>> >
>>> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>>> >
>>> > That URL doesn't work, but the rst file indicates running pkg does the
>>> > build.
>>> >
>>> > However, when I run pkg, I get the following:
>>> >
>>> > ~/Desktop/apache-trafficcontrol-2.0.0-incubating
>>> > ☺  ./pkg
>>> >
>>> >
>>> >
>>> > Building traffic_portal_build.
>>> > Building traffic_router_build.
>>> > Building traffic_monitor_build.
>>> > Building source.
>>> > Building traffic_ops_build.
>>> > Building traffic_stats_build.
>>> > Failed to build traffic_portal_build.
>>> >
>>> >
>>> >>
>>> >> I will change to +1 when I can compile/ you raise a JIRA to add
>>> >> instructions on how to build.
>>> >>
>>> >> I checked:
>>> >> - signatures and hashes good
>>> >> - DISCLAIMER exists
>>> >> - LICENSE good
>>> >> - NOTICE OK . You can remove the information about the fonts in there
>>> it’s
>>> >> not needed.
>>> >> - No unexpected binary files
>>> >> - All source files have headers (there's a few script files and other
>>> >> files that could also have headers)
>>> >> - can't build from source
>>> >>
>>> >> when running the build.sh script it eventually fails with this error
>>> >>
>>> >> cp: ./build/*.spec: No such file or directory
>>> >> Could not copy spec files: 1
>>> >> traffic_stats failed:
>>> >> The following subdirectories had errors:
>>> >>traffic_monitor
>>> >>traffic_monitor_golang
>>> >>traffic_ops
>>> >>traffic_portal
>>> >>traffic_router
>>> >>traffic_stats
>>> >>
>>> >> Has perhaps something not been included in the release or is my
>>> >> environment not set up correctly?
>>> >>
>>> >> It would be nice to include the build instructions in the build itself.
>>> I
>>> >> believe this has come up before. By providing a URL it means that the
>>> >> content of that URL may change for future releases and people would be
>>> >> unable to build this release

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

[Dan Kirkwood]

unfortunately,  no log  -- -v is the only way to get it.  That's
something I'd like to have,  so I'll put in a Jira issue for that as
well.

On Wed, Jun 28, 2017 at 1:28 PM, John D. Ament  wrote:
> On Wed, Jun 28, 2017 at 3:26 PM Dan Kirkwood  wrote:
>
>> Thanks John and Justin..Eric's out for a few days,  but I can work
>> on getting some of these things addressed.
>>
>> The build instructions will be put in place once the release is done
>> -- catch-22..  but I should be able to add a reference to the local
>> rst file as well.   Would Jira issues for the copyright and build
>> instruction issues be sufficient?  Or would you prefer to see another
>> RC to address those?
>>
>> The `./pkg` is the simplest way to build.   If you give that a `-v`,
>> it will spill all the output to stdout so you can see where it's
>> erroring out.   We are able to build it,  so not sure where the issue
>> lies with building the traffic_portal.
>>
>
> Is there a log to look at the failure?
>
> Either way I'm fine with releasing as is, so +1.
>
>
>>
>> -dan
>>
>> On Tue, Jun 27, 2017 at 6:59 PM, John D. Ament 
>> wrote:
>> > On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean 
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> +0 binding as I can’t build from source and no instructions provided.
>> >>
>> >
>> > I struggled with this a bit as well.  The BUILD.md indicates:
>> >
>> > See the build instructions at ./docs/source/development/building.rst or
>> at
>> >
>> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>> >
>> > That URL doesn't work, but the rst file indicates running pkg does the
>> > build.
>> >
>> > However, when I run pkg, I get the following:
>> >
>> > ~/Desktop/apache-trafficcontrol-2.0.0-incubating
>> > ☺  ./pkg
>> >
>> >
>> >
>> > Building traffic_portal_build.
>> > Building traffic_router_build.
>> > Building traffic_monitor_build.
>> > Building source.
>> > Building traffic_ops_build.
>> > Building traffic_stats_build.
>> > Failed to build traffic_portal_build.
>> >
>> >
>> >>
>> >> I will change to +1 when I can compile/ you raise a JIRA to add
>> >> instructions on how to build.
>> >>
>> >> I checked:
>> >> - signatures and hashes good
>> >> - DISCLAIMER exists
>> >> - LICENSE good
>> >> - NOTICE OK . You can remove the information about the fonts in there
>> it’s
>> >> not needed.
>> >> - No unexpected binary files
>> >> - All source files have headers (there's a few script files and other
>> >> files that could also have headers)
>> >> - can't build from source
>> >>
>> >> when running the build.sh script it eventually fails with this error
>> >>
>> >> cp: ./build/*.spec: No such file or directory
>> >> Could not copy spec files: 1
>> >> traffic_stats failed:
>> >> The following subdirectories had errors:
>> >>traffic_monitor
>> >>traffic_monitor_golang
>> >>traffic_ops
>> >>traffic_portal
>> >>traffic_router
>> >>traffic_stats
>> >>
>> >> Has perhaps something not been included in the release or is my
>> >> environment not set up correctly?
>> >>
>> >> It would be nice to include the build instructions in the build itself.
>> I
>> >> believe this has come up before. By providing a URL it means that the
>> >> content of that URL may change for future releases and people would be
>> >> unable to build this release. In fact the URL in the documentation is
>> >> incorrect [1] and currently 404s which is less than helpful.
>> >>
>> >> There a few file still copyright comcast I assume these need to be
>> >> removed? [2][3][4][5][6]
>> >>
>> >> Thanks,
>> >> Justin
>> >>
>> >> 1.
>> >>
>> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>> >> 2.
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
>> >> 3.
>> >>
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
>> >> 4.
>> >>
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
>> >> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>> >> github.com/jheitz200/test_helper/http.go
>> >> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>> >> github.com/jheitz200/test_helper/test.go
>> >>
>> >>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Dan Kirkwood]

Thanks John and Justin..Eric's out for a few days,  but I can work
on getting some of these things addressed.

The build instructions will be put in place once the release is done
-- catch-22..  but I should be able to add a reference to the local
rst file as well.   Would Jira issues for the copyright and build
instruction issues be sufficient?  Or would you prefer to see another
RC to address those?

The `./pkg` is the simplest way to build.   If you give that a `-v`,
it will spill all the output to stdout so you can see where it's
erroring out.   We are able to build it,  so not sure where the issue
lies with building the traffic_portal.

-dan

On Tue, Jun 27, 2017 at 6:59 PM, John D. Ament  wrote:
> On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> +0 binding as I can’t build from source and no instructions provided.
>>
>
> I struggled with this a bit as well.  The BUILD.md indicates:
>
> See the build instructions at ./docs/source/development/building.rst or at
> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>
> That URL doesn't work, but the rst file indicates running pkg does the
> build.
>
> However, when I run pkg, I get the following:
>
> ~/Desktop/apache-trafficcontrol-2.0.0-incubating
> ☺  ./pkg
>
>
>
> Building traffic_portal_build.
> Building traffic_router_build.
> Building traffic_monitor_build.
> Building source.
> Building traffic_ops_build.
> Building traffic_stats_build.
> Failed to build traffic_portal_build.
>
>
>>
>> I will change to +1 when I can compile/ you raise a JIRA to add
>> instructions on how to build.
>>
>> I checked:
>> - signatures and hashes good
>> - DISCLAIMER exists
>> - LICENSE good
>> - NOTICE OK . You can remove the information about the fonts in there it’s
>> not needed.
>> - No unexpected binary files
>> - All source files have headers (there's a few script files and other
>> files that could also have headers)
>> - can't build from source
>>
>> when running the build.sh script it eventually fails with this error
>>
>> cp: ./build/*.spec: No such file or directory
>> Could not copy spec files: 1
>> traffic_stats failed:
>> The following subdirectories had errors:
>>traffic_monitor
>>traffic_monitor_golang
>>traffic_ops
>>traffic_portal
>>traffic_router
>>traffic_stats
>>
>> Has perhaps something not been included in the release or is my
>> environment not set up correctly?
>>
>> It would be nice to include the build instructions in the build itself. I
>> believe this has come up before. By providing a URL it means that the
>> content of that URL may change for future releases and people would be
>> unable to build this release. In fact the URL in the documentation is
>> incorrect [1] and currently 404s which is less than helpful.
>>
>> There a few file still copyright comcast I assume these need to be
>> removed? [2][3][4][5][6]
>>
>> Thanks,
>> Justin
>>
>> 1.
>> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>> 2. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
>> 3.
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
>> 4.
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
>> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>> github.com/jheitz200/test_helper/http.go
>> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>> github.com/jheitz200/test_helper/test.go
>>
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Release Apache Traffic Control 1.8.1-incubating

[Dan Kirkwood]

The vote passes with three +1 and no -1 votes.

Thanks!

The Apache Traffic Control (Incubating) team

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Release Apache Traffic Control 1.8.1 (Incubating)

[Dan Kirkwood]

The Apache Traffic Control team would like to announce the release of
Apache Traffic Control 1.8.1 (incubating).

More details regarding Apache Traffic Control can be found at:
http://trafficcontrol.incubator.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/1.8.1-incubating/

The release notes can be found here:
http://trafficcontrol.incubator.apache.org/downloads/index.html

Thanks!
The Apache Traffic Control Team


Apache Traffic Control is an effort undergoing Incubation at The
Apache Software Foundation (ASF), sponsored by the Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control 1.8.1-incubating (RC0)

[Dan Kirkwood]

Thanks for that feedback -- I'll make sure our release instructions
are clear on those points and remove users@ from any future votes.

> The draft release notes (along with links to artifacts,
> signatures/checksums, and updated documentation) can be found here:
>
> http://trafficcontrol.incubator.apache.org/downloads/

To clarify,  this is misstated: the artifacts for this release are not
there -- they will be placed at that location once the release is
approved and not before.  The previous (approved) release artifacts
are at that location.

-dan


On Mon, Jun 5, 2017 at 3:49 PM, sebb  wrote:
> On 5 June 2017 at 22:12, Dan Kirkwood  wrote:
>
> DROPPED user@ list - see below.
>
>> Hello Incubator PMC,
>>
>> The Apache Traffic Control community has voted on and approved a
>> proposal to release Apache Traffic Control 1.8.1-incubating. We now
>> kindly request that the Incubator PMC members review and vote on this
>> incubator release.
>>
>> The VOTE RESULT is here:
>>
>> https://lists.apache.org/thread.html/c43fe387586c44e2ecbac1f968a146f9a402a328be0f6e9b296fc3c9@%3Cusers.trafficcontrol.apache.org%3E
>>
>> The draft release notes (along with links to artifacts,
>> signatures/checksums, and updated documentation) can be found here:
>>
>> http://trafficcontrol.incubator.apache.org/downloads/
>
> This is a *public* URL.
> However the release has not yet been approved, so it must *not* be published.
> For the same reason, the email regarding the RC should not be sent to
> the user list.
>
> Also the download page points to
>
> https://dist.apache.org/repos/dist/
>
> The dist repo is a staging repo only, and must not be used for public URLs.
>
>> The git tag for the repository is "RELEASE-1.8.1-RC0":
>> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.1-RC0
>>
>> The source distribution (also linked in the release notes) is here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.1/RC0/
>
> That URL is fine for RC vote mails
>
>> Build instructions are included in the BUILD.md file which is included
>> in the source artifact.
>>
>> Artifacts have been signed with the "dang...@apache.org" key listed in:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>
> That URL is fine for RC vote mails
>
>> Please review and vote:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Don't approve the release (please provide specific comments)
>>
>> This vote will be open for at least 72 hours.
>>
>> Thanks,
>>
>>  Dan Kirkwood 
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Traffic Control 1.8.1-incubating (RC0)

[Dan Kirkwood]

Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 1.8.1-incubating. We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/c43fe387586c44e2ecbac1f968a146f9a402a328be0f6e9b296fc3c9@%3Cusers.trafficcontrol.apache.org%3E

The draft release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

The git tag for the repository is "RELEASE-1.8.1-RC0":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.1-RC0

The source distribution (also linked in the release notes) is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.1/RC0/

Build instructions are included in the BUILD.md file which is included
in the source artifact.

Artifacts have been signed with the "dang...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

Please review and vote:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

 Dan Kirkwood 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Jenkins access

[Dan Kirkwood]

Hi,

My apologies if this is the wrong forum to ask..Can someone please
add permission for the users dangogh and neuman to modify Jenkins
configuration for the incubator-trafficcontrol project?

thanks..   Dan

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Release Apache Traffic Control 1.8.0 (incubating)

[Dan Kirkwood]

The Apache Traffic Control team would like to announce the release of
Apache Traffic Control 1.8.0 (incubating).

More details regarding Apache Traffic Control can be found at:
http://trafficcontrol.incubator.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/1.8.0-incubating/

The release notes can be found here:
http://trafficcontrol.incubator.apache.org/downloads/index.html

Thanks!
The Apache Traffic Control Team


Apache Traffic Control is an effort undergoing Incubation at The
Apache Software Foundation (ASF), sponsored by the Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC11)

[Dan Kirkwood]

Sorry -- I used the same template as the previous RC..  A couple of
the descriptions of links above are not accurate,  but the content is
correct:

The updated documentation can be found here:
http://trafficcontrol.incubator.apache.org

The source distribution along with checksums and signature (using the
dang...@apache.org key) is here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC11/



On Tue, Feb 21, 2017 at 9:06 AM, Dan Kirkwood  wrote:
> Hello Incubator PMC,
>
> The Apache Traffic Control community has voted on and approved a
> proposal to release Apache Traffic Control 1.8.0-incubating.  We now
> kindly request that the Incubator PMC members review and vote on this
> incubator release.
>
> The VOTE RESULT is here:
>
> https://lists.apache.org/thread.html/dc3ba61d2834579a6e7237df08d828b61011a6cb087e1948be70c78a@%3Cdev.trafficcontrol.apache.org%3E
>
> The draft release notes (along with links to artifacts,
> signatures/checksums, and updated documentation) can be found here:
>
> http://trafficcontrol.incubator.apache.org/downloads/
>
> The git tag for the repository is "RELEASE-1.8.0-RC11":
> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC11
>
> The source distribution (also linked in the release notes) is here:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC11/
>
> Build instructions are included in the BUILD.md file which is included
> in the source artifact.
>
> Artifacts have been signed with the "dang...@apache.org" key listed in:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>
> Please review and vote:
>
> [  ] +1 Approve the release
> [  ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
>
> - Dan

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Traffic Control 1.8.0-incubating (RC11)

[Dan Kirkwood]

Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 1.8.0-incubating.  We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/dc3ba61d2834579a6e7237df08d828b61011a6cb087e1948be70c78a@%3Cdev.trafficcontrol.apache.org%3E

The draft release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

The git tag for the repository is "RELEASE-1.8.0-RC11":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC11

The source distribution (also linked in the release notes) is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC11/

Build instructions are included in the BUILD.md file which is included
in the source artifact.

Artifacts have been signed with the "dang...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

Please review and vote:

[  ] +1 Approve the release
[  ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

- Dan

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)

[Dan Kirkwood]

Thanks,   John..we do have a new PR that intends to address these
issues (currently only in master):
https://github.com/apache/incubator-trafficcontrol/pull/285

I intend to examine that tomorrow morning and pull it in to 1.8 if all
looks good -- there will be a few changes needed to address diffs
between 1.8 and master,  but not significant.   If you have a chance
to look at that PR and give a thumbs-up,  it would help greatly..

thanks for all your help.. Dan

On Wed, Feb 15, 2017 at 5:37 PM, John D. Ament  wrote:
> On Wed, Feb 15, 2017 at 5:10 PM Marvin Humphrey 
> wrote:
>
>> On Wed, Feb 15, 2017 at 1:00 PM, John D. Ament 
>> wrote:
>> > On Wed, Feb 15, 2017 at 3:05 PM Marvin Humphrey 
>> > wrote:
>> >
>> >> On Wed, Feb 15, 2017 at 11:58 AM, Dan Kirkwood 
>> wrote:
>>
>> > Personally, the reason why I'm asking about the impact is to better make
>> a
>> > judgment call on whether to block or not.  I don't particularly see why
>> > we're now being jumped on over this fact.
>>
>> John,
>>
>> My email was rushed because I wanted to preempt cancellation of the
>> vote. I see now that it can be read in a more confrontational tone
>> than was meant.
>>
>> Thank you very much for taking the time to review the release
>> candidate. I'll make the case for more lenience in general when
>> approving incubating release candidates on a separate thread later
>> today.
>>
>
> Marvin,
>
> Its OK.  I myself am frazzled over lots of things going on around me.  So I
> know some of my responses as of late have either been way too
> short/confrontational and too long/fillibustery.  So I know where you're
> coming from.
>
> I look forward to arguing with you over podling releases in a separate
> thread.
>
> Dan,
>
> So here's my point of view.  Justin's provided some more context on how to
> shape licenses.  If you feel very strongly that the release should go out
> the door, the way it is, then I am OK with changing my vote to a +1.  If
> however, you're like me, and would prefer accuracy over speed, I think its
> worth your time to fix the remaining license issues, package up a CR10, and
> see that the IPMC votes +1 without reservations (it gives better confidence
> that you can cut an ASF release).
>
> I'm even willing to help you rewrite your license file for accuracy.
>
> John
>
>
>>
>> Marvin Humphrey
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)

[Dan Kirkwood]

You're right -- fixing the license file is not a huge effort (now that
we understand what's expected..).  The effort is in going thru the
voting process again..

I'll go with whatever you recommend..

thanks.. Dan

On Wed, Feb 15, 2017 at 10:58 AM, John D. Ament  wrote:
> I'd like to know the effort required from your POV to fix the license
> file.  Alex's description matches my expectations, thanks for clarifying
> it.  I would rather not create a release that didn't match the licensing
> requirements, but will be OK if you come back saying its a huge effort
> (however, I can't imagine copy and pasting license contents is difficult).
>
> On Wed, Feb 15, 2017 at 12:14 PM Dan Kirkwood  wrote:
>
>> Thanks,  Alex..
>>
>> John -- would it be reasonable to fix this in the next release barring
>> any other major issues?
>>
>> thanks..  Dan
>>
>> On Wed, Feb 15, 2017 at 9:34 AM, Alex Harui  wrote:
>> >
>> >
>> > On 2/15/17, 7:40 AM, "Dan Kirkwood"  wrote:
>> >
>> >>Thanks,  John..   I'm confused on this.   According to
>> >>http://www.apache.org/dev/licensing-howto.html#permissive-deps :
>> >>
>> >>`In LICENSE, add a pointer to the dependency's license within the
>> >>distribution and a short note summarizing its licensing:`
>> >>
>> >>Is MIT a special case in this regard?  And in that case,  do we need a
>> >>separate full license entry for each MIT-licensed component we use?
>> >>Is this RC acceptable other than the license issues you pointed out?
>> >
>> > AIUI, a "pointer" is the text from that web page:
>> >
>> > This product bundles SuperWidget 1.2.3, which is available under a
>> > MIT license.  For details, see deps/superwidget/LICENSE.txt.
>> >
>> > Your build/packaging should copy the dependency's MIT License into a file
>> > in the release package.  MIT-licensed projects are supposed to have their
>> > own copy of the MIT license in their release distributions with a
>> > project-specific copyright.  The pointer isn't supposed to be a
>> > third-party URL since URLs are not stable, although I would have probably
>> > advised you to fix that in the next release.  IMO, it isn't a major flaw
>> > for an incubating release.
>> >
>> > Instead of a "pointer" you can copy whole license files into LICENSE, but
>> > many prefer "pointers" to keep the LICENSE file shorter.
>> >
>> > Of course, I could be wrong...
>> >
>> > -Alex
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)

[Dan Kirkwood]

Thanks,  Alex..

John -- would it be reasonable to fix this in the next release barring
any other major issues?

thanks..  Dan

On Wed, Feb 15, 2017 at 9:34 AM, Alex Harui  wrote:
>
>
> On 2/15/17, 7:40 AM, "Dan Kirkwood"  wrote:
>
>>Thanks,  John..   I'm confused on this.   According to
>>http://www.apache.org/dev/licensing-howto.html#permissive-deps :
>>
>>`In LICENSE, add a pointer to the dependency's license within the
>>distribution and a short note summarizing its licensing:`
>>
>>Is MIT a special case in this regard?  And in that case,  do we need a
>>separate full license entry for each MIT-licensed component we use?
>>Is this RC acceptable other than the license issues you pointed out?
>
> AIUI, a "pointer" is the text from that web page:
>
> This product bundles SuperWidget 1.2.3, which is available under a
> MIT license.  For details, see deps/superwidget/LICENSE.txt.
>
> Your build/packaging should copy the dependency's MIT License into a file
> in the release package.  MIT-licensed projects are supposed to have their
> own copy of the MIT license in their release distributions with a
> project-specific copyright.  The pointer isn't supposed to be a
> third-party URL since URLs are not stable, although I would have probably
> advised you to fix that in the next release.  IMO, it isn't a major flaw
> for an incubating release.
>
> Instead of a "pointer" you can copy whole license files into LICENSE, but
> many prefer "pointers" to keep the LICENSE file shorter.
>
> Of course, I could be wrong...
>
> -Alex
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)

[Dan Kirkwood]

Thanks,  John..   I'm confused on this.   According to
http://www.apache.org/dev/licensing-howto.html#permissive-deps :

`In LICENSE, add a pointer to the dependency's license within the
distribution and a short note summarizing its licensing:`

Is MIT a special case in this regard?  And in that case,  do we need a
separate full license entry for each MIT-licensed component we use?
Is this RC acceptable other than the license issues you pointed out?

Thanks..   Dan

On Tue, Feb 14, 2017 at 7:10 PM, John D. Ament  wrote:
> -1 license file still needs a lot of work.
>
> MIT licenses need to be explicitly included in the license, not just
> linked.  In general, the license contents need to be in the LICENSE file,
> not just links to the licenses.  In some cases, its done like this (full
> license headers copied) and in others there's a path link to the license.
>
> John
>
> On Thu, Feb 2, 2017 at 2:38 PM Dan Kirkwood  wrote:
>
>> Hello Incubator PMC,
>>
>> The Apache Traffic Control community has voted on and approved a
>> proposal to release Apache Traffic Control 1.8.0-incubating.  We now
>> kindly request that the Incubator PMC members review and vote on this
>> incubator release.
>>
>> The VOTE RESULT is here:
>>
>>
>> https://lists.apache.org/thread.html/4aa7f70b34ba9d2e4190301ae7ea118aa86b297c81e60467aedaf3dc@%3Cdev.trafficcontrol.apache.org%3E
>>
>> The draft release notes (along with links to artifacts,
>> signatures/checksums, and updated documentation) can be found here:
>>
>> http://trafficcontrol.incubator.apache.org/downloads/
>>
>> The git tag for the repository is "RELEASE-1.8.0-RC9":
>>
>> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC9
>>
>> The source distribution (also linked in the release notes) is here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC9/
>>
>> Build instructions are included in the BUILD.md file which is
>> included in the source artifact.
>>
>> Artifacts have been signed with the "dang...@apache.org" key listed in:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>>
>> Please review and vote:
>>
>> [  ] +1 Approve the release
>> [  ] -1 Don't approve the release (please provide specific comments)
>>
>> This vote will be open for at least 72 hours.
>>
>> Thanks,
>>
>> - Dan
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)

[Dan Kirkwood]

Minor correction to the previous email -- the artifacts for RC9 are
located here 
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC9/.

Please review this RC and vote..



The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 1.8.0-incubating. We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/4aa7f70b34ba9d2e4190301ae7ea118aa86b297c81e60467aedaf3dc@%3Cdev.trafficcontrol.apache.org%3E

The draft release notes can be found here:
http://trafficcontrol.incubator.apache.org

The git tag for the repository is "RELEASE-1.8.0-RC9":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC9

The source distribution is here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC9/

Build instructions are included in the BUILD.md file which is included
in the source artifact.

Artifacts have been signed with the "dang...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

Please review and vote:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

- Dan

On Thu, Feb 2, 2017 at 12:38 PM, Dan Kirkwood  wrote:
> Hello Incubator PMC,
>
> The Apache Traffic Control community has voted on and approved a
> proposal to release Apache Traffic Control 1.8.0-incubating.  We now
> kindly request that the Incubator PMC members review and vote on this
> incubator release.
>
> The VOTE RESULT is here:
>
> https://lists.apache.org/thread.html/4aa7f70b34ba9d2e4190301ae7ea118aa86b297c81e60467aedaf3dc@%3Cdev.trafficcontrol.apache.org%3E
>
> The draft release notes (along with links to artifacts,
> signatures/checksums, and updated documentation) can be found here:
>
> http://trafficcontrol.incubator.apache.org/downloads/
>
> The git tag for the repository is "RELEASE-1.8.0-RC9":
> https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC9
>
> The source distribution (also linked in the release notes) is here:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC9/
>
> Build instructions are included in the BUILD.md file which is
> included in the source artifact.
>
> Artifacts have been signed with the "dang...@apache.org" key listed in:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>
> Please review and vote:
>
> [  ] +1 Approve the release
> [  ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
>
> - Dan

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)

[Dan Kirkwood]

Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 1.8.0-incubating.  We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/4aa7f70b34ba9d2e4190301ae7ea118aa86b297c81e60467aedaf3dc@%3Cdev.trafficcontrol.apache.org%3E

The draft release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

The git tag for the repository is "RELEASE-1.8.0-RC9":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC9

The source distribution (also linked in the release notes) is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC9/

Build instructions are included in the BUILD.md file which is
included in the source artifact.

Artifacts have been signed with the "dang...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

Please review and vote:

[  ] +1 Approve the release
[  ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

- Dan

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Traffic Control 1.8.0-incubating (RC8)

[Dan Kirkwood]

Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 1.8.0-incubating.  We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/64b9ffad20aca8a4af3bdb0ce33c2d2a26c24c48d96c31494acdca9d@%3Cdev.trafficcontrol.apache.org%3E

The draft release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

The git tag for the repository is "RELEASE-1.8.0-RC8":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC8

The source distribution (also linked in the release notes) is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC8/

Build instructions are included in the BUILD.md file which is
included in the source artifact.

Artifacts have been signed with the "dang...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

Please review and vote:

[  ] +1 Approve the release
[  ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

- Dan

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC5)

[Dan Kirkwood]

Thanks for the feedback,  Justin..We are working on rectifying these 
issues,  but want clarification on a couple.

On 2016-12-29 17:58 (-0700), Justin Mclean  wrote: 
> Hi,
> 
> -1 (binding) As package names don’t include incubating, release includes 
> non Category A licensed software, files incorrectly having Apache headers, 
> unexpected binary file in release and unable to compile from source.
> 
> I checked:
> - package names do not contain “incubating”

is this referring to the tar ball having the name "incubator-trafficcontrol" 
and just changing that to "incubating-..." would suffice?

> - PGP key is not published (but does match KEYS file)

I think my PGP key is published -- here:  
http://pgp.mit.edu/pks/lookup?search=dangogh%40apache.org&op=indexShould it 
be published elsewhere?

> - signatures and hashes correct
> - LICENSE has a large number of issues (see below)
> - NOTICE is OK
> - unexpected binary file in release [22]
> - all source files have ASF headers
> - Unable to compile from source
> 
> With most common permissive licenses you need to include the text of the 
> license in full, while this doesn’t have to be in the LICENSE file it’s a 
> good idea to do so or includes a pointer to the full text in the license. [1]
> 
> Given the number of licenses it would also be a good idea (IMO) to use the 
> the short form i.e. pointers to the license, see also [1].
> 
> This would include licenses for:
> - fontawesome
> - bootstrap
> - SortTable
> - jQuery UI
> - jMenu (a better URL would be https://libraries.io/github/alpixel/jMenu)

Unfortunately,  that page also has links to the missing github repo.   We are 
planning to remove or replace  this for the next release.

> - DataTables
> - Underscore
> 
> License is missing license information for:
> - normalize.css (MIT license) inside [5]
> - Probably several things from the contents of this file? see the copyrights 
> inside [3]
> - angular loading bar (MIT license) in here [4]
> - bootstrap vertical tabs (MIT license) also in [4]
> - cropper (MIT licensed) also in [4]
> - this file [5]
> - bootstrap progress bar also in [4]
> - WTFPL license code here [6]
> - MIT licensed handlebars [7]
> - BSD licensed pretty print [8]
> - this dual license (Apache/GPL) file [14]
> - Several font files [16][17][18][19][20][21]
> - files here [23]
> 
> Given the large number of issues it likely I may of missed something. For 
> instance I would double check all of the JS files bundled as some of them 
> don’t seem to be mentioned in license i.e. modernizr [15]
> 
> Other licensing issues:
> - I don’t believe CC by 2.5 licensed WebAppers Progress Bar would be 
> allowed to be bundled in an Apache releases as the license is listed in 
> Category B and can’t in included in source form. [2]
> - For the MaxMind DB GeoLite2 Database under CC share-alike license you would 
> need to get approve from legal discuss [2]
> - Theses files may be under under the perl artistic license (not 100% sure) 
> [9][10][11][12][13] which is not a Category A license.
> 
> These files [6][8] incorrectly have ASF headers, there may be others.
> 
> The source fails to compile with this error:
> [ERROR] Failed to execute goal on project traffic_router_core: Could not 
> resolve dependencies for project 
> com.comcast.cdn.traffic_control.traffic_router:traffic_router_core:war:1.8.0: 
> Could not find artifact jdnssec:jdnssec-tools:jar:0.12 in cloudera 
> (https://repository.cloudera.com/content/repositories/releases) -> [Help 1]
> 
> Thanks,
> Justin
> 
> 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> 2. https://www.apache.org/legal/resolved#cc-sa
> 3. 
> ./incubator-trafficcontrol/traffic_server/patches/trafficserver-5.3.2-f914e70.diff
> 4. ./incubator-trafficcontrol/traffic_portal/app/src/styles/main.scss
> 5. ./incubator-trafficcontrol/misc/traffic-control-cdn/css/bootstrap.min.css
> 6. ./incubator-trafficcontrol/traffic_ops/app/public/js/lz-string-1.3.3.js
> 7. ./incubator-trafficcontrol/traffic_ops/app/public/js/handlebars.js
> 8. ./incubator-trafficcontrol/traffic_ops/app/public/js/prettyprint.js
> 9. 
> ./incubator-trafficcontrol/traffic_ops/install/lib/perl5/JSON/backportPP/Compat5005.pm
> 10. 
> ./incubator-trafficcontrol/traffic_ops/install/lib/perl5/JSON/backportPP/Compat5006.pm
> 11. 
> ./incubator-trafficcontrol/traffic_ops/install/lib/perl5/JSON/backportPP.pm
> 12. ./incubator-trafficcontrol/traffic_ops/install/lib/perl5/JSON/PP.pm
> 13 ./incubator-trafficcontrol/traffic_ops/install/lib/perl5/JSON.pm
> 14. ./incubator-trafficcontrol/traffic_ops/app/public/js/select2.js
> 15. ./docs/source/_themes/sphinx_rtd_theme/static/js/modernizr.min.js
> 16. 
> ./incubator-trafficcontrol/docs/source/_themes/sphinx_rtd_theme/static/fonts/Inconsolata-Bold.ttf
> 17. 
> /incubator-trafficcontrol/docs/source/_themes/sphinx_rtd_theme/static/fonts/Inconsolata.ttf
> 18. 
> incubator-trafficcontrol/docs/source/_themes/sphinx_rtd_theme/static/fonts/L

[VOTE] Release Apache Traffic Control 1.8.0-incubating (RC5)

[Dan Kirkwood]

Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 1.8.0-incubating.  We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

http://mail-archives.apache.org/mod_mbox/incubator-trafficcontrol-dev/201612.mbox/%3CCAHkg7wQuBwGvVJ7oT3QP=_tymyg+mg4wrzb7g26hn6vydaq...@mail.gmail.com%3E

The draft release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

The git tag for the repository is "RELEASE-1.8.0-RC5":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC5

The source distribution (also linked in the release notes) is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC5/

Build instructions are included in build/README.md file which is
included in the source artifact.

Artifacts have been signed with the "dang...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

Please review and vote:

[  ] +1 Approve the release
[  ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

- Dan

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org