Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Phil Sorber]

+1!

On Mon, Apr 2, 2018 at 8:12 PM Dave Neuman <neu...@apache.org> wrote:

> +1
>
> On Mon, Apr 2, 2018 at 2:11 PM, David Neuman <david.neuma...@gmail.com>
> wrote:
>
> > Dear Traffic Control community members:
> >
> > I would like to call a vote on the resolution for Traffic Control to
> > graduate from to an Apache TLP.  We have already voted on whether or not
> we
> > should start the graduation process [1] and this is the next step.
> Please
> > see the resolution below and vote as follows:
> >
> > [ ] +1 Graduate Traffic Control from the incubator
> > [ ] +0 No Opinion
> > [ ] -1 Do not graduate Traffic Control from the incubator (please provide
> > a reason)
> >
> > The vote is open for a minimum of 72 hours and will need at least 3 more
> > +1 votes than -1 votes from PMC members to succeed.
> >
> > If this VOTE succeeds, a similar VOTE will be started on the
> > gene...@incubator.apache.org mailing list. If that VOTE succeeds, a
> > resolution will be included in the next Apache Board Meeting.
> >
> > Please feel free to reach out with any questions.
> >
> > Thanks,
> > Dave
> >
> > [1] https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa207
> > 23eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
> >
> > -
> >
> > Establish the Apache Traffic Control Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to building, monitoring, configuring, and provisioning a large
> > scale content delivery network (CDN)..
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Traffic Control Project", be and
> > hereby is established pursuant to Bylaws of the Foundation; and be it
> > further
> >
> > RESOLVED, that the Apache Traffic Control Project be and hereby is
> > responsible for the creation and maintenance of software related to
> > building, monitoring, configuring, and provisioning a large scale
> > content delivery network (CDN).; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Traffic Control" be
> > and hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache Traffic
> > Control Project, and to have primary responsibility for management of
> > the projects within the scope of responsibility of the Apache Traffic
> > Control Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache Traffic Control
> > Project:
> >
> >  * Dan Kirkwood   <dang...@apache.org>
> >  * David Neuman   <neu...@apache.org>
> >  * Dewayne Richardson <dewr...@apache.org>
> >  * Eric Covener   <cove...@apache.org>
> >  * Eric Friedrich <fri...@apache.org>
> >  * Hank Beatty<hbea...@apache.org>
> >  * Jan van Doorn  <j...@apache.org>
> >  * Jeff Elsloo<els...@apache.org>
> >  * Jeremy Mitchell<mitchell...@apache.org>
> >  * Leif Hedstrom  <zw...@apache.org>
> >  * Mark Torluemke <mtorlue...@apache.org>
> >  * Phil Sorber<sor...@apache.org>
> >  * Steve Malenfant<smalenf...@apache.org>
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
> > to the office of Vice President, Apache Traffic Control, to serve in
> > accordance with and subject to the direction of the Board of Directors
> > and the Bylaws of the Foundation until death, resignation, retirement,
> > removal or disqualification, or until a successor is appointed; and be
> > it further
> >
> > RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to encourage open
> > development and increased participation in the Apache Traffic Control
> > Project; and be it further
> >
> > RESOLVED, that the Apache Traffic Control Project be and hereby is
> > tasked with the migration and rationalization of the Apache Incubator
> > Traffic Control podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Traffic Control podling encumbered upon the Apache Incubator PMC are
> > hereafter discharged.
> >
> >
> >
>

Re: [VOTE] Traffic Control graduation to TLP

[Phil Sorber]

+1

On Thu, Mar 1, 2018 at 1:12 PM Hank Beatty  wrote:

