Re: Traffic Ops UI Deprecation in favor of Traffic Portal

[Jason Tucker]

Jeremy - I realized I never submitted the follow-up issue for the bulk
delete of parameters, so I just opened it now:
https://github.com/apache/incubator-trafficcontrol/issues/1969

Right now, this is something that can only be done through the legacy UI
(or, via the DB directly). I think we should have it before the legacy UI
goes away.

__Jason

On Tue, Mar 6, 2018 at 10:38 PM, Rawlin Peters 
wrote:

> Thanks, Jeremy. I'd like to add that all new features don't
> necessarily need to be added to the old Traffic Ops UI. That precedent
> has already been set with features like Delivery Service Cloning and
> URI Signing which are only available in Traffic Portal as of today,
> and I think that's perfectly acceptable given the plan to deprecate
> the old Traffic Ops UI in the near future.
>
> I'm not sure if we need to formalize this with a vote or not because
> the precedent is already set, but I'd say we should continue to fix
> things like bugs and security issues but not add new
> features/enhancements to the old Traffic Ops UI. This should reduce
> the burden of shipping new features in Traffic Control while we're in
> this stage of having two different UIs.
>
> - Rawlin
>
> On Tue, Mar 6, 2018 at 3:12 PM, Jeremy Mitchell 
> wrote:
> > At last year's TC summit, we discussed the deprecation of the TO UI in
> > favor of the Traffic Portal.
> >
> > Now that TP has almost achieved feature parity with the TO UI, that day
> is
> > coming soon.
> > Here are 2 issues I know that need to be complete to achieve feature
> parity:
> >
> > https://github.com/apache/incubator-trafficcontrol/issues/1616
> > https://github.com/apache/incubator-trafficcontrol/issues/1287
> >
> > Deprecation may mean simply deleting traffic_ops/app/public/ for 2.3 (or
> > 3.x). Or maybe it means something else. Not sure yet.
> >
> > But the point is, if you want to ensure that all new UI features that you
> > build live past 2.3 (or 3.x), please be sure to put those features in TP.
> > Reach out to me if you need help with TP.
> >
> > Jeremy
>

Traffic Ops UI Deprecation in favor of Traffic Portal

[Jeremy Mitchell]

At last year's TC summit, we discussed the deprecation of the TO UI in
favor of the Traffic Portal.

Now that TP has almost achieved feature parity with the TO UI, that day is
coming soon.
Here are 2 issues I know that need to be complete to achieve feature parity:

https://github.com/apache/incubator-trafficcontrol/issues/1616
https://github.com/apache/incubator-trafficcontrol/issues/1287

Deprecation may mean simply deleting traffic_ops/app/public/ for 2.3 (or
3.x). Or maybe it means something else. Not sure yet.

But the point is, if you want to ensure that all new UI features that you
build live past 2.3 (or 3.x), please be sure to put those features in TP.
Reach out to me if you need help with TP.

Jeremy

[RESULT][VOTE] Traffic Control Graduation to TLP

[Dave Neuman]

The vote for Apache Traffic Control to graduate to a top level project [1]
has overwhelmingly passed with 16 +1 votes and 0 -1 votes!
Thank you to everyone who voted, I am excited to start on the resolution
and move forward toward graduation!

--Dave

[1]
https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa20723eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E






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

Re: [VOTE] Traffic Control graduation to TLP

[Gelinas, Derek]

+1000!

On 3/6/18, 11:51 AM, "David Neuman"  wrote:

Hi All,
I am calling this vote as PASSED!
I will send out a results email shortly, and notify the IPMC.
Please keep an eye out for the next communication which should be a vote on
our resolution.

Thanks,
Dave

On Fri, Mar 2, 2018 at 2:43 PM, Leif Hedstrom  wrote:

> +1
>
> — Leif
>
> > On Mar 1, 2018, at 08:41, 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
>
>

Re: [VOTE] Traffic Control graduation to TLP

[David Neuman]

Hi All,
I am calling this vote as PASSED!
I will send out a results email shortly, and notify the IPMC.
Please keep an eye out for the next communication which should be a vote on
our resolution.

Thanks,
Dave

On Fri, Mar 2, 2018 at 2:43 PM, Leif Hedstrom  wrote:

> +1
>
> — Leif
>
> > On Mar 1, 2018, at 08:41, 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
>
>

Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2

[Dave Neuman]

The 2.1 profiles should work for 2.2

On Tue, Mar 6, 2018 at 9:19 AM, Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:

> Can you please post default profiles for 2.2 on the website?
>
> For now, I’m using 2.1 default profiles to test the release
>
> —Eric
>
> > On Mar 5, 2018, at 1:25 PM, Robert Butts  wrote:
> >
> > Hello All,
> >
> > I've prepared a release for v2.2.0-RC2
> >
> > 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.1.0:
> > https://github.com/apache/incubator-trafficcontrol/
> compare/RELEASE-2.1.0...RELEASE-2.2.0-RC2
> >
> > This corresponds to git:
> > Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d
> > Tag: RELEASE-2.2.0-RC2
> >
> > Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2
> >
> > My code signing key is available here:
> > http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F=vindex
> >
> > 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 sha1 checksums are provided here:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/
> trafficcontrol/2.2.0/RC2
> >
> >
> > Thanks!
>
>