Re: What happened to the code freeze?

[Gregory Casamento]

The feature freeze only includes core (make, base, gui and back).   I
don't really consider the WinUXTheme (or any of the themes) to be part
of the freeze, so your changes are fine where they are.

I should have been more concise about the scope of the freeze I wanted
in the first place.  That would have avoided some of the current
confusion.

I would like Doug to send the patches he's got in mind to Fred for
review and testing.

GC

On Wed, Apr 21, 2010 at 2:04 PM, Eric Wasylishen <address@hidden> wrote:
> Sorry, two of my recent theme-related commits were probably inappropriate to
> make  during the feature freeze (adding an option to disable the inner
> border in NSScrollView, and moving NSBrowser header drawing to GSTheme). I
> can revert these if you'd like.
> Doug: the Windows menu fixes sound great. I was noticing a lot of menu
> flickering with the WinUX theme, and mousewheel scrolling in Ink was really
> laggy - I bet your patch will fix those problems.
> Eric
> On Wed, Apr 21, 2010 at 11:32 AM, Gregory Casamento
> <address@hidden> wrote:
>>
>> 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



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