> +1
>
> On 03/01/2018 10:41 AM, Dave Neuman wrote:
> >   Hey All,
> >
> > After a great discussion amongst the Apache Traffic Control PPMC,
> reviewing
> > the graduation checklist[1], updating the podling status page[2], and
> > updating the project website to ensure the whimsy podling website checks
> > pass[3], I would like to call a vote for Apache Traffic Control
> graduating
> > to a top level project.
> >
> > Apache Traffic Control entered the incubator on July 12, 2016.  Since
> then
> > we have announced 4 releases, nominated 4 new committers, organized 3
> > summits, had almost 8,000 commits from 63 different contributors, and --
> > most importantly -- we have grown and diversified our community.  Apache
> > Traffic Control is a healthy project that is already acting like an
> Apache
> > top level project, so we should take the next step.
> >
> > If we agree that we should graduate to a top level project, the next
> steps
> > will be to pick the initial PMC chair for the TLP and draft a Resolution
> > for the PPMC and IPMC to vote upon.
> >
> > Please take a minute to vote on wheter or not Traffic Control should
> > graduate to a Top Level Project by responding with one of the following:
> >
> > [ ] +1 Apache Traffic Control should graduate.
> > [ ] +0 No opinion
> > [ ] -1 Apache Traffic Control should not graduate (please provide the
> > reason)
> >
> > The VOTE will be opened for at least the next 72 hours.  Per Apache
> > guidelines[4] I will also be notifying the incubator mailing list that a
> > community vote is under way.
> >
> > Thanks,
> > Dave
> >
> >
> > [1]
> >
> https://incubator.apache.org/guides/graduation.html#graduation_check_list
> > [2] http://incubator.apache.org/projects/trafficcontrol.html
> > [3] https://whimsy.apache.org/pods/project/trafficcontrol
> > [4]
> >
> https://incubator.apache.org/guides/graduation.html#community_graduation_vote
> >
>

Fwd: Google Summer of Code 2018 Mentor Registration

[Phil Sorber]

I think we should do this.

-- Forwarded message -
From: Ulrich Stärk 
Date: Sat, Feb 24, 2018 at 2:19 PM
Subject: Google Summer of Code 2018 Mentor Registration
To: 
Cc: d...@community.apache.org 


Dear PMCs,

I'm happy to announce that the ASF has made it onto the list of accepted
organizations for
Google Summer of Code 2018! [1,2]

It is now time for mentors to sign up, so please pass this email on to your
community and
podlings. If you aren’t already subscribed to ment...@community.apache.org
you should do so now else
you might miss important information.

Mentor signup requires two steps: mentor signup in Google's system [3] and
PMC acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an acknowledgement from the PMC for which you want to mentor
projects. Use the below
template and *do not forget to copy ment...@community.apache.org*. We will
use the email adress you
indicate to send the invite to be a mentor for Apache.

PMCs, read carefully please.

We request that each mentor is acknowledged by a PMC member. This is to
ensure the mentor is in good
standing with the community. When you receive a request for
acknowledgement, please ACK it and cc
ment...@community.apache.org

Lastly, it is not yet too late to record your ideas in Jira (see my
previous emails for details).
Students will now begin to explore ideas so if you haven’t already done so,
record your ideas
immediately!

Cheers,

Uli

mentor request email template:

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2018 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code
2018 projects for Apache
.

I would like to receive the mentor invite to 





[1] https://summerofcode.withgoogle.com/organizations/
[2] https://summerofcode.withgoogle.com/organizations/5718432427802624/
[3] https://summerofcode.withgoogle.com/

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

Re: Remove file with invalid license

[Phil Sorber]

Rob,

Just because we remove it for now doesn't mean we have to leave it out
forever. I encourage you to contribute to the thread on the legal mailing
list to make your case or at least get an understanding of their
requirements. The ASF does tend to lean toward conservative interpretations.

Thanks.

On Mon, Dec 18, 2017 at 12:08 PM Robert Butts 
wrote:

