db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <banda...@gmail.com>
Subject Re: (10.2 maintenance release version for Jira?) Re: [jira] Updated: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux
Date Thu, 03 Aug 2006 17:08:28 GMT
Hi Rick,

Currently both Andrew and myself have JIRA-admin access, though Andrew
has been doing all the work lately.

I have been thinking of giving up my JIRA-admin access... May be the
right time now to switch it over to you, since you are the release
manager for 10.2.

Satheesh

Rick Hillegas wrote:

> Yes, please! If I knew the JIRA magic to do this, I would mumble it.
> Could someone teach me the magic, and if necessary, give me karma to
> mumble?
>
> Thanks,
> -Rick
>
> Kathey Marsden wrote:
>
>> Rick Hillegas (JIRA) wrote:
>>
>>> It appears that fixing this bug will require us to agree on some
>>> mechanism for caching VM-global Derby state. This seems to be an
>>> architectural decision which requires careful thought and
>>> experiment. I think we should defer this to a future release. I am
>>> moving this to 10.3 because thatt's the next release available in
>>> the dropdown. I agree with Kathey that this is a good candidate for
>>> a bug fix release in the 10.2 lineage.
>>>
>>>  
>>>
>> Sounds like a reasonable move since there is no immediate solution
>> apparent.  I was wondering though, could  we could add a  new version
>> that we can use as some of the 10.2 candidates start getting moved
>> out?  I want to say 10.2.2.0 but am not sure that is right.
>>
>> Kathey
>>
>>
>>
>
>



Mime
View raw message