Re: when should we do another release?

[Brett Porter <br...@apache.org>]

Attempted to send this last week, but it got lost in the conference  
wireless problems it seems.

Same question still stands - though I don't think we can release  
immediately as the code is much less stable right now (and there's 3  
outstanding "vetoes" on r584279, r584218, r583412). But if we agree a  
release is needed, we need to ensure that:
- those issues get addressed as the top priority, rather than fixing  
more issues
- the snapshot dependencies we have get released soon

The only work I particularly want to see included in this release at  
this point is MRM-37 since it was pretty much done before r583412 and  
I'd rather have that in to get additional testing time. MRM-516 would  
be good to have first, but not essential.

Thoughts?

- Brett

On 10/10/2007, at 4:39 PM, Brett Porter wrote:

> It looks like the beta-3 is growing a bit all the time since we  
> identified it as the last beta. I took a run through the issues and  
> pushed some non-essential things out.
>
> There seem to be a number of good changes already, when do folks  
> think we should have another release? I think having another beta  
> might be helpful in getting some testing done on the recent stuff  
> while wrapping up the remaining issues.
>
> - Brett
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>

--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/

Re: when should we do another release?

[Maria Odea Ching <oc...@exist.com>]

+1 on releasing 1.0-beta-3 at least after the mentioned r583412 
questions and MRM-398 issue have been resolved :-)

-Deng

Brett Porter wrote:
> Thoughts?
>
> MRM-37 is done, but the following are outstanding:
>
> - r583412 response
> - plexus-webdav release (looks like it's getting close)
> - MRM-398 was reopened (though it's not a blocker problem)
>
> Cheers,
> Brett
>
> On 14/10/2007, at 9:55 AM, Brett Porter wrote:
>
>> Attempted to send this last week, but it got lost in the conference 
>> wireless problems it seems.
>>
>> Same question still stands - though I don't think we can release 
>> immediately as the code is much less stable right now (and there's 3 
>> outstanding "vetoes" on r584279, r584218, r583412). But if we agree a 
>> release is needed, we need to ensure that:
>> - those issues get addressed as the top priority, rather than fixing 
>> more issues
>> - the snapshot dependencies we have get released soon
>>
>> The only work I particularly want to see included in this release at 
>> this point is MRM-37 since it was pretty much done before r583412 and 
>> I'd rather have that in to get additional testing time. MRM-516 would 
>> be good to have first, but not essential.
>>
>> Thoughts?
>>
>> - Brett
>>
>> On 10/10/2007, at 4:39 PM, Brett Porter wrote:
>>
>>> It looks like the beta-3 is growing a bit all the time since we 
>>> identified it as the last beta. I took a run through the issues and 
>>> pushed some non-essential things out.
>>>
>>> There seem to be a number of good changes already, when do folks 
>>> think we should have another release? I think having another beta 
>>> might be helpful in getting some testing done on the recent stuff 
>>> while wrapping up the remaining issues.
>>>
>>> - Brett
>>>
>>> -- 
>>> Brett Porter - brett@apache.org
>>> Blog: http://www.devzuz.org/blogs/bporter/
>>>
>>
>> -- 
>> Brett Porter - brett@apache.org
>> Blog: http://www.devzuz.org/blogs/bporter/
>>
>
> -- 
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>

Re: when should we do another release?

[Brett Porter <br...@apache.org>]

Thoughts?

MRM-37 is done, but the following are outstanding:

- r583412 response
- plexus-webdav release (looks like it's getting close)
- MRM-398 was reopened (though it's not a blocker problem)

Cheers,
Brett

On 14/10/2007, at 9:55 AM, Brett Porter wrote:

> Attempted to send this last week, but it got lost in the conference  
> wireless problems it seems.
>
> Same question still stands - though I don't think we can release  
> immediately as the code is much less stable right now (and there's  
> 3 outstanding "vetoes" on r584279, r584218, r583412). But if we  
> agree a release is needed, we need to ensure that:
> - those issues get addressed as the top priority, rather than  
> fixing more issues
> - the snapshot dependencies we have get released soon
>
> The only work I particularly want to see included in this release  
> at this point is MRM-37 since it was pretty much done before  
> r583412 and I'd rather have that in to get additional testing time.  
> MRM-516 would be good to have first, but not essential.
>
> Thoughts?
>
> - Brett
>
> On 10/10/2007, at 4:39 PM, Brett Porter wrote:
>
>> It looks like the beta-3 is growing a bit all the time since we  
>> identified it as the last beta. I took a run through the issues  
>> and pushed some non-essential things out.
>>
>> There seem to be a number of good changes already, when do folks  
>> think we should have another release? I think having another beta  
>> might be helpful in getting some testing done on the recent stuff  
>> while wrapping up the remaining issues.
>>
>> - Brett
>>
>> --
>> Brett Porter - brett@apache.org
>> Blog: http://www.devzuz.org/blogs/bporter/
>>
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>

--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/