From: Crawford C. <cc...@c-...> - 2008-07-04 07:34:43
|
I'm not sure at this point if I'll be able to attend this meeting or not - but I will definitely try. One thing anyone - and most especially experienced people like you and I - can do to help get these issues fixed is to generate unit test cases that illustrate any bugs. I can't over-state how useful it is to have a unit test case, and how important it is longer term to ensure any bugs don't re-emerge. So I'd strongly recommend that as a starting point. C. Michael Daum wrote: > Hi all, > > I have just finished a call with one of my clients. The result of it > is that we decided to downgrade from TWiki-4.2 to TWiki-4.1.2 > because 4.2 is too buggy, i.e. the user code. > > To keep that client I had to argue in length what actually is going > on within the TWikiCommunity and why and what and when this all > is going to be fixed ... which I actually don't know. > > This client is quite unsettled if TWiki was the right strategy to > continue to build their intranet with. > > The only thing left for me was to help them downgrading and > promissing them to do what I can to get the next TWiki-4.2.x release out. > > Fact is, we are losing our faces if we are not going to fix this > thing As Soon As Possible! > > Please, let's have a meeting, on IRC or on SKYPE, > to discuss how we can move ahead. > > I'd suggest that we will use a Monday #twiki_release meeting > time slot just for that issue. > > We need to start actioning here. So anybody who is able > to fix TWiki in that area, to all perl developers with an interest in TWiki: > please join, please offer your helping hand. > > This is a case of emergency! > > Michael. > > -- Crawford Currie - C-Dot Consultants http://c-dot.co.uk - A WikiRing Partner http://wikiring.com - landline: +44-1606-330-242 - mobile: +44-7837-877-956 - public key http://keyserver.veridis.com:11371/search?q=Crawford+Currie |