Re: GNUstep Code Freeze

[Gregory Casamento]

Fred,

I need to determine if the current issue with changing outlet names in
Gorm is due to an AppKit issue or a Gorm issue.   This shouldn't take
long.

I'll report back shortly.

GC

On Sun, Jan 29, 2012 at 4:49 PM, Fred Kiefer <address@hidden> wrote:
> I would like to collect some feedback on the current state.
> Are there any bugs still open that would block making a release? That would
> be really serious bugs that stop a critical GNUstep application from
> working, definitely worked in the last release and cannot be worked around
> in some way.
>
> As for the ICU locale issue we have the work around to not use ICU for
> people with other languages, that should give them about the fallback that
> they had in previous base releases.
>
> As for the gui bugs, I am under the impression that we wont be able so fix
> much more for this release. But a lot of testing is still going on.
>
> Adam, are you willing to prepare this release again?
>
> Fred
>
>
> On 20.01.2012 00:27, Fred Kiefer wrote:
>>
>> In order to get a full GNUstep release out before FOSDEM, that is at
>> least base/gui/back, maybe also make, Richard, Eric and I have decided
>> to put a code freeze for these libraries in place. Only strict bug fixes
>> should go into the code over the next week (or maybe a bit longer) and
>> everybody should try to find time to test the current code on as many
>> different machines as possible.
>>
>> There hasn't been a gui release in almost a year and now seems as good a
>> time as ever. Feel free to report any bugs you find on the mailing list
>> or even better in the bug tracker on Savannah.
>
>
> _______________________________________________
> Gnustep-dev mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnustep-dev



-- 
Gregory Casamento
Open Logic Corporation, Principal Consultant
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)
http://www.gnustep.org
http://heronsperch.blogspot.com