‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMPIn anticipation of the release of JMP 19 and the chance for so many JMP staff to interact with customers at the four upcoming Discovery Summits, here’s a quick reminder of how to answer any questions users might pose regarding accessing and using older versions of JMP.
“With the advent of My JMP in JMP 18, installing JMP became a quick, just-a-couple-of-clicks process. But ease of use wasn’t the only goal of My JMP. It’s also ensured that the latest version of JMP – and only the latest version – was provided,” said Jeff Perkinson, Director of User Enablement.
However, there are still some customers who are using earlier versions of JMP – and would like to continue doing so. What do you tell users who ask how to get more JMP 17 when My JMP will only provide the newest version?
First, let’s take a look at what the current license agreement says:
"JMP will provide Customer access to the most recent commercially available release of the Software. However, if requested by Customer, JMP may, in its sole discretion, provide access to an earlier version of the Software. However, JMP will not provide an installation program for any version of the Software other than the most recent commercially available release."
Accordingly, when JMP 19 is released, it will replace JMP 18. Anyone coming to My JMP to download the software will find JMP 19 installers. We will no longer distribute JMP 18 via My JMP.
Note, however, that an authorization to use JMP software will work for any release newer than JMP 18, so there is no need for administrators to re-authorize users. Any authorized user will be able to use JMP 19.
For those who already have access to JMP 17 and earlier, we will continue to provide license files but not installers. Please see the policy for providing older releases for more information.
Be sure to remind users wanting access to older versions of a few key points:
- Older releases have security vulnerabilities. JMP only patches the current version and does not provide security updates for older releases.
- Older releases still have bugs that we have since fixed.
- Older releases are unsupported or have limited support (e.g., see “no bug fixes” above!).
Answers to questions users might pose regarding accessing and using older versions of JMP.
Company UpdateFeature StoryJMP NewsSalesUser EnablementRe: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMPThank you @AmyStuart ! A couple of clarification questions: (1) For renewal customers (not new or transition), which aren't directly addressed in the linked policy, do we still follow the outlined exception approval path if the customers want ONLY the new version and not JMP 17 license files at renewal? (2) For store customers, if they need to reinstall do they immediately receive only installers for the most recent version (ie for JMP 19 not JMP 18 once it's out)?
Re: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMPWill users still be able to have multiple version of JMP installed at the same time? If moving to JMP 19 breaks a script will they still be able to use JMP 18 or will that have to be removed during the JMP 19 install?
Re: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMP @amy with MyJMP being relatively new, and this process being the first of it's kind in MyJMP regarding a major version update from JMP, is a communication plan in place for Admin's - I'm thinking an email to admins, or a FAQ for a technical understanding for them to know how it works? I'd love to see something similar to this posting be presented externally (and quickly) via JMP Blog - possible?
Re: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMP@Juliette_Plager
For your second question, yes, the JMP Store will make available the most recent version of the installer. When JMP 19 is generally available in September the JMP Store will make available the most current version of the installer, i.e., JMP 19 for download.
And for your first question I would reach out to your manager for specific policy guidance.
Re: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMP@Peter_Hersh yes users can still have multiple versions of JMP installed. And yes they can still use JMP 18. No, the installation of JMP 19 will not uninstall an earlier version of JMP.
Re: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMP@Juliette_Plager
For your second question, yes, the JMP Store will make available the most recent version of the installer. When JMP 19 is generally available in September the JMP Store will make available the most current version of the installer, i.e., JMP 19 for download.
And for your first question I would reach out to your manager for specific policy guidance.
Re: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMP@Juliette_Plager
For your second question, yes, the JMP Store will make available the most recent version of the installer. When JMP 19 is generally available in September the JMP Store will make available the most current version of the installer, i.e., JMP 19 for download.
And for your first question I would reach out to your manager for specific policy guidance.
Re: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMP@dara_hammond Landra is preparing a series of communications to administrators and will take this into consideration but I think we want to be careful that we don’t introduce a solution for something that is not yet an issue. If we get support cases or questions in the community from JMP administrators we can prepare an FAQ in combination with a blog post as you suggested.
I hope this helps.
Re: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMPI'm glad to see us strongly encouraging use of new versions of JMP through license language, support stance, MyJMP and sales policies. JMP Development spends a lot of time and effort not only adding new features, but fixing many bugs and crashes during each release cycle, as well as updating third party libraries so that customers can have faster access to the most secure JMP software possible. After delivering bi-monthly "dot-dot" releases in the JMP 18 cycle with the latest third party library updates, development will be delivering monthly security releases for all products during the 19 cycle during months where we don't have a regular maintenance release. That is, JMP 19.0.1 will come out a month after JMP 19 ships, and we will deliver 19.0.5 the month before we ship 19.1. We will also ship security updates in regular maintenance releases as we've been doing.
Anecdotally, I have noticed that with MyJMP always providing "the latest", more customers seem willing to update to the current version when TS assesses their bug/crash and confirms that it matches up to a know issue for which we have already shipped a fix. I've seen this trend especially with crashes that match up to problems that we know to be resolved in the current shipping version. Customers seem very willing to install "the latest" and often come back to say "My issue was resolved, thank you!" I rarely see "I can't update JMP to get this fix." I think that's great progress. In any case, everyone who uses software is getting used to very frequent software updates and becoming more familiar with security best practices for software. It's much better for us as a company to be aligned with those best practices.
Re: ‘But we need more JMP 17!’ How to respond to customers who want earlier versions of JMP@stan_koprowski and @LandraRobertson - super glad to hear a communication is slated for Admins. Do you have an ETA on that delivery - with the update release in a couple weeks are we targeting prior to that. I hear you with with FAQ, and that makes sense, I may have used the wrong descriptor there. When I was reading the SF update the other day from Candice I thought "something like this is what I mean" . I'll send a copy of that your way to consider. As you prepare, can considerations please be given to ELAs that may have domain authorization - I don't *think" the Premier team own all of those, but I do believe there may be different implications for those customers. Thanks!
