Welcome to the JMP Development Update for November 18, 2022!
Product and development managers have changed the Code Approval and Code Freeze dates for JMP 17.1 to permit more time for JMP 17.0 CRP bug reports to surface. You can see the new schedule for 17.1 on the JMP 17 Dates page in Confluence. Code Approval mode will begin at the end of the day on Friday, January 6, and Code Freeze will happen at the end of the day on Friday, January 27.
Thank you for continuing to integrate important fixed into the 17.1 track! Please be aware that although we are shifting out the start of approval and code freeze, 17.1 Doc and L10N freeze dates will not change. Book updates and their associated translation projects are already in underway and changing those schedules could negatively impact our ability to deliver translated doc in 17.2 installers. Therefore, please pay special attention to the potential for any doc and L10N changes that might be needed for code changes you are considering and work with those teams to minimize downstream impact. Since we have already handed off 17.1 strings, any string additions or edits will cause a string to be in English for 17.1 and this may negatively impact doc/screenshots and cause confusion for translators and reviewers.
Thanks very much to Sarah Sylvestre for sharing that JMP Product Management has made changes to the JMP Wish List process that will have some impact on development and others. Starting next week, PM team members will be cloning Feature Requests from their Product Management Jira project into the relevant development Jira project (JMP, JMP Clinical, WebJMP, etc). Cloning a Jira issue just means that PM will copy the contents of the Feature Request from the PM Project to a Story in the development project. These cloned issues will automatically show up in the appropriate development project, so there is no need for you to try to move Feature Requests from the Product Management project into a development (or other) project.
The team has decided to clone Wish List Feature Requests instead of Moving them to development projects because this will make it easier for them to track progress in their own backlog and to close the loop with our customers. Please reach out to Product Management (Sarah Sylvestre or Mia Stephens) if you have any questions or concerns. The PM team has volunteered to discuss this and other changes related to triaging feature requests in a future dev meeting.
Finally, thanks to Audrey Shull for sharing this week’s Jira Tip of the Week!
This week, we made one change which had a bigger impact to R&D groups than we expected. Sorry about that – if we had realized that, we would have given you more warning! We updated the names of the status field values that we inherited from SAS R&D Jira to be more readable:
- Test-Ready(Q) was renamed to Test-Ready
- Testing(W) was renamed to Testing
- Dev-ready(Q) was renamed to Dev-Ready
- Developing(W) was renamed to Developing
- Accepted and Close(Q) was renamed to Accepted and Closed
This had the unfortunate impact of breaking saved filters that used these status values, causing you to see a message like this when you tried to use one:
The simple fix is to adjust the names of the states in your filter to use the new names above, and press Save next to the filter name.
The Admin team has plans for a few more changes that will optimize our Jira experience in the future:
- Removing unused fields (but you won’t even notice - they’re unused!)
- Cleaning up and simplifying the possible options for the Resolution field (we’ll work with individual groups and make sure we’re not removing your favorite resolution)
- Add a Planned Version field. Once we add that, you can consider using this field rather than the :OPEN tag to indicate the version where you are aiming to resolve an issue. (We’ll adopt this as our standard and deprecate the use of :OPEN when we start the 17.2 cycle.)
- Cleaning up Labels
General Announcements
- Please be sure to read the email today from Bob Hickey with guidance on how to use OneDrive technology to have installers synced to your PC/Mac to avoid download speed issues from Cary HQ. Please note: these installers are for employee use only.
Important Upcoming Dates
- JMP 17.1 Doc Freeze – 12/21/22
- JMP 17.1 Code Approval Starts – 1/6/23
- JMP 17.1 L10N Freeze – 1/16/23
- JMP 17.1 Code Freeze – 1/27/23
- JMP 18 EA1 Freeze – 2/3/23
- JMP 18 EA2 Freeze – 4/7/23
- Please visit Confluence for a full list of JMP 17 and JMP 18 dates.
JMP Development Updates
DOE
- Brad: I have an accepted paper this week with Technometrics. Co-authors Jon Stallrich NCSU and Katherine Allen Moyers Eli Lilly. I submitted a revision of a paper on 2- and 3- mixed level screening designs to JQT. Co-authors Ryan Lekivetz and Chris Nachtsheim
- Peng: Prepared and delivered a Developer Tutorial: State-of-the Art Use of Repeated Measures Degradation to Model Product or Part Failures. Planned and organized by Gail, and got help from Caleb, Jerry, and Don. It was a successful event. Other than that, are regular maintenance work for improvement and fixes JMP-14652, JMP-14749.
- Caleb: Finished up my 17.1 sample size explorer fixes as Yeng will be out for the rest of the year to finish up her dissertation work. I’ve also made good progress on fixing some bugs related to MSA design and helped Peng present a developer tutorial on his new Repeated Measures Degradation platform. He did a great job!
- Ryan L: Published an article in Quality Engineering “Testing the prediction profiler with disallowed combinations—A statistical engineering case study”, with Jeremy Ash, Caleb King, Laura Lancaster, Ryan Lekivetz, Joseph Morgan, Yeng Saanchi. ß Congratulations, team!
Host
- Daniel Powell: Finishing up testing for the fully AWS Activation Server as well as adding some QOL improvements for our JMP Pro Trial testing!
HTML5
- Praveena: Completed work on GB: Line: Stacked with fill below using missing, hidden, excluded data gives different chart, GB Line : Data with Hidden/Missing/Excluded Incorrect tooltip, GB Line - Stacked : Incorrect tooltips, and Plot Col Box in Col Span Box is not applied in Interactive HTML with data (This was a customer reported issue. John Powell helped with the analysis). Working on GB: Line: Chart w/no X and row order should default to use Row instead of Mean.
- John Powell: Completed another Level 2 security training module. Integrated a fix for a crashing unit test into 17.1. Held sprint and dev. cycle end meetings. Helped new HTML5 developer Mike Stickles choose initial hardware for his start date of Dec. 1st. Attended the JMP 17 Release Reception.
- Mayowa: Completed product security training, wrote a trip report for connect.tech conference, participated in html scrum planning and sprint planning meetings.
- Paul Spychala: This week was spent wrapping up sprint planning for our next sprint, adding html support for title span/alignment [JMPHTML-702, JMPHTML-713, JMPHTML-1768, JMPHTML-1368], and more security training.
JMP Live
- Aurora: For 17.1, helped Justin Chilton brainstorm on a hung table processing event. For 18.0, removed some obsolete code. Miscellaneous: Required security training (finished). Fixed some broken Jira filters and Confluence macro references. Working on Perforce --> Git change for JMP Live.
Statistics
- Laura C-S: Fixed a few bugs, including a crash, in SEM. Continue with remaining integration of fixes to 17.1. Doing research on the Bollen-Stein algorithm for bootstrapping the chi-square statistic and other fit indices in SEM.
- John Sall: Fit Group now supports the Design Space Profiler (JMP-14411). Oneway now includes the (Cohen's D) effect size. (JMP-14692).
Stat Testing
- Jacob: Testing MSA Design, writing unit test to compare expected mean squares calculations to SAS. Testing designs using response surface models and random blocks, investigating a bug reported by Tom Donnelly. Writing follow-up usability study for Factor UI prototype. Continuing Product Security Training.
- Mark: Attending Product Security Level 2 training. Working with Brad and Joseph on Easy DOE for JMP 18. Preparing to record a presentation with Jianfeng for JMP Discovery Summit Europe. Answered questions in JMP Community.
- Tonya: Working on EA presentation. Testing auto recalc in distribution. Bug verification.
Product Management
- Sarah: Working on creating a better workflow for the Wish List in our new Jira instance. Testing out ways we can effectively represent prioritization of issues done in JMP with a weighted formula in Jira, with a combination of custom fields and plug-ins (primarily doing this work for the Data Discovery team). Testing out how we can incorporate the Feature Readiness Checklist in Jira, potentially using plug-ins. I wrote a blog post about my experience as a new user to JMP, so feel free to check it out if you are interested in hearing some candid new user feedback. The blog incorporates my own experience and what I heard from new and experienced users at Discovery.
- Bryan F: Researched different platforms for user testing, provided information to First 5 team, and working on getting a trial to UserTesting.com. Solicited and evaluated icon creation from a couple of providers on Fiverr. Created first Amazon AppStream image instance for usability testing. Coordinating the second JMP Projects usability test.
- Mia: Results from the JMP EA survey to understand the use of Columns Viewer and how JMP is being used to perform basic tasks are in this JMP Live Report. (Note that only a very superficial descriptive analysis was conducted, but you’re more than welcome to explore the data on your own.)
Technical Support
- Duane: More JMP 17 cases are being opened. Here are the TS JMP Live reports and the usual plot below.
Development Operations
- Myron: JiraBot – finished testing and now I’m running through selective tickets from the production backlog. I will send a mass email Monday when I let it run through the general ticket population. Working on new Help build projects (JMPTOOL-582, JMPTOOL-597). After a weekend backup, I will be deleting years of old test results to free up table space (JMPTEST-569). Starting to replace jmptool’s OpenAM client as requested/mandated by SAS I.T.
- Melanie: Finished fixing bugs for tutorials for 17.1. Worked with Myron to extract strings for sample data for 17.1. Worked with localization team to get sample data kits made and ready to send out.
Documentation
- Qiana: Worked with WebWorks support to create control files for JMP Help. Worked with HR on summer intern offer. Reached out to the Data Ethics Practice regarding requests I received from JMP employees to make updates to sample data table language; will be working with SAS Chief Diversity Officer to address these issues. Communicated with Landra about editing support.
- Susan C: Working on updates from Ross to student subscription doc. Working on JMP Live Jiras for 17.1. Also made an update to the install help per an email request from Brian C and Dieter. Did UI string review, no updates needed.
- Chris B: Working on JMPDOC-1567 and JMP-7698 (thanks Melanie Drake!). Looking at how we can deliver help and (maybe) PDFs in the future.
System/Host Testing-Cary
- Nick H:
- Working with Mandy to track down mystery unit test failures that only happen in the nightly runs - we have been unsuccessful in resolving these so far but still making daily attempts to gain more information. Looked into failures due to a regression related to recent changes Dan S has made (now fixed). Dan retired a preference for JMP 12 JSL compatibility warnings (JMP-14734) which has required an adjustment to many tests across several files. Also have been adding unit tests for verifications of a few bugs and small features.
- Worked with Audrey to track down an issue where known issues are not being marked as known in the Testing Dashboard because the table we use to mark these issues is still pulling from the old Jira sever – we hope to fix this soon. There is also an issue in the Testing Dashboard where test failure history is not showing up due to the SQL query timing out. I am hoping that once Myron completes cleanup of one of one of the dependent tables performance will improve. Lastly, I am implementing a new feature for the line graphs that track failure count over time in the dashboard to have their date lookback on the x-axis be adjustable via a slider – a request from Jim here: JMPTEST-556.
- Mandy: Spent a bunch of time chasing down an odd Main Menu issue that came up around 11/08 and only happens on Windows and on the nightly runs (appearing to be a headless type machine issue). I feel that code was pushed to 18 that is causing this but we can’t quite figure out what or who yet! Completed level 2 security training. Working on verifying a few fixes and adding tests, and working on Workflow Builder Demo for Dec. 1st P&G day.
- Audrey: Working with Atlassian to finish fixing some Confluence links which still point to old Confluence, brainstorming with Nala/Josh on a stress environment for JMP Live, Jira tweaks.
- Lisa: Worked on updating the status and workflow transition names in Jira and entering tickets for some annotation improvement ideas.
System/Host Testing-Beijing
- Eric Wang: (1) Completed WEBJMP-2026. Tested audit log for all actions. (2) Moved JMP Live tests from Cary nightly run to Beijing Jenkins environment. (3) Investigating JMP Live stress testing.
- Da Li: (1) Verified bugs JMP-14158 and JMPTEST-555. (2) Verifying JMP-14661 and WEBJMP-6205. (3) Knowledge sharing KnowledgeSharing-Da-20221114 Postman introduction.
- Mike Wu: (1) JMP 17.1, 18.0 bugs regression testing on the JMP 18.0 roaming migration issue and some sample datatable/scripts changes. (2) Activating JMP 18.0 ProTrial against Dev activation server met issues on both Windows and Mac and discussion with Daniel, now the JMP 18.0 ProTrial activation is working good on both Windows and Mac by 11/15. (3) JMP 18.0 Telemetry testing continued, details can be found from: JMPTESTBJ-1770. Also updated the JMP 18.0 telemetry test plan according to the new change due to bug JMP-14650.
- Kimi: (1) Assist with Jim updating python version to 3.11.0 on Cary UT env and update the JSL to the new version, details refer to JMPTOOL-390. (2) Debug the UT Failures of Formula Depot, created a new bug JMP-14683. (3) http://public.jmp.com is updated to 17.0, so verified related jira WEBJMP-4739 and WEBJMP-2640. (4) Jenkins: Upgrade the python/anaconda version for both win and mac in Beijing Env. Update Visual Studio Professional 2022 for AWS testing image. Debug the failures of JMP Live E2E Tests with Eric.
- Da Zhang: (1) Researching on load testing for JMP Live using JMeter. (2) Looking at Baseline UT failures in JMP 17.1 for non-English (Japanese).
- Nala: (1) Jira tickets verification. (2) I18N testing for JMP Live 17.1. (3) Deployed a JMP Live 17.0 server for Beijing team. (4) Completed check-in conversation within Beijing team. (5) Investigated Load Testing and preparing a brief introduction for Load Testing.
Data Discovery
- Evan: Working on adding a JSL RowStatesMask restriction to <
- Dave B: Added a max version to the addin builder, fixed a copy/paste bug with crosstabbox, fixed a save journal crash, made $addinhome available in an addin unload script, pushed new dialog resource files for the page setup dialog.
- Ernest: Undo/Redo in Workflow Builder. Showing/editing attributes in Columns Viewer. Threading stats in Columns Viewer.
- Dan S: Integrated data filter crash fix to 17.1, JMP 18 work on New Window(), Data Filter, and speedup of PCA with many columns.
Note from Shannon
