Mailing-List: contact scout-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: scout-dev@ws.apache.org
Received-SPF: pass (herse.apache.org: domain of linsun.unc@gmail.com
 designates 66.249.82.237 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=qTVuU/Dw3kiSguORYCgUtE8VuZDUiofHp4Nsh47/KZChiKXjPooZFwr02BgzzN02rKPLync28NUFbZOBY8W9q5A+I3b4WrvT9m55HOAeIwXpMNmG47arNsvUXtPmCgmwsIvGYSj9udsoyjj4tH/wM4S6cIJJMCTA4KkoST2D2s0=
Message-ID: <469E0D38.9000405@gmail.com>
Date: Wed, 18 Jul 2007 08:53:12 -0400
From: Lin Sun <linsun.unc@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: scout-dev@ws.apache.org
Subject: Re: Scout Release Plans
References: <46951A72.3040603@gmail.com> <4695775B.40108@apache.org>
 <4696083F.7050309@gmail.com> <4697835F.4020906@apache.org>
 <4697D660.7020400@gmail.com> <4697D70F.3070508@apache.org>
 <469C2F6F.6040908@gmail.com> <469DF6E9.2050608@apache.org>
In-Reply-To: <469DF6E9.2050608@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Kurt, I am sorry that I misunderstood you.  I had thought these fixes 
were already avail as all the JIRAs were marked as fixed/closed.   I had 
thought we just need to merge these fixes to trunk...  No?

Lin

Kurt T Stam wrote:
> Hi Lin,
> 
> I think we want to try to get them fixed. I should have time tomorrow to
> take a look at it. Hopefully we can complete the vote by Friday and get
> rc1 out over the weekend.
> 
> --Kurt
> 
> Lin Sun wrote:
>> Yes you are right - I was able to see the commit for some of the
>> jiras, but not all of them.   I guess all looked minor except scout 11
>> which doesn't contain any commit log/info.   I remember there is some
>> issues related to classification fixed recently (like scout 23, 24,
>> 30) so scout 11 may have been already fixed in trunk.
>>
>> If we decide we are going to merge this fixes into trunk, I am okay
>> with that.  I'd like to get the rc1 build soon so that I can start
>> test it in geronimo env. and fix any possible issues that might have
>> been regressed.
>>
>> Thanks, Lin
>>
>> Kurt T Stam wrote:
>>> You should be able to see it in SVN. Like for SCOUT-15:
>>>
>>> https://issues.apache.org/jira/browse/SCOUT-15?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel
>>>
>>>
>>> Hope that helps.
>>>
>>> --Kurt
>>>
>>> Lin Sun wrote:
>>>> Hi Kurt,
>>>>
>>>> I looked at them, I think most of them sounds minor fixes, and should
>>>> not impact us.    However, I haven't been able to figure out how to
>>>> tell which revision is associated with JIRA yet.   I'd like to do that
>>>> if there is an easy way to.
>>>>
>>>> I think [SCOUT-15] is fixed in trunk.
>>>>
>>>> Lin
>>>>
>>>> Kurt T Stam wrote:
>>>>> Hi Lin,
>>>>>
>>>>> If you have time maybe you can take a look at
>>>>>
>>>>> https://issues.apache.org/jira/browse/SCOUT-42
>>>>>
>>>>> --Kurt
>>>>>
>>>>> Lin Sun wrote:
>>>>>> Hi Kurt,
>>>>>>
>>>>>> That sounds great for me.   1.0rc1 is good and we can test it in our
>>>>>> env.   Let me know if there is anything I can do to help out.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Lin
>>>>>>
>>>>>> Kurt T Stam wrote:
>>>>>>> Hi Lin,
>>>>>>>
>>>>>>> I'm also interested in a build for Scout in roughly the same
>>>>>>> time-frame.
>>>>>>>
>>>>>>> We currently have three issues in jira:
>>>>>>>
>>>>>>> SCOUT-38 <https://issues.apache.org/jira/browse/SCOUT-38> Produce
>>>>>>> website from the maven2 build
>>>>>>> <https://issues.apache.org/jira/browse/SCOUT-38>
>>>>>>> Not related to the code, but I'm working on it and it's almost done
>>>>>>> anyway
>>>>>>>
>>>>>>> SCOUT-14 <https://issues.apache.org/jira/browse/SCOUT-14> Binaries
>>>>>>> from
>>>>>>> download are empty <https://issues.apache.org/jira/browse/SCOUT-14>
>>>>>>> Not related to the code, This should be fixed when SCOUT-38 is done.
>>>>>>>
>>>>>>> SCOUT-12 <https://issues.apache.org/jira/browse/SCOUT-12> Implement
>>>>>>> the
>>>>>>> Asynchronous Registry Request Feature
>>>>>>> <https://issues.apache.org/jira/browse/SCOUT-12>
>>>>>>> Seems like no one is jumping to get this implemented.
>>>>>>>
>>>>>>> So I would be actually be fine with a 1.0 build now :). Should we
>>>>>>> vote
>>>>>>> on doing a 1.0rc1?
>>>>>>>
>>>>>>> Input still welcome:).
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> --Kurt
>>>>>>>
>>>>>>> p.s. As a side note, maybe we can follow it up by a 1.1 version
>>>>>>> in the
>>>>>>> August time frame that supports JAXB on top the XMLBean UDDIv2
>>>>>>> binding.
>>>>>>> I'm currently working on that in my workspace to see what it
>>>>>>> takes and
>>>>>>> it takes a bit of moving code around between classes to make that
>>>>>>> work.
>>>>>>> (I'm also doing this work so we can add a UDDI v3 binding).
>>>>>>>
>>>>>>> Lin Sun wrote:
>>>>>>>> Hi there,
>>>>>>>>
>>>>>>>> I wanted to let y'all know that Apache Geronimo is working towards
>>>>>>>> our
>>>>>>>> 2.0 release and the projects goals for 2.0 are to ship scout as the
>>>>>>>> JAXR 1.0 implementation.  So far we are doing well with JAXR tck in
>>>>>>>> geronimo by using the latest scout snapshot and would very much
>>>>>>>> like
>>>>>>>> to include scout in our 2.0 release.
>>>>>>>>
>>>>>>>> To plan better I'd like to know what the next version of Scout
>>>>>>>> (1.0?)
>>>>>>>> release plans are.  we'd like to get Apache Geronimo 2.0 out around
>>>>>>>> the end of July.
>>>>>>>>
>>>>>>>> Input welcome :)
>>>>>>>>
>>>>>>>> Lin
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>>>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org