medley-210827

We've moving to separate releases of medley and maiko.
Just get the latest version of each.

Or, you could pick up the medley release and build your own maiko.

 `medley-`releasename`.tgz`

To use (from a shell/terminal window):

1. Unpack the medley tar file

tar -xvfz medley-210827.tgz

and the maiko file for your os.arch, e.g.,

     tar -xvfz maiko-210823.linux.x86_64.tgz

This should leave you with two directories, medley and maiko.
Then you can

cd medley
./run-medley -full

medley-210825

We've moving to separate releases of medley and maiko.
Just get the latest version of each.

Or, you could pick up the medley release and build your own maiko.

 `medley-`releasename`.tgz`

To use (from a shell/terminal window):

1. Unpack the medley tar file

tar -xvfz medley-210825.tgz

and the maiko file for your os.arch, e.g.,

     tar -xvfz maiko-210823.linux.x86_64.tgz

This should leave you with two directories, medley and maiko.
Then you can

cd medley
./run-medley -full

nightly-210815

Each release should have a subset of the medley repo in a file
medley-releasename.tgz

and at least one
maiko-releasename.osname.arch.tgz

e.g.,
maiko-nightly-210815.linux.x86_64.tgz

for each os/arch pair for which we have GitHub "action" runners.

To use (from a shell/terminal window):

1. Unpack the medley tar file

tar -xvfz medley-nightly-210815.tgz

and the maiko file for your os.arch

tar -xvfz maiko-nightly-210815.linux.x86_64.tgz

this should leave you with two new directories, medley and maiko.
Then you can

cd medley
./run-medley -full

nightly-210806

Each release should have a subset of the medley repo in a file
medley-releasename.tgz

and at least one
maiko-releasename.osname.arch.tgz

e.g.,
maiko-nightly-210806.linux.x86_64.tgz

for each os/arch pair for which we have GitHub "action" runners.

To use (from a shell/terminal window):

1. Unpack the medley tar file

tar -xvfz medley-nightly-210806.tgz

and the maiko file for your os.arch

tar -xvfz maiko-nightly-210806.linux.x86_64.tgz

this should leave you with two new directories, medley and maiko.
Then you can

cd medley
./run-medley -full

nightly-210804

Each release should have a subset of the medley repo in a file
medley-releasename.tgz

and at least one
maiko-releasename.osname.arch.tgz

e.g.,
maiko-nightly-210804.linux.x86_64.tgz

for each os/arch pair for which we have GitHub "action" runners.

To use (from a shell/terminal window):

1. Unpack the medley tar file

tar -xvfz medley-nightly-210804.tgz

and the maiko file for your os.arch

tar -xvfz maiko-nightly-210804.linux.x86_64.tgz

this should leave you with two new directories, medley and maiko.
Then you can

cd medley
./run-medley -full

nightly-210506

Each release should have a subset of the medley repo in a file
medley-releasename.tgz

and at least one
maiko-releasename.osname.arch.tgz

e.g.,
maiko-nightly-210506.linux.x86_64.tgz

for each os/arch pair for which we have GitHub "action" runners.

To use (from a shell/terminal window):

1. Unpack the medley tar file

tar -xvfz medley-nightly-210506.tgz

and the maiko file for your os.arch

tar -xvfz maiko-nightly-210506.linux.x86_64.tgz

this should leave you with two new directories, medley and maiko.
Then you can

cd medley
./run-medley -full

nightly-210502

Each release should have a subset of the medley repo in a file
medley-releasename.tgz

and at least one
maiko-releasename.osname.arch.tgz

e.g.,
maiko-nightly-210502.linux.x86_64.tgz

for each os/arch pair for which we have GitHub "action" runners.

To use (from a shell/terminal window):

1. Unpack the medley tar file

tar -xvfz medley-nightly-210502.tgz

and the maiko file for your os.arch

tar -xvfz maiko-nightly-210502.linux.x86_64.tgz

this should leave you with two new directories, medley and maiko.
Then you can

cd medley
./run-medley -full

nightly-210424

Each release should have a subset of the medley repo in a file
medley-releasename.tgz

and at least one
maiko-releasename.osname.arch.tgz

e.g.,
maiko-nightly-210424.linux.x86_64.tgz

for each os/arch pair for which we have GitHub "action" runners.

To use (from a shell/terminal window):

1. Unpack the medley tar file

tar -xvfz medley-nightly-210424.tgz

and the maiko file for your os.arch

tar -xvfz maiko-nightly-210424.linux.x86_64.tgz

this should leave you with two new directories, medley and maiko.
Then you can

cd medley
./run-medley -full

What's Changed

• Add -screensize arg to run-medley by @AbeJellinek in #44
• Reorg try4 to match Ron's lispcore by @masinter in #66
• Update Dockerfile and add Maiko as submodule by @AbeJellinek in #57
• Simpler init by @masinter in #71
• Don't change LOGINDIR LDEINIT default if already set by @masinter in #78
• Lisp testing by @masinter in #107
• Create CODE_OF_CONDUCT.md by @masinter in #112
• Ignore versions + macinterface + some cleanup of internal/test by @masinter in #118
• Remove Maiko submodule. by @AbeJellinek in #123
• Larry teditmenu by @masinter in #128
• Undo 2 edits correcting textmodules ref by @masinter in #131
• add MEDLEY-FIX-DIRS to fix dates of (most of) medley repo by @masinter in #129
• Added ~= selector for COMPAREDIRECTORIES to exclude byte-equal files.… by @rmkaplan in #141
• dir and fb behave badly when filing.enumeration.depth is T; change it by @masinter in #151
• Medley utilities by @masinter in #153
• move palatino fonts down into c0 by @masinter in #156
• Update instructions for building and running & coordinate with Wiki by @masinter in #161
• remove (some) duplicate fonts by @masinter in #158
• Rename to MEDLEY-FIX-LINK… by @masinter in #155
• Move organizational health files (back)to Interlisp/.GitHub master branch by @masinter in #147
• Revert "Move organizational health files (back)to Interlisp/.GitHub master branch" by @masinter in #165
• UTF-8 wasn't interpreting EOLCONVENTION by @rmkaplan in #171
• move loadup scripts + part of initial phase of cleanup by @masinter in #174
• Restore fontprofile by @masinter in #200
• Now that XQuartz supports m1 mac, don't need separate instructions by @masinter in #179
• Fix run-medley -dimensions processing to make sensible choices by @nbriggs in #217
• Making loadups from "scratch" by @masinter in #187
• Move all of sunloadup directory to obsolete by @masinter in #234
• Move unused X-window package sources to obsolete by @masinter in #236
• Removed files duplicated in Lispusers by @masinter in #237
• remove note files by @masinter in #238
• delete WINDOW-OLD, old version of WINDOW by @masinter in #241
• SYNCLISPFILES was the way of patching sysouts but it was unreliable, full of special cases, obsolete now by @masinter in #242
• Of historical interest: BCPL and Dorado microcode, moved by @masinter in #240
• Main cleanup of new init process, scripts, etc by @masinter in #243
• remove nits by @masinter in #245
• XREM.CM used in mid-from-init loadup script doesn't need package lookups by @masinter in #246
• SUNFONT set DISPLAYFONTDIRECTORIES incorrectly by @masinter in #248
• Make exports.all and whereis.hash in tmp directory. Add script to release. by @masinter in #249
• removed files duplicated or older versions of library/lafite by @masinter in #250
• READ-PRINT-PROFILE only mentioned by internal/library/MULTI-COMPILE by @masinter in #258
• unixprint by @masinter in #254
• Save RDSYS for reading sysouts. Made by loadup-init by @masinter in #251
• Added release notes by @masinter in #225
• COLOR on LispUsers older than copy in library by @masinter in #255
• add options to run-medley for new sysouts by @masinter in #259
• move older "new" TEDIT by @masinter in #252
• new loadup full by @masinter in #261
• Remove awkward duplicate function CHECKTRAN by @masinter in #274
• Changes to interpret.rem.cm and sysout et all by @masinter in #273
• MAPATOMS contains an older definition (by a few hours) than fn in LLBASIC by @masinter in #256
• Loadup failure ldeinit by @nbriggs in #286
• move staging file for whereis.hash (back?) to {DSK} by @masinter in #283
• Fix sysout makesys to make new versions by @masinter in #277
• Checktran called from outside block, remove one blockcompile by @masinter in #278
• Revert "Checktran called from outside block, remove one blockcompile" by @masinter in #292
• Revert "Fix sysout makesys to make new versions" by @masinter in #293
• sysout logout version by @masinter in #296
• dwim dwimify checktran fix by @masinter in #295
• Add back in files that were in lisp.venuesysout by @masinter in #298
• Second try release scripts by @masinter in #284
• Add writing guard to subrs.h and running again by @masinter in #279
• Fix eolconv.sh script so tr doesn't choke on bad UTF-8 data by @nbriggs in #309
• Change default EOL to LF on UFS by @rmkaplan in #312

New Contributors

• @AbeJellinek made their first contribution in #44

Full Changelog: v3.5.2-pre-alpha-test...nightly-210424

nightly-210329

Each release should have a subset of the medley repo in a file
medley-releasename.tgz

and at least one
maiko-releasename.osname.arch.tgz

e.g.,
maiko-nightly-210329.linux.x86_64.tgz

for each os/arch pair for which we have GitHub "action" runners.

To use (from a shell/terminal window):

1. Unpack the medley tar file

tar -xvfz medley-nightly-210329.tgz

and the maiko file for your os.arch

tar -xvfz maiko-nightly-210329.linux.x86_64.tgz

this should leave you with two new directories, medley and maiko.
Then you can

cd medley
./run-medley -full