Dear developers (esp. Arsenij and Stefan), Right now I'm not sure how to deal with the issue Stefan discovered, i.e. whether to include the fix [1] in 13.3.22 or just push it to the master for the next release.
I just want to get the right picture. What are the circumstances under which the issue discovered by Stefan leads to failures and what are the consequences from the user's perspective? The AssertionError only occurs in a development environment, and one way to put Saros into the according state in production is to reset the color settings to 'default' through the preferences. And what does the normal user get to know of this? Does this impair the color management? Stefan wrote something about flipping colors? Best Regards, Franz [1] http://saros-build.imp.fu-berlin.de/gerrit/672 ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
