James in in a code freeze pending release of version 2.1 I can't say when the release is likely to happen, but it is unlikely that this issue is going to be addressed before then.
The reason for it not being fixed before now is because we inherit it from Avalon. We are intending to replace that with our own filesystem code in the next cycle. d. > -----Original Message----- > From: Dejan Nenov [mailto:[EMAIL PROTECTED]] > Sent: 19 December 2002 07:44 > To: [EMAIL PROTECTED] > Subject: There is no active development on James > > > To any committers / active contributors to James development out there - > can you please review and verify bug 15460 - unless no one else can > reproduce the problem - it seems to be making James totally unusable! > > > > Thank you, > > > > Dejan > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
