Re: [castor-dev] unable to call update

[Thomas Yip]

Title: Re: [castor-dev] unable to call update

No doubt that Castor JDO is moving too slow. I really would like to be an full time Castor developer, like I was. There is really a lot of deadlines here, I don’t even have much “free” time!!   The OQL side is certainly need test cases and bug fixes. If you willing to work on that, it would be great. Test cases and fixes will last beyond to next versions. After that we might have something more interesting for you to work on. It might disappoint you, but test cases, fixes and patch review were what I spent my rare “free” time in the last few months.   I hardly have chance to wrote new code either.       Thomas   -----Original Message----- >From: Low Heng Sin [mailto:[EMAIL PROTECTED]] >Sent: Thursday, January 10, 2002 6:33 PM >To: [EMAIL PROTECTED] >Subject: Re: [castor-dev] unable to call update > >Thomas, >I believe there might be one or more Castor-JDO user out there >who are willing to participate as part/full time Castor-JDO >developer ( I'm interested to join as a part-timer ). What is >the requirement/policy here to participate as a developer ? >IMHO, Castor-JDO's are moving too slow now and this is not >good for the Castor-JDO future. >  >Regards, >Low >-----Original Message----- >>From: Thomas Yip [mailto:[EMAIL PROTECTED]] >>Sent: Friday, January 11, 2002 3:51 >>To: [EMAIL PROTECTED] >>Subject: Re: [castor-dev] unable to call update >>Hi Matthew, >>  >>There are three active part-times including me. >>  >>  >>Working on a product without future, or will ever a >>second-rated alternative doesn’t interest me to >>spend my after work hours on it. And, I am spending >>time on that. I do believe Castor JDO have a future. >>  >>The plan for existing branch is bug fixing. >>It is unlikely that we will invest significant time on >>new feature in the existing branch. I will be (and >>have been) extremely caution on user patches, >>especially those “new feature” one. >>  >>On the development side, we are continuing on >>revising the architecture. However, it would take >>considerable time for that to be finished and mature. >>While we don’t have a lot of “free” time currently, >>it means it will take long time before the public will >>see it. >>  >>  >>  >>  >>Thomas >>  >>-----Original Message----- >>>From: Matthew Baird [mailto:[EMAIL PROTECTED]] >>>Sent: Thursday, January 10, 2002 10:58 AM >>>To: [EMAIL PROTECTED] >>>Subject: [castor-dev] RE: [castor-dev] unable to call update >>> >>>is anyone working on Castor JDO? >>>  >>>I ask, because we've invested some time in using it, and I would like to know if we should consider a migration to another solution. >>>  >>>I'm definitely not trying to be pushy, but it would help a lot for decision making purposes to know what's happening, and what the plans are for the JDO code. >>>-----Original Message----- >>>From: Thomas Yip [mailto:[EMAIL PROTECTED]] >>>Sent: Thursday, January 10, 2002 10:30 AM >>>To: [EMAIL PROTECTED] >>>Subject: Re: [castor-dev] unable to call update >>>  >>>  >>>  >>>  >>>  >>>  >>>-----Original Message----- >>>>From: Matthew Baird [mailto:[EMAIL PROTECTED]] >>>>Sent: Thursday, January 10, 2002 10:04 AM >>>>To: [EMAIL PROTECTED] >>>>Subject: RE: [castor-dev] unable to call update >>>> >>>>just out of interest Thomas, do you work full time on Castor JDO? >>>  >>>I did. But, not now. >>>  >>>  >>>  >>>Thomas >>>  >>>>-----Original Message----- >>>>>From: Thomas Yip >>>>>Sent: Thu 1/10/2002 9:48 AM >>>>>To: [EMAIL PROTECTED] >>>>>Cc: >>>>>Subject: Re: [castor-dev] unable to call update >>>>>Hope it helps. I am very busy since the end of the holiday. I might not able >>>>>to give >>>>>you any further help until a few week later. >>>>> >>>>>Thomas >>>>> >>>> >>> >> >