[M3devel] HEADS UP: release_CM3_5_8_RC2 / code freeze

[Jay K]

Definitely these should be renamed from what they are.
Does "kext" bother anyone else, enough to come up with another name? kext is the extension for "kernel extensions" on Darwin -- drivers.
 
Maybe I can get one more change in in the day window. :) Or it can be in after the RC, ok. It's a very compatible and fairly desirable change, to shorten the symlink chain lengths.
 
 - Jay


----------------------------------------
> Date: Wed, 15 Jul 2009 19:35:01 +0200
> From: wagner at elegosoft.com
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com; m3-support at elego.de
> Subject: RE: [M3devel] HEADS UP: release_CM3_5_8_RC2 / code freeze
>
> OK< I've done the first changes to RC2 myself now:-/
>
> cvs commit -m 'consistently rename programs lex, yacc, tok, ext to
> klex, kyacc, ktok, kext' caltech-parser
>
> The following files have been changed:
> T caltech-parser/parserlib/kext/src/m3makefile
> T caltech-parser/parserlib/klex/src/m3makefile
> T caltech-parser/parserlib/ktok/src/m3makefile
> T caltech-parser/parserlib/kyacc/src/m3makefile
> T caltech-parser/parserlib/parserlib/src/parser.tmpl
>
> I think that change is justified as we do not want to ship competing
> yaccs and lexs again, that's rather surprising (not to say annoying).
>
> I'd suggest we'll wait another day for late fixes and then build
> the RC2 packages.
> Any comments/suggestions so far?
>
> Olaf
>
> Quoting Jay K :
>
>> I'd still like to:
>>
>> reduce the indirection in the recently introduced symlinks..it is
>> a small change (that's what I always say!) (though the movement from
>> pkg to lib I wouldn't call small)
>>
>>
>> improve the state of a few targets, esp. ARM_DARWIN, I386_SOLARIS,
>> AMD64_SOLARIS, maybe SPARC64_SOLARIS, SPARC64_OPENBSD,
>> AMD64_OPENBSD, AMD64_NETBSD, I386_OPENBSD, maybe others
>>
>> These might be be mostly just:
>> - updating RTSignalC.c
>> - updating the GNU configuration name for AMD64_SOLARIS in
>> m3cc/src/m3makefile
>> - fix my Python scripts to consume the master package list,
>> build m3gdb, build cm3ide, build in dependency order (huh, I thought
>> they always did, now not sure), add your feature of passing on
>> extra parameteres to cm3
>> - maybe change the *.sh files to accept parameters in any order
>> like the *.py
>> - maybe whittle away more on m3core/src/unix
>>
>> Also some minor features I'll propose shortly.
>>
>> - Jay
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------
>>> Date: Wed, 15 Jul 2009 11:33:56 +0200
>>> From: wagner at elegosoft.com
>>> To: jay.krell at cornell.edu
>>> CC: m3devel at elegosoft.com; m3-support at elego.de
>>> Subject: RE: [M3devel] HEADS UP: release_CM3_5_8_RC2 / code freeze
>>>
>>> Quoting Jay K :
>>>
>>>> How does one checkout, update or commit to RC2 and beyond RC2?
>>>
>>> No changes here. I'd just like to avoid branching for the release,
>>> and concentrate work on it.
>>>
>>>> There is still maybe the formsedit crash. I'll verify soon.
>>>>
>>>> Ideally we get to a situation in which distributions are built every
>>>> day and what we ship is merely picked among them. I need to ever
>>>> get Tinderbox working and under cron or in a loop.
>>>>
>>>> I also wonder if we should go back to 5.7.something, since we burned
>>>> through 5.7 fairly fast.
>>>
>>> Please, let's just provide one stable official release, and not confuse
>>> anybody by using old version numbers.
>>>
>>> Olaf
>>>
>>>> ----------------------------------------
>>>>> Date: Wed, 15 Jul 2009 08:31:40 +0200
>>>>> From: wagner at elegosoft.com
>>>>> To: m3devel at elegosoft.com
>>>>> CC: m3-support at elego.de
>>>>> Subject: [M3devel] HEADS UP: release_CM3_5_8_RC2 / code freeze
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I'm currently tagging the source base with release_CM3_5_8_RC2.
>>>>> The reported compiler vesion will be d5.8.2 for this RC.
>>>>> There seems to be a neverending stream of commits, which makes
>>>>> it quite difficult to choose a good time to do this, but I hope
>>>>> that Tinderbox will show no major problems with the tagged sources.
>>>>>
>>>>> I'd like everybody for the next weeks to postpone their functional
>>>>> changes and concentrate on testing and fixing bugs that are found
>>>>> or already known. If anybody knows of any problems with the current
>>>>> tag we can still move it in places _before_ we build any release
>>>>> archives. Tagging the whole repository is a quite costly operation
>>>>> in CVS.
>>>>>
>>>>> To summarize:
>>>>>
>>>>> o refrain from functional changes
>>>>> o report and correct bugs
>>>>> o don't build any distribution archives until we've agreed we've
>>>>> tagged a good source set
>>>>>
>>>>> I'll perform some testing myself and try to prepare a draft for the
>>>>> release notes (a lot of changes occured in the recent years) within the
>>>>> next days.
>>>>>
>>>>> Thanks for your patience and your contribution,
>>>>>
>>>>> Olaf
>>>>> --
>>>>> Olaf Wagner -- elego Software Solutions GmbH
>>>>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
>>>>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
>>>>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
>>>>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr:
>>>>> DE163214194
>>>>>
>>>
>>>
>>>
>>> --
>>> Olaf Wagner -- elego Software Solutions GmbH
>>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
>>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
>>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
>>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>>>
>
>
>
> --
> Olaf Wagner -- elego Software Solutions GmbH
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>