Skip to content

Remove MXM MTL #2849

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jsquyres opened this issue Jan 26, 2017 · 5 comments
Closed

Remove MXM MTL #2849

jsquyres opened this issue Jan 26, 2017 · 5 comments
Assignees
Milestone

Comments

@jsquyres
Copy link
Member

Per F2F Jan 2017 discussion, remove the MXM MTL for v3.0.0.

@jladd-mlnx was going to investigate if this was ok. I'm filing a ticket here to make sure we don't forget.

@jsquyres jsquyres added this to the v3.0.0 milestone Jan 26, 2017
@bwbarrett
Copy link
Member

Brian, Howard,

We can safely deprecate MXM/MTL.

Josh

-----Original Message-----
From: Barrett, Brian [mailto:[email protected]]
Sent: Tuesday, March 07, 2017 2:52 PM
To: Joshua Ladd [email protected]
Cc: Pritchard Jr., Howard [email protected]
Subject: Re: MXM MTL / Yalla PML

Thanks! We won’t take any action until we hear from you.

Brian

On Mar 7, 2017, at 11:51 AM, Joshua Ladd [email protected] wrote:

Hi, Brian

We can probably deprecate the MTL, but we will certainly want to continue supporting Yalla. Let me double check with Yossi and make sure he doesn't have any concerns about the MTL.

Josh

-----Original Message-----
From: Barrett, Brian [mailto:[email protected]]
Sent: Tuesday, March 07, 2017 2:47 PM
To: Joshua Ladd [email protected]
Cc: Pritchard Jr., Howard [email protected]
Subject: MXM MTL / Yalla PML

Josh -

For the 3.0 series, does Mellanox want to continue shipping / shipping the MXM MTL and/or the Yalla PML? There’s an open issue about deprecation, so wanted to make sure we weren’t shipping something unnecessarily.

Thanks,

Brian

@jladd-mlnx
Copy link
Member

👍

@hppritcha hppritcha modified the milestones: v3.1.0, v3.0.0 Mar 14, 2017
@jsquyres
Copy link
Member Author

Looks like we unfortunately forgot to remove this in 3.0.0 (or 3.1.0) -- @bwbarrett will file a PR shortly to remove this from master (and thereby trigger the next release series to be v4.0.x).

@jsquyres jsquyres modified the milestones: v3.1.0, vNEXT Nov 27, 2017
@gpaulsen
Copy link
Member

Howard said he'll do this.

@hppritcha
Copy link
Member

this was actually closed via #5180

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants