I don't care about specific features so long as a supported, upgradable plug-in ability is supported. Hopefully something better than the hook implementation of the SF codebase (hooks didn't usually survive upgrades without modifications) but I'll take anything at this point.
On Thu, Jan 15, 2004 at 04:23:43PM -0600, Zeljko Dimic wrote: > Let me answer this for Joey. > The short answer to your question is: The RCL continues to be the supported > version of the client code. > > I recently moved from Development into Product Management, and one of my > most important objectives is to develop specifications for a new > architecture of the client code (RCL) and have the new code built. > > We are redesigning the client code to incorporate some of the best features > of the Source Forge version. Joey has briefed me on all of the requests by > the development community, but feel free to contact me off the list and > submit your suggestions. Presently, we have prioritized the enhancements > and defined the business requirements. The next step is a functional spec. > This whole exercise is a significant effort and it will be the second part > of 2004 before we release new RCL architecture. > > Zeljko Dimic > Technical Product Manager > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Joe Rhett > Sent: Wednesday, January 14, 2004 6:10 PM > To: Joey deVilla > Cc: [EMAIL PROTECTED] > Subject: Time is up! Verdict please... > > > Hey Joey. It's been 4 months since you said you were going to make a > determination on whether we go to the SF client base, or drop it > entirely. Can we get a judgement here? > > And no, "we're keeping both but ..." isn't an acceptable answer. > > I don't care how you do it, but a client which provides the ability to > plug in a payment interface that can survive minor upgrades (aka hooks or > whatever) is necessary. Tell us how you will be providing it. > > I personally don't care which way you go, I just want a SINGLE answer. > > -- > Joe Rhett Chief Geek > [EMAIL PROTECTED] Isite Services, Inc. -- Joe Rhett Chief Geek [EMAIL PROTECTED] Isite Services, Inc.
