Same here, i follow SVN pretty closely on our production servers for
potentially 1 million+ accounts. Luckily for now only a few thousand
are actually using it (the rest is using squirrelmail), and they know
it's alpha/experimental. Im still porting some of our internal
functionality to RC. Ive already implemented the previous cache
busting ideas cause I was going crazy answering questions about weird
UI issues. All related to cached JS or CSS. But id much rather see
this in core RC.
I want to say again though, its very cool to see how easy it is to
implement extra functionality through the API. It's been very well
implemented. Currently working on a data migration plugin from
squirrelmail->rc and its a breeze.
Cor
On Jun 5, 2009, at 11:15 AM, Roland Liebl wrote:
On Fri, 05 Jun 2009 10:52:47 +0200, Thomas Bruederli <roundcube@gmail.com
OK, so you will submit it soon to SVN trunk? It is important for me too, because I follow SVN trunk with a demo version for the mail4us community. My testers should get rid of these caching issues when updating the test environment as soon as this might be available.
List info: http://lists.roundcube.net/dev/