Freeze Approaching

[A. Karl Kornel]

On Sep 2, 2005, at 7:19 PM, Max Kanat-Alexander wrote:

>     For anybody who was unaware or had forgotten, the development  
> freeze
> for 2.22 is coming up on September 15.

     It would be hard for me to forget, as I had never known.  Would  
you mind giving me a URL where I could go to in order to see  
"September 15 is the freeze date for 2.22", and where I could also  
see the freeze dates for 2.24 and later?

>     I think that we can all agree that *this* time, we really  
> should keep
> our development freeze. We moved it for 2.20, and now 2.20 has been
> frozen for six months because its development period was too long.
>
>     If we're ever going to get back onto a normal release schedule,  
> we have
> to start freezing when we say we're going to freeze. :-)

     I feel pretty betrayed by this freeze date.  I spent most of my  
time working on bugs targeted for 2.20, and doing QA for 2.20, only  
to discover that there won't be more than a few days between the  
release of 2.20 and the freeze of 2.22.  This makes me ask the  
following question:  Assuming I'm here to work on 2.24, why should I  
even spend any time fixing bugs in, or QA testing, 2.22, if it means  
I will have little time to work on code for 2.24?

     Later!


===================
|  Alfred Karl Kornel
|
|   kornel.1 at osu.edu
===================