> That's correct. No RPM, unfortunately. License is here:
> https://www.owasp.org/index.php/Projects/OWASP_SecLists_Project.
>
> -1 on downloading during rpmbuild, or especially postinstall. Both pose a
> security risk. Moreover, it makes our build or install dependent on the
> internet and a particular website. Neither building nor installing should
> require either internet or a particular website; we should be working to
> get away from that, not towards it.
>
> I'd prefer to find something Apache is ok with vendoring, if we have to.
> Though, ideally we'd keep this one, Daniel Miessler is a well-known name in
> the security community.
>
>
> On Mon, Dec 18, 2017 at 11:51 AM, Dan Kirkwood  wrote:
>
> > Thanks,  Eric..Then it's possible we could download it during
> > rpmbuild or postinstall.
> >
> > On Mon, Dec 18, 2017 at 11:40 AM, Eric Friedrich (efriedri)
> >  wrote:
> > > It can be downloaded from Github.
> > >
> > > I think this is the file (Rob correct me if I picked the wrong
> variant):
> > https://github.com/danielmiessler/SecLists/blob/
> > master/Passwords/10_million_password_list_top_10.txt
> > >
> > > —Eric
> > >
> > > On Dec 18, 2017, at 1:38 PM, Dan Kirkwood  > o...@gmail.com>> wrote:
> > >
> > > Rob,   is there a specific download location for this file?   I see it
> > > referenced as "Projects/OWASP SecLists Project",  but didn't find it
> > > with a quick search.   Is it possible it's provided by an rpm we could
> > > list as a dependency rather than including in our source?
> > >
> > > -dan
> > >
> > > On Mon, Dec 18, 2017 at 11:11 AM, Robert Butts <
> robert.o.bu...@gmail.com
> > > wrote:
> > > I'd really like to keep this, or replace it with a similar file from
> > > another source. Which I'd be willing to investigate, if necessary.
> > >
> > > Having a good blacklist of most-common passwords specifically puts
> > Traffic
> > > Ops in compliance with NIST SP 800-63B.
> > >
> > > I also don't understand the objections, the Apache Legal FAQ
> specifically
> > > says CC-SA is permissible, and doesn't say anything about being limited
> > to
> > > binary (which would be odd, CC is designed for text, not binary).
> > > https://www.apache.org/legal/resolved.html#cc-sa
> > >
> > > I'd vote we wait for the legal resolution, or find a suitable
> > replacement,
> > > in order to remain in NIST compliance.
> > >
> > >
> > > On Mon, Dec 18, 2017 at 10:55 AM, David Neuman <
> david.neuma...@gmail.com
> > >
> > > wrote:
> > >
> > > Hey all,
> > > I don't know if you have been following the release 2.1 thread on the
> > > incubator list [1] , but we have been given a -1 vote by the IPMC for
> > > having a file in our release [2] that has an incompatible license.
> There
> > > is some debate about the license, and we have reached out to Legal for
> > more
> > > information [3] (thanks Eric!), but we haven't heard back from legal
> yet.
> > > Instead of waiting for legal to get back to us, I would like to propose
> > > that we instead remove this file from our release.  The file in
> question
> > is
> > > just a list of weak passwords and I feel like we can easily include a
> > blank
> > > file, or a file with a couple passwords that we generate, and
> individual
> > > installs of Traffic Control can replace this file as they see fit.
> This
> > > will
> > > remove issue of having an incompatible license in our release and
> should
> > > also not require us to do a code change.  The downside of removing this
> > > file is that we will need to create another 2.1 release candidate and
> go
> > > through the vote process again.  I would really like to see us get 2.1
> > > released before the end of the year, and at this point our chances are
> > > looking pretty slim.  So, does anyone object to removing this file from
> > our
> > > release?  If not, I will put an issue into github, remove the file, and
> > > back port the change so that we can get another 2.1 release candidate
> > out.
> > >
> > > Thanks,
> > > Dave
> > >
> > >
> > > [1]
> > > https://lists.apache.org/thread.html/c211f049e3d68af90196c30f6b6d31
> > > a67b3072029dea1efe7d35c9dc@%3Cdev.trafficcontrol.apache.org%3E
> > > [2]
> > > apache-trafficcontrol-2.1.0-incubating/traffic_ops/app/
> > > conf/invalid_passwords.txt
> > > [3] https://issues.apache.org/jira/browse/LEGAL-356
> > >
> > >
> >
>

Re: Changing max_dns_answers default

[Phil Sorber]

You say it causes issues with "large cache groups". What is "large" in this
context? Maybe we should pick a default that puts us slightly below that.
Reading a little into your comment here, I assume the "problems" stems from
the number of answers that fit in a UDP packet. Maybe we should just make
the default below that threshold so we get as close to the max without
causing said problems?

Thanks.

On Mon, Dec 4, 2017 at 12:52 PM Volz, Dylan  wrote:

> Hi All,
>
> The max_dns_answers has been defaulted to 0, which is an unlimited number
> of answers, which causes issues for deployments with large cache groups. I
> opened a PR (1611<
> https://github.com/apache/incubator-trafficcontrol/pull/1611>) to change
> the default from 0 to 5 which is hopefully a sensible value for most
> deployments. If this doesn’t seem like a sensible default please respond
> with alternatives.
>
> Thanks,
> Dylan
>

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC1

[Phil Sorber]

I agree with Dave.

On Thu, Oct 26, 2017 at 1:59 PM Hank Beatty <hbea...@apache.org> wrote:

> Not currently. We either need to use a different script to generate the
> changelog or go back and modify all of the
> PRs/commits to have the 2.1.0 milestone.
>
> Give me until tomorrow because I would like to look at the other one that
> I presented.
>
> Hank
>
> On 10/26/2017 01:42 PM, Eric Friedrich (efriedri) wrote:
> > Do PRs/issues that don’t have a milestone assigned still end up in this
> changelog? I know theres a bunch more that went into 2.1 that isn’t in this
> list.
> >
> > Should we make sure that every PR/Issue is assigned a milestone before
> its merged?
> >
> >> On Oct 26, 2017, at 12:52 PM, Hank Beatty <hbea...@gmail.com> wrote:
> >>
> >> Thanks Phil this is very nice.
> >>
> >> Both of these scripts use the "milestones" to generate the changelog.
> Currently there are 21 issues associated with the 2.1.0 milestone.
> >>
> >> Here is the output of the one in TC:
> >>
> >> Changes with Traffic Control 2.1.0
> >>   #878 - [TC-488] Docs - Multi Site Origin not up to date
> >>   #879 - [TC-490] mso.qstring_handling parameter is checked but not
> documented
> >>   #880 - [TC-489] Multi Site Origin - Invalid default values for
> multiple config params
> >>   #901 - [TC-377] Default profiles for EDGE and MID are missing after
> initial install
> >>   #906 - [TC-327] ConfigFiles.pm detects blank as not null and tries to
> gen files GH #1090
> >>   #909 - [TC-301] creating https delivery service and not setting to
> active still looks for cert. Github Issue #1086
> >>   #912 - [TC-169] TR download the RGB file continuously when the same
> RGB file on server
> >>   #915 - [TC-116] remap.config order is different on master (postgres)
> than it is on 1.8.
> >>   #980 - [TC-552] Global parameters may be duplicated when seeds.sql is
> run
> >>   #988 - [TC-514] ORT: Change Traffic Ops hostname in middle of ORT run
> >>   #1001 - [TC-408] Documentation for creating ssl keys is missing a
> field.
> >>   #1090 - [TC-518] ToCDUCheck and ToCHRCheck: Value formatted as float
> instead of int
> >>   #1115 - [TC-429] - TP - removes map due to license incompatibility
> >>   #1118 - POST /api/1.2/deliveryserviceserver doesn't update header
> rewrite, regex remap and cacheurl
> >>   #1167 - [BACKPORT][TC-518] ToCDUCheck and ToCHRCheck: Value formatted
> as float instead of int #1090
> >>   #1168 - [BACKPORT][TC-514] ORT: Change Traffic Ops hostname in middle
> of ORT run
> >>   #1195 - [Issue-1189] - Backport to 2.1.x - delivery service tenancy
> is forced on creation and update if use_tenancy is on
> >>   #1375 - BACKPORT - fix docs for Deliveryservice/sslkeys/generate and
> deliveryservice/ssl…
> >>   #1386 - Traffic Portal V2 main menu has two rows labeled "Tenants"
> >>
> >>
> >> On 10/26/2017 11:55 AM, Phil Sorber wrote:
> >>> I believe this one has had a little more love recently and does things
> like
> >>> only include merged pull requests, etc.
> >>> https://github.com/apache/trafficserver/blob/master/tools/changelog.pl
> >>> On Thu, Oct 26, 2017 at 9:52 AM Phil Sorber <sor...@apache.org> wrote:
> >>>> You guys mean like this?
> >>>>
> >>>>
> >>>>
> https://github.com/apache/incubator-trafficcontrol/blob/master/misc/changelog.pl
> >>>>
> >>>> On Thu, Oct 26, 2017 at 8:39 AM Hank Beatty <hbea...@apache.org>
> wrote:
> >>>>
> >>>>> I was thinking of starting with something like this:
> >>>>>
> https://github.com/skywinder/github-changelog-generator#output-example.
> >>>>> I will also look at the github-changes that Steve mentions.
> >>>>>
> >>>>> Hank
> >>>>>
> >>>>> On 10/26/2017 08:48 AM, Steve Malenfant wrote:
> >>>>>> Do we have a sample from a script that would create a change log
> based
> >>>>> on
> >>>>>> pull request only? I tried `github-changes` yesterday but it seemed
> to
> >>>>> work
> >>>>>> only with the older releases (<1.8). Although I haven't spent much
> time
> >>>>> on
> >>>>>> it.
> >>>>>>
> >>>>>> We should probably only list the high level changes such as new
> >>>

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC1

[Phil Sorber]

I believe this one has had a little more love recently and does things like
only include merged pull requests, etc.

https://github.com/apache/trafficserver/blob/master/tools/changelog.pl

On Thu, Oct 26, 2017 at 9:52 AM Phil Sorber <sor...@apache.org> wrote:

> You guys mean like this?
>
>
> https://github.com/apache/incubator-trafficcontrol/blob/master/misc/changelog.pl
>
> On Thu, Oct 26, 2017 at 8:39 AM Hank Beatty <hbea...@apache.org> wrote:
>
>> I was thinking of starting with something like this:
>> https://github.com/skywinder/github-changelog-generator#output-example.
>> I will also look at the github-changes that Steve mentions.
>>
>> Hank
>>
>> On 10/26/2017 08:48 AM, Steve Malenfant wrote:
>> > Do we have a sample from a script that would create a change log based
>> on
>> > pull request only? I tried `github-changes` yesterday but it seemed to
>> work
>> > only with the older releases (<1.8). Although I haven't spent much time
>> on
>> > it.
>> >
>> > We should probably only list the high level changes such as new
>> features,
>> > improvements, important fixes and breaking changes (relates to
>> operations
>> > action required).
>> >
>> > Few things we should note as well :
>> > - How to upgrade from pre-2.0 releases
>> > - What are the upgrade procedures (run postinstall for example)
>> > - Profiles locations (not included in 2.x basic install anymore)
>> >
>> > I'm sure some of those are documented already, might just requires
>> > references.
>> >
>> > Steve
>> >
>> >
>> >
>> > On Wed, Oct 25, 2017 at 8:06 AM, Hank Beatty <hbea...@apache.org>
>> wrote:
>> >
>> >> Hello Steve,
>> >>
>> >> The release notes are still being worked on. I am also looking for
>> >> suggestions on how the release notes should be formatted, and how they
>> >> might be auto-generated. If you have any, please let me know.
>> >>
>> >> Regards,
>> >> Hank
>> >>
>> >> On 10/24/2017 07:26 AM, Steve Malenfant wrote:
>> >>
>> >>> Is there any Release Notes associated with this release? 1,337
>> changes and
>> >>> the link above will only display 250 of them.
>> >>>
>> >>> Steve
>> >>>
>> >>> On Mon, Oct 23, 2017 at 4:01 PM, Hank Beatty <hbea...@apache.org>
>> wrote:
>> >>>
>> >>> Hello All,
>> >>>>
>> >>>> I've prepared a release for v2.1.0-RC1
>> >>>>
>> >>>> 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.0.0:
>> >>>> https://github.com/apache/incubator-trafficcontrol/compare/
>> >>>> 2.0.x...RELEASE-2.1.0-RC1
>> >>>>
>> >>>> This corresponds to git:
>> >>>>Hash:6ea2ca86d07c16a3b3ca419dd56b975059271206 <(505)%20927-1206>
>> <(505)%20927-1206>
>> >>>> <(505)%20927-1206>
>> >>>>Tag: RELEASE-2.1.0-RC1
>> >>>>
>> >>>> Which can be verified with the following: git tag -v
>> RELEASE-2.1.0-RC1
>> >>>>
>> >>>> My code signing key is available here:
>> >>>> https://pgp.mit.edu/pks/lookup?op=get=0x582D3F6E79270895
>> >>>>
>> >>>> Make sure you refresh from a key server to get all relevant
>> signatures.
>> >>>>
>> >>>> The source .tar.gz file, pgp signature (.asc signed with my key from
>> >>>> above), md5 and sha512 checksums are provided here:
>> >>>> https://dist.apache.org/repos/dist/dev/incubator/trafficcont
>> >>>> rol/2.1.0/RC1
>> >>>>
>> >>>> Thanks!
>> >>>>
>> >>>>
>> >>>>
>> >>>
>> >
>>
>

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC1

[Phil Sorber]

You guys mean like this?

https://github.com/apache/incubator-trafficcontrol/blob/master/misc/changelog.pl

On Thu, Oct 26, 2017 at 8:39 AM Hank Beatty  wrote:

> I was thinking of starting with something like this:
> https://github.com/skywinder/github-changelog-generator#output-example.
> I will also look at the github-changes that Steve mentions.
>
> Hank
>
> On 10/26/2017 08:48 AM, Steve Malenfant wrote:
> > Do we have a sample from a script that would create a change log based on
> > pull request only? I tried `github-changes` yesterday but it seemed to
> work
> > only with the older releases (<1.8). Although I haven't spent much time
> on
> > it.
> >
> > We should probably only list the high level changes such as new features,
> > improvements, important fixes and breaking changes (relates to operations
> > action required).
> >
> > Few things we should note as well :
> > - How to upgrade from pre-2.0 releases
> > - What are the upgrade procedures (run postinstall for example)
> > - Profiles locations (not included in 2.x basic install anymore)
> >
> > I'm sure some of those are documented already, might just requires
> > references.
> >
> > Steve
> >
> >
> >
> > On Wed, Oct 25, 2017 at 8:06 AM, Hank Beatty  wrote:
> >
> >> Hello Steve,
> >>
> >> The release notes are still being worked on. I am also looking for
> >> suggestions on how the release notes should be formatted, and how they
> >> might be auto-generated. If you have any, please let me know.
> >>
> >> Regards,
> >> Hank
> >>
> >> On 10/24/2017 07:26 AM, Steve Malenfant wrote:
> >>
> >>> Is there any Release Notes associated with this release? 1,337 changes
> and
> >>> the link above will only display 250 of them.
> >>>
> >>> Steve
> >>>
> >>> On Mon, Oct 23, 2017 at 4:01 PM, Hank Beatty 
> wrote:
> >>>
> >>> Hello All,
> 
>  I've prepared a release for v2.1.0-RC1
> 
>  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.0.0:
>  https://github.com/apache/incubator-trafficcontrol/compare/
>  2.0.x...RELEASE-2.1.0-RC1
> 
>  This corresponds to git:
> Hash:6ea2ca86d07c16a3b3ca419dd56b975059271206 <(505)%20927-1206>
> <(505)%20927-1206>
>  <(505)%20927-1206>
> Tag: RELEASE-2.1.0-RC1
> 
>  Which can be verified with the following: git tag -v RELEASE-2.1.0-RC1
> 
>  My code signing key is available here:
>  https://pgp.mit.edu/pks/lookup?op=get=0x582D3F6E79270895
> 
>  Make sure you refresh from a key server to get all relevant
> signatures.
> 
>  The source .tar.gz file, pgp signature (.asc signed with my key from
>  above), md5 and sha512 checksums are provided here:
>  https://dist.apache.org/repos/dist/dev/incubator/trafficcont
>  rol/2.1.0/RC1
> 
>  Thanks!
> 
> 
> 
> >>>
> >
>

Re: [VOTE] Adding a CHANGELOG.md file

[Phil Sorber]

Here is a link to an example script generated CHANGES file from Jira:

https://raw.githubusercontent.com/apache/trafficserver/6.0.x/CHANGES

On Wed, May 17, 2017 at 10:48 AM Phil Sorber <sor...@apache.org> wrote:

> The script can be updated to do Jira. ATS used a Jira version before they
> went to github. You can also separate out easily. In fact, we did it more
> easily with Jira than with github, since those categories are mutually
> exclusive in Jira and labels in github are not. You could also have a
> developer run the script regularly, or have CI do it.
>
> To Eric's comment, if you can make that indication in Jira/GitHub then you
> can transition that to the script. For example, a "Changelog" label in
> github that would mean to have it included.
>
> On Wed, May 17, 2017 at 10:37 AM Eric Friedrich (efriedri) <
> efrie...@cisco.com> wrote:
>
>> What about a compromise where developer chooses whether or not a
>> feature/important fix is worth mentioning in the release notes. This would
>> be at feature granularity not individual commit.
>>
>> Then at release build time, a script gathers from JIRA/Github API all
>> fixes that were committed in that release and checks that into repo.
>>
>> —Eric
>>
>> > On May 17, 2017, at 12:18 PM, Phil Sorber <sor...@apache.org> wrote:
>> >
>> > Don't we have a script that can generate this? ATS had this for a long
>> time
>> > and it became a huge hassle. It caused merge conflicts all the time,
>> that
>> > while easy to address, were a huge nuisance. It also ended up out of
>> date
>> > often.
>> >
>> > On Wed, May 17, 2017 at 10:11 AM Gelinas, Derek <
>> derek_geli...@comcast.com>
>> > wrote:
>> >
>> >> +1 for sure. It'll also give us a way to scan the notes and see what
>> needs
>> >> documenting and what doesn't yet have it.
>> >>
>> >>> On May 17, 2017, at 11:44 AM, Dave Neuman <neu...@apache.org> wrote:
>> >>>
>> >>> Hey All,
>> >>> One thing we discussed at the meetup was the addition of a
>> CHANGELOG.md
>> >>> file to the project.   This file will contain changes that are made to
>> >> the
>> >>> project including bug fixes and new features. (e.g.
>> >>> https://github.com/influxdata/influxdb/blob/master/CHANGELOG.md).
>> >> Adding
>> >>> this file means that we will now require each PR to contain an update
>> to
>> >>> the CHANGELOG.md file, and our documentation will need to be updated
>> >>> accordingly.
>> >>> I thought it would be good to open a vote for adding this file, and
>> if it
>> >>> passes, I will update the documentation and add a CHANGELOG.md file.
>> >>>
>> >>> Thanks,
>> >>> Dave
>> >>
>>
>>

Re: Github "Backport" Label

[Phil Sorber]

You can also search on the branch base. Something like: "is:pr is:open
base:2.0.x"

On Mon, Mar 13, 2017 at 7:55 AM Dave Neuman  wrote:

> I see the label, but I don't see a way to add the label to existing PRs.
>
> On Sun, Mar 12, 2017 at 8:38 PM, Eric Friedrich (efriedri) <
> efrie...@cisco.com> wrote:
>
> > I created a new label in Github called “backport”.
> >
> > Please tag any PRs with this label to make them easier to find.
> >
> > —Eric
> >
> >
>

CC-SA 4.0

[Phil Sorber]

The Traffic Control (Incubating) PPMC was directed here [1] to ask about
Creative Commons Share Alike 4.0 [2] which has not been previously
approved. Basically, is this license compatible with ASL2 and able to be
included in an Apache release?

Thanks.

[1]:
https://lists.apache.org/thread.html/eaf09b5e136a2a8f0cc01e54b08bb7f6de48cd838b75f3df5d350044@%3Cgeneral.incubator.apache.org%3E
[2]:
https://creativecommons.org/share-your-work/licensing-considerations/version4/

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC2

[Phil Sorber]

http://www.apache.org/dev/release-signing.html#basic-facts

Missing checksums for the artifacts.

And for the record, I am still not liking the RPM's as release artifacts,
but I'll let the IPMC weigh in on that.

On Thu, Dec 1, 2016 at 12:36 PM Leif Hedstrom  wrote:

>
> > On Nov 30, 2016, at 10:56 AM, Dan Kirkwood  wrote:
> >
> > Hello All,
> >
> > I've prepared a release for v1.8.0 (RC2)
> >
> > Changes since 1.7.0:
> >
> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC2
> >
> > This corresponds to git:
> > Hash: 8766dbcb38105fbc97b955b4733defe40c83db00
> > Tag: RELEASE-1.8.0-RC2
> >
> > Which can be verified with the following:
>
>
> Minor (nit-pick) detail: Why does the tar-ball unpack into a directory
> named “workspace”? I would have expected it to be
> incubator-trafficcontrol-1.8.0.4567.8766dbcb .
>
> Also, why the UUID in the release name? Is that something the incubator
> wants now?
>
> Cheers,
>
> — leif
>
>