On Mon, 2 Aug 2010 17:33:09 +0200, Cor Bosman cor@xs4all.nl wrote:
We have about 50,000 users depending on it right now, and im running SVN-3838 or something. The SVN versions are generally better than 0.4-beta. But you have to be willing to be on top of things. I check the tracker almost every day to see if any serious issues were addressed, or more importantly, patches were reversed.
Cor
Agreed. My ~2000 users are on r3788. I decided to hold it there until the Safari/Windows attachment bug was fixed. (That happened over the weekend.) I do not update my "production" server until I have identified a stable Trunk release, and even then only after testing.
I would recommend that if you decide to go this route, install Subversion to checkout and manage your Trunk version rather than manually downloading a nightly build. Using Subversion you can easily backout a bad update.
- Arne
================================== I want to add a comment to this. I have no real concerns about using a trunk version in production - with two requirements.
One is that I be deliberate and careful in testing and choosing a stable release, and that once a stable version has been identified and placed into production, don't keep upgrading as the trunk changes. Wait for a compelling reason to change.
The other is that I probably would NOT use a trunk early in the development cycle. Doing so now as we approach the stable release isn't too bad, but early on it would be harder to find a version to sit on.
-- Arne Berglund System Administrator, Internet Services Lane Education Service District Eugene, OR 541.461.8343 ____________
List info: http://lists.roundcube.net/users/
Arne Berglund wrote:
One is that I be deliberate and careful in testing and choosing a stable release, and that once a stable version has been identified and placed into production, don't keep upgrading as the trunk changes. Wait for a compelling reason to change.
It would be nice for those of use who don't have te time and/or skills to manage our own subversion server if the devs would simply release more beta builds using the stable trunk builds as they are identified - which is kindof the point of betas, isn't it? It would provide a lot more exposure and potential bug reports if this would happen.
Of course, I'm not really complaining - if time/resources don't permit (how many roundcube devs are there? I imagine they all have full time jobs, etc), then we get what we get... :)
On Mon, Aug 2, 2010 at 11:14 AM, Charles Marcus CMarcus@media-brokers.com wrote:
It would be nice for those of use who don't have te time and/or skills to manage our own subversion server if the devs would simply release more beta builds using the stable trunk builds as they are identified - which is kindof the point of betas, isn't it? It would provide a lot more exposure and potential bug reports if this would happen.
Of course, I'm not really complaining - if time/resources don't permit (how many roundcube devs are there? I imagine they all have full time jobs, etc), then we get what we get... :)
Agreed. It's not ideal for me to have to test these out until I find a stable version. I manage multiple servers, but it's not really in my job description to test out development versions to find a stable release. If I find time, it may be what I have to do, but I don't right now.
-
Arne Berglund -
Bradlee Landis -
Charles Marcus