[M3devel] HEADS UP: Release engineering, was: Re: CM3 Release

[Jay]

> o complete switch to new Unix headers
 
 
I386_DARWIN and AMD64_DARWIN not switched.
ok though either way.


> o working cvsup (OK AFAIK)
 
 
ok, though I didn't add it to build automation.
 

> o formsvbt crashes
 
Not solved.
I couldn't get an older release to work to verify against.
 

> o performance issues: threads, exception frames, texts, ...
 
 
A little better.
I don't think regressed wrt cm3 though.
Can release asis I think.
 

> We must also decide which platforms _must_ be part of the release.
> I'd suggest AMD64_LINUX, LINUXLIBC6, FreeBSD(4/7?), SOLgnu,
> I386_DARWIN (and/or AMD64_DARWIN?), and of course Windows (native and
> Cygwin, however these are called these days ;-)

 
I'd just as soon skip Cygwin.
 Maybe we can have some sort of "tiers"?
All of PPC_DARWIN, I386_DARWIN, AMD64_DARWIN can be included.
Many others /can/ be included, but I don't know what must/should be included.
 

> Should we add more? I'll need support to build several of them.
>
> I suggest that we use the old make_bin_dist_min.sh scripts with
> the core distribution. Or is something better already completely
> automated (possibly by Jay)?
 
 
I have good automation, with some caveats:
 
No cminstall.
A few packages should be added:
  m3gdb, cm3ide, cvsup
 
 
There might be a few copyrights missing, and they might be so numerous that a directory should be created, if that is "prominent" enough.
 
There is always more work to do..

 - Jay