consequence of 4.0 release branch?

François-Xavier Coudert Francois-Xavier.Coudert@lcp.u-psud.fr
Mon Feb 28 09:09:00 GMT 2005


>> What does this mean for testing patches?  Does a fortran patch
>> require testing for both mainline and the release branch?  I'll
> 
> Yes, this is how it's supposed to work for all patches.

I don't know how I feel about that. We're having trouble keeping a minimum 
speed in fixing gfortran bugs. Basically, double testing will mean greatly 
diminishing the number of bugs that will get fixed in a given amount of time.

I understand the reasons for this rule, but since we're using a different 
policy for gfortran (that is, all patches are applied to mainline and 4.0), 
we might say that every patch needs only testing on mainline. Or, perhaps 
more reasonnable, that every libfortran patch needs only testing on one branch.

I hope I don't interefere in grown-up discussions as I'm new to gfortran 
development, but I wanted to contribute my opinion.

FX



More information about the Fortran mailing list