[castor-dev] =?utf-8?B?UkU6IFtjYXN0b3ItZGV2XSB1bmFibGUgdG8gY2FsbCB1cGRhdGU=?=

[Matthew Baird]

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

I guess I'm worried because my Oracle patch never got committed (twice submitted) I don't know who has commit status, and currently there are a bunch of bugs (ie set-method, get-method) that made it into a release that should have been caught by unit tests. Should we patch those? or will they not make it into the main line? I'm not adverse to hunting down the get-set bugs, but the code is complex, and while it might take us a long time to hunt down the get-set method bugs, it could take one of you guys a couple hours. I wish we had "spare time" to work on this but such is the lifestyle.   You are right, adding new features at this point isn't a high priority if the architecture is changing, but fixing bugs should be. IMHO reporting bugs on a mailing list isn't very effective, and the bugzilla db isn't up to date (as far as I know). maybe someone other than the developers should consider maintaining a bug database that the castor dev people can look at, to see what users in the field are doing; in a lot of cases we (the users) are stressing castor JDO a lot more than even the developers.   Having said that, I do appreciate you guys working on this product, especially in your valuable spare time. Keep up the good work.   cheers, Matthew -----Original Message----- From: Thomas Yip [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 11:51 AM 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 >>> >> >