Steve,

This proposal was subsumed into Sam's, just to be clear.

I agree with your statements below.

Glyn


                                                                                       
                                               
                      "Steve Loughran"                                                 
                                               
                      <[EMAIL PROTECTED]        To:       <[EMAIL PROTECTED]>     
                                               
                      om>                      cc:                                     
                                               
                                               Subject:  Re: [VOTE] Re: managing 
change during the 1.0 release process                
                      26/09/02 11:16                                                   
                                               
                      Please respond to                                                
                                               
                      axis-dev                                                         
                                               
                                                                                       
                                               
                                                                                       
                                               




----- Original Message -----
From: "Glyn Normington" <[EMAIL PROTECTED]>

>
> So, let's put this to the vote: "create a branch for 1.0 and allow only
> agreed changes to be committed to that branch".
>
> Here's my +1.

Ultimately we will have to branch, and by branching now people who want to
add features can continue, while the branch gets stable

+1.

now, Can we have Gump build the 1.0 branch as well as CVS_HEAD?

For changes to be fed back from the CVS_HEAD to 1.0, we need to keep the
delta between head and 1.0 to a minimum, which means a lockdown on
gratuitous refactoring, reformatting, etc. The rate of change of the Axis
code base is very high -a sign of an evolving product and perhaps a side
effect of the refactoring support in eclipse and IDEA. We also need to be
rigorous about CVS checkin messages to make comparing branches easier

-steve





Reply via email to