alpha release

[Jeff Faath <jf...@apache.org>]

I think it's time we take a vote on the alpha release.  All the alpha issues
have been more or less completed and I've made some changes over the past
couple days to shore up the implemented APIs.  Anyone else have outstanding
work or are we ready for the release?  +1 for me.

 

On another note, I'm going to start working on a new API, probably Custody
Transfer.  Let's also plan on having another conference call in the near
future to discuss development status.

 

-Jeff

Re: alpha release

[Tom Cunningham <tc...@redhat.com>]

Is there any further testing we want to do on it before declaring 
alpha?        I'd like to take another once-over on the docs before we 
ship -  I think I changed a few things late that didn't make it back 
into the docs yet.

Kurt T Stam wrote:
> Hi Jeff,
>
> I think we're good for alpha too. I want to see if I can hook up one 
> or two unit tests in cargo. I think we can reuse some of the test code 
> created for core api, but then send over a webservice call. After 
> that, given that no one else sees any reason to postpone the release I 
> will create the releasable artifacts and start a vote.
>
> So please contact me if you have more stuff to commit that you're not 
> sure of whether it should go into alpha. Maybe we can create another 
> branch for that (beta?).
>
> I'll try to also work on the 2.0rc6 release. It'd be great if we could 
> put out 2.0 final soon, put it on a branch switch the 3.0 code base to 
> the trunk.
>
> Let's plan on discussing plans next week. Maybe we can do on irc so we 
> end up with the transcripts after.
>
> --Kurt
>
>
> Jeff Faath wrote:
>>
>> I think it’s time we take a vote on the alpha release. All the alpha 
>> issues have been more or less completed and I’ve made some changes 
>> over the past couple days to shore up the implemented APIs. Anyone 
>> else have outstanding work or are we ready for the release? +1 for me.
>>
>> On another note, I’m going to start working on a new API, probably 
>> Custody Transfer. Let’s also plan on having another conference call 
>> in the near future to discuss development status.
>>
>> -Jeff
>>
>

Re: alpha release

[Kurt T Stam <ku...@gmail.com>]

Hi Jeff,

I think we're good for alpha too. I want to see if I can hook up one or 
two unit tests in cargo. I think we can reuse some of the test code 
created for core api, but then send over a webservice call. After that, 
given that no one else sees any reason to postpone the release I will 
create the releasable artifacts and start a vote.

So please contact me if you have more stuff to commit that you're not 
sure of whether it should go into alpha. Maybe we can create another 
branch for that (beta?).

I'll try to also work on the 2.0rc6 release. It'd be great if we could 
put out 2.0 final soon, put it on a branch switch the 3.0 code base to 
the trunk.

Let's plan on discussing plans next week. Maybe we can do on irc so we 
end up with the transcripts after.

--Kurt


Jeff Faath wrote:
>
> I think it’s time we take a vote on the alpha release. All the alpha 
> issues have been more or less completed and I’ve made some changes 
> over the past couple days to shore up the implemented APIs. Anyone 
> else have outstanding work or are we ready for the release? +1 for me.
>
> On another note, I’m going to start working on a new API, probably 
> Custody Transfer. Let’s also plan on having another conference call in 
> the near future to discuss development status.
>
> -Jeff
>