New Version of JASP

Comments

• EJ

  July 14

  We hope for this week or next week
• asjones

  July 15

  I know you all have been working hard on the next big version of JASP. Between features, and getting both old and new bugs. I also know you all are behind when you hoped to release.

  Not pushing and not complaining, but out of curiosity what has been the biggest pain points in getting this version out?

  This is more a question about learning more about the JASP development process.

  Don't want you all to rush a new version before it is ready then have to issue a fix shortly after.

  
  

  Just curious.

  Alan
• EJ

  July 16

  There are a number of new modules that needed thorough testing and bug fixing. But there are architectural changes as well (to improve the data editing for instance, and to enhance security by sandboxing). If we only released for Linux then life would be much easier for the programmers, I believe. With software projects like this one, you only see the tip of the iceberg. But our release cycle is relatively effortful, and we have also made substantial changes to make it more modular. This was quite an investment of time and effort, but it should pay dividents going into the future!

  EJ
• asjones

  July 16

  Thanks EJ. The back end work is often never seen, but can be the most important part for both short and long term success.

  I am sure the back end work is really harder than adding new modules and other changes.

  We truly appreciate the work. Don't rush get it right rather than fast.

  thanks

  Alan