Re: What happened to the code freeze?

[Gregory Casamento]

I believe that "feature freeze" is the correct term and what I was
really after when I suggested the freeze.   I'm comfortable with any
changes that fix or improve existing functionality so long as:

1) they don't add new features and
2) They don't involve drastic refactoring of existing code.

GC

On Tue, Apr 20, 2010 at 5:30 PM, Nicola Pero
<address@hidden> wrote:
>
>> Looks like we have more commit right now during code freeze then we have
>> at normal times. I would suggest that we give up the idea of doing more
>> tests. As long as people cannot stick to a code freeze even for a week,
>
> I thought we were in "feature freeze" - ie, all commits must be bug fixes as
> opposed to
> implementation of new features.  A typical pre-release phase to iron out
> bugs before
> a release. :-)
>
> Instead, you're suggesting we're in "code freeze" - meaning no commits at
> all ?  Ie, nothing
> gets done for weeks ?  I've never seen a project do that.  Anyway it would
> be easy enough to
> do, we just all have to stop doing anything.  Hmmm.  Not sure why that would
> be useful ? ;-)
>
> Having many commits during a "feature freeze" is very good as it is supposed
> to mean
> that a lots of bugs are being fixed. :-)
>
> With about 150 bugs open in the bug tracking system, we probably need quite
> a few
> weeks of feature freeze / bug fixing to get a good release. :-)
>
> If I am the one who misunderstood and we really are in "code freeze", please
> let me know. ;-)
>
> Probably Gregory should clarify.
>
> I personally suggest we stay in a "feature freeze / bug fixing only" phase
> for a while until
> the bug count is down and the commits slow down because there are no more
> bugs to fix :-)
>
> Finally, it is quite possible you were referring to some specific changes
> that are new features
> instead of being bug fixes - presumably in the gui ?  If so, you should IMO
> feel free to point these
> out, and even revert them.
>
> Thanks
>
>
> _______________________________________________
> Gnustep-dev mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnustep-dev
>



-- 
Gregory Casamento - GNUstep Lead/Principal Consultant, OLC, Inc.
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)