From: Adam R. <ad...@ex...> - 2009-11-10 22:48:22
|
> There are thousands of users of this software. Chances are that any one user > uses a certain subset of functionality. If it works for you, that's > wonderful! If it is broken for someone else, and we can fix it before going > live, isn't that preferable? (The answer depends on whether you are the user > who has the bug, of course.) > > Shouldn't we strive to do everything we can to make sure that each release > of eXist is as stable and bug-free as possible? And if all it takes is a > little extra SCM process and a couple of weeks (in a development cycle that > has taken many months), is that too big a price to pay? I feel that the eXist part is done. We have completed our testing and also taken a lot of input from users (like those who follow trunk). I would advise anyone to test a new version of ANY software in a development setting to understand the full implications of an upgrade and how to manage that, before they move to a production environment. As such, I feel that our part is done, and its now time for your part. Test 1.4.0 and if your comfortable with it then use it in live, if not then feedback to us and wait for 1.4.1. I know a lot of very serious users/developers who will never immediately use a version "1" of any software branch in a production system, they will wait some time for known bugs to appear and be documented first. Risk. Its all about risk and trying to reduce that, IMHO we have worked hard to keep risk low, but only you can manage the risk of your higher-level software. -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |