Sorry guys, quote from Suse.DE after asking QA Mgt to advise if Evolution bugs had correct disposal as I had entered a few bugs and after 2 months no reply (Paraphrase) "Sorry I don't get down here to much with bugs that are not critical or above" I was basically told Evolution bugs don't get much of a first glance and hence stay at New for very long periods of time. Then 10.2 was released with huge upgrade issues wit the whole distro and admittedly I only look after 11PC's but the whole upgrade disaster was very concerning. I have another 8 months to decide if we purchase SLES/D based upon performance and productivity. Then suse.de released its RC with a alpha test3 blocker still unresolved - the password issue. Operationally our group may process over 11,000 messages between us. I only found out the issue after all the upgrade bugs got sorted out so you can image my distress and the by all. Also each person has up to 7 different email addresses pop3 to process. Basically if 10.4 has anything like the upgrade bugs in it or a blocker in it - I'm out of here completely and there will be no evaluation of SLES/D. Of everyone who replied they were happy to keep evolution could you please tell me if you are operating in a commercial work place? Basically I regarded the upgrade bugs I had to deal with as if the RC was Alpha in 10.2 and if they cannot get online update happening a bit better in 10.3 I will have to re-assess how much money I authorise for new hardware and other commercial software and spend it. Personally I want to keep Linux, however I don't have the luxury of personal preference to stand on P.S Good morning to all its 07:40 here (GMT+10) and its sweet to do a bit of work from home. Scott :-$ Rajko M. wrote:
On Saturday 14 April 2007 03:54, Registration Account wrote:
4. A sound confidence in that there are so many Evolution bugs that have been outstanding for a very long time 12 months +
The picture can be wrong if you look only in a number of bugs.
When you look in bug reports, there is a lot of bugs that is not easy to tell what to do as problem is reported by one person with not so common hardware or software configuration that no one else confirmed, bugs waiting for response from reporter for a long time, bugs waiting on response from upstream developers, overloaded developers not having time to check old bug reports, etc.
I guess that being busy is overall problem as you have time to check number of bugs, but not what they are, so you make your decision on facts that you have time to capture.
BTW, I'm not using Evolution, but 2 other posts in this thread that say they are satisfied with, made me wonder how can happen that Evolution has many open bugs, but still works good.