JMP 14 for "early adopters"I know we normally wait for the .1 update to move to a new version of JMP, but is there any chance of a mechanism for early adopters to move to 14 before the official distribution?
With the new python connector, a optimal designs, and the new Project mode, there's more applicable stuff for zymers than in previous versions, so it would be nice to get it out early to frequent users.
~MichaelRe: JMP 14 for "early adopters"
We do significant testing and have instituted new methods over the last couple of years to try to track down the seemingly irreproducible crashes, but we do need your help if JMP crashes on you. You should be getting a prompt to send the crash report to our tech support department. If you don't do that we have no way of knowing that you're experiencing problems. We can't fix what we don't know about.
Please do us (and Novozymes) a favor by reporting these when they happen. Even if you can't reproduce it, or can't describe exactly what you were doing when it crashed, the crash report may have details that will help us understand where the problem is.
Thanks for your support.
Re: JMP 14 for "early adopters"I also would like a mechanism to move to JMP 14 before the official distribution. There are a lot of new features that would improve our team's workflow and allow us to gain better insight into our data.
Re: JMP 14 for "early adopters"Hi Jeff,
No, I have not reported the bugs. It crashes every time I open from Sharepoint, so I open from Windows Explorer instead. It also crashes a lot in general, and I cannot tell you when and why because it seems so random. All I can say, is that your developers could do a much better job debugging and testing, before you release a new version.
Sincerely,
Jesper
Re: JMP 14 for "early adopters"Hi Jesper (@jfri0),
I’m sorry that you’ve found JMP 13 to be problematic. Have you reported the bugs and crashes that you’ve experience to Tech Support (support@jmp.com)?
Re: JMP 14 for "early adopters"
Is it as buggy and unstable as 13, or has it improved? Have you tried opening JMP files from OneDrive, SharePoint and ELN?
I don't recall ever doing so. It's also possible I did but nothing went wrong so I don't remember it 
To be fair, usually my JMP crashes are because I do irresponsible things in JSL like opening 265 separate graph builder windows accidentally.
I expect JMP 14 still has bugs (the last Early Access version definitely still did), which is why we normally wait for the .1 release (14.1 in this case) before deploying throughout the company. I would personally rather have 14 with the new features, and just report bugs to JMP if I run into them so they can be fixed for 14.1. I expect most users would rather wait, unless they urgently want something like the Python connector (or want to test it so other users might have fewer bugs)
Re: JMP 14 for "early adopters"Is it as buggy and unstable as 13, or has it improved? Have you tried opening JMP files from OneDrive, SharePoint and ELN?
Thanks,
Jesper
