directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <aok...@bellsouth.net>
Subject Re: Convo summary: Procedures for Directory committers working on trunks
Date Fri, 24 Feb 2006 23:18:24 GMT
Ersin Er wrote:

>On 2/24/06, Emmanuel Lecharny <elecharny@gmail.com> wrote:
>  
>
>>Ersin Er a écrit :
>>
>>>The convo started with my question "What procedure would we follow for
>>>backporting some 1.1 trunk changes (fixes) to 1.0 ?"
>>>
>>>And the convo evolved then and I'm summarizing Alex's points here:
>>>
>>>* We need to be much more carefull from now on because we have a more
>>>complicate structure with releases and branches. We should triple
>>>check our work.
>>>      
>>>
>>+1. And triple may not be enough :) That means, to the least, no commit
>>before having run successfully a mvn -Dregressions test
>>    
>>
>
>I agree. And one problem I face is files I've forget to commit. So in
>case our tests pass, our patch may not cause the same effect in trunks
>on the server. So we need to be sure that we added all our changes to
>the patch (or svn added them).
>  
>
Perhaps CI and better test coverage can help.  We need to setup cruise 
control or continuum.  I'll volunteer space and resources for this.

Alex

Mime
View raw message