Shouldn't we keep the scout version numbers in line with the JAXR API
version they represent, rather than a corresponding UDDI API version number?
Anil Saldhana wrote:
Another thought.
We should probably rename the v1.1 to Scout v2 to reflect UDDIv2
support and then start working on Scout v3 for UDDIv3 needs (to
facilitate juddiv3 work that you guys are all doing).
--- On *Tue, 7/21/09, Tom Cunningham /<[email protected]>/* wrote:
From: Tom Cunningham <[email protected]>
Subject: Re: Request for Scout v1.1RC1
To: [email protected]
Date: Tuesday, July 21, 2009, 10:41 PM
Checked the fix in, and did some additional testing with the 1.1
changes - they look good to me!
Kurt T Stam wrote:
> Well this bug seems to have some urgency since it's holding
people up. It seems that Tom has a fix and he is double checking
things. So when he checks it in (tonight/tomorrow) we can create
some release artifacts and restart the vote for 1.1RC1.
>
> Cheers,
>
> --Kurt
>
> Anil Saldhana wrote:
>> Why not move that fix to RC2?
>>
>> --- On *Tue, 7/21/09, Kurt T Stam /<[email protected]
</mc/[email protected]>>/* wrote:
>>
>>
>> From: Kurt T Stam <[email protected]
</mc/[email protected]>>
>> Subject: Re: Request for Scout v1.1RC1
>> To: [email protected]
</mc/[email protected]>
>> Date: Tuesday, July 21, 2009, 12:29 AM
>>
>> Anil Saldhana wrote:
>> > Hi all,
>> > I have removed the xmlbeans dependency and brought in JAXB
>> into Scout in the v1.1 branch
>> (https://issues.apache.org/jira/browse/SCOUT-43). I have
merged
>> it with the latest changes in trunk. So basically v1.1
branch is
>> the latest with all the changes that happened in trunk.
>> >
>> > Given this, I would like to propose a release of Scout
v1.1RC1 asap.
>> >
>> > +1 from me.
>> >
>> > We can hold another vote to make v1.1 the trunk.
>> >
>> > Regards,
>> > Anil
>> >
>> >
>> Hi Anil,
>>
>> Pretty cool to go to JAXB :). Great work.
>> However before we can do a release I think we need to at
least fix
>> SCOUT-72, since this is a blocking the TCK issue.
>>
>> --Kurt
>>
>>
---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
</mc/[email protected]>
>> </mc/[email protected]
</mc/[email protected]>>
>> For additional commands, e-mail:
[email protected]
</mc/[email protected]>
>> </mc/[email protected]
</mc/[email protected]>>
>>
>>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
</mc/[email protected]>
> For additional commands, e-mail: [email protected]
</mc/[email protected]>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
</mc/[email protected]>
For additional commands, e-mail: [email protected]
</mc/[email protected]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
