2023.1 release

Makefile.in

@@ -191,7 +191,7 @@ BOOTSTRAP_3_ROOT = $(abs_builddir)/Bootstrap.3
 BOOTSTRAP_3_LIBRARIES = \
 	dylan-compiler dylan-environment parser-compiler dswank
 BOOTSTRAP_3_STATICS = \
-	dylan-tool
+	dylan-tool-app
 
 BOOTSTRAP_3_COMPILER = \
         $(BOOTSTRAP_2_ROOT)/bin/dylan-compiler \
@@ -348,7 +348,7 @@ dist: 3-stage-bootstrap
 	rm -rf release/opendylan-$(version)/sources/bootstrap1-registry
 	cp -R Bootstrap.3/bin release/opendylan-$(version)/
 	cp -R Bootstrap.3/sbin/* release/opendylan-$(version)/bin
-	ln -s dylan-tool release/opendylan-$(version)/bin/dylan
+	ln -s dylan-tool-app release/opendylan-$(version)/bin/dylan
 	cp -R Bootstrap.3/databases release/opendylan-$(version)/
 	-cp -R Bootstrap.3/include/opendylan release/opendylan-$(version)/include
 	cp -R Bootstrap.3/lib release/opendylan-$(version)/

README.md

@@ -9,7 +9,7 @@ If you're reading this inside of a binary release that you just downloaded and
 unpacked, then this is all you need to do to get started:
 
   ```
-  $ export PATH=/path/to/opendylan-2022.1/bin:$PATH    # for bash
+  $ export PATH=/path/to/opendylan/bin:$PATH    # for bash
   ```
 
 Verify that the downloaded version is working correctly by building a

configure.ac

@@ -1,4 +1,4 @@
-AC_INIT([Open Dylan], [2023.1pre])
+AC_INIT([Open Dylan], [2023.1])
 AC_PREREQ(2.50)
 
 # Directory for config.guess etc.

documentation/getting-started-cli/source/dylan-compiler.rst

@@ -1,14 +1,14 @@
 Using dylan-compiler interactively
 ==================================
 
-The interactive mode of ``dylan-compiler`` allows you to carry out
-multiple development tasks over a period of time without having to
-restart the console compiler each time.  To start the console
-environment in interactive mode, enter ``dylan-compiler`` without any
-arguments at a shell. For example::
+The interactive mode of :program:`dylan-compiler` allows you to carry out
+multiple development tasks over a period of time without having to restart the
+console compiler each time.  To start the console environment in interactive
+mode, enter :program:`dylan-compiler` without any arguments at a shell. For
+example::
 
     $ dylan-compiler
-    Welcome to Open Dylan, Version 2022.1.
+    Welcome to Open Dylan!
 
     For documentation on Open Dylan, see http://opendylan.org/documentation/.
     See http://opendylan.org/documentation/getting-started-cli/ for an introduction to the command line tools.

documentation/getting-started-cli/source/dylan-environment.rst

@@ -45,7 +45,7 @@ interactive mode, opens the playground project, performs some
 arithmetic, defines a method, and then traces it::
 
     $ dylan-environment
-    Welcome to Open Dylan, Version 2022.1.
+    Welcome to Open Dylan!
 
     > play
     Opened project gui-dylan-playground

documentation/hacker-guide/source/topics/making-a-release.rst

@@ -12,7 +12,9 @@ now here is a manual check-list.
    out.
 
 #. Update submodules to the latest stable version tags and document the version
-   number changes in the release notes.
+   number changes in the release notes. This command may help::
+
+     git submodule foreach --quiet 'echo -n "$name "; git describe --always --tags $sha1'
 
    What "stable" means isn't well-defined; use your discretion. The important
    point is that libraries are bundled with the release so people may use them
@@ -22,7 +24,7 @@ now here is a manual check-list.
 #. Test on supported platforms.
 
    * Do a 3-stage boostrap: make distclean, autogen.sh, configure, make, make
-     install.
+     install, make dist.
 
    * Run ``make check`` and if anything fails that is not marked ``EXPECTED TO
      FAIL``, fix the problem or discuss with others how to proceed.
@@ -34,7 +36,6 @@ now here is a manual check-list.
 #. Update the version number in the sources
 
    * In the release-info library
-   * In the build/packages/unix/README file
    * In the configure.ac file
    * Do a ``git grep`` for the previous release number, e.g., "2019.1" and see
      if anything else needs to be updated.
@@ -45,10 +46,13 @@ now here is a manual check-list.
    Download the release tarballs.
 
 #. Update the release notes. Hopefully these have been maintained as changes
-   were made.  It may be worth scanning the commit logs or pull requests.
+   were made.  GitHub's "Draft a New Release" UI provides a succinct list of
+   contributions based on pull requests since the previous release; just click
+   on "Generate release notes" button. *But don't actually create the release
+   yet, until the release notes have been committed.*
 
    To determine what to put in the Contributors section of the notes, this
-   command is useful (with obvious modifications)::
+   command is useful (but modify the tag argument)::
 
      git log --format=short --no-merges v2019.1.0..origin/master | grep '^Author: ' | sort | uniq -c | sort -n
 

documentation/man-pages/source/conf.py

@@ -51,9 +51,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = '2022.1'
+version = '2023.1'
 # The full version, including alpha/beta/rc tags.
-release = '2022.1.0'
+release = '2023.1.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

documentation/release-notes/source/2023.1.rst

@@ -2,11 +2,11 @@
 Open Dylan 2023.1
 *****************
 
-This document describes the 2023.1 release of Open Dylan, released DD
-Month, 2023.  This release contains many enhancements and bug fixes,
-highlights of which are listed below.  For complete details see `the opendylan
-commit logs
-<https://github.com/dylan-lang/opendylan/compare/v2022.1.0...v2023.1.0>`_.
+This document describes the 2023.1 release of Open Dylan, released 01
+June, 2023.  The highlights of the release are listed below.  For complete
+details see the `commit logs
+<https://github.com/dylan-lang/opendylan/compare/v2022.1.0...v2023.1.0>`_ for
+this release.
 
 .. note:: Some commit logs, for example for testworks and other libraries that
           are included in Open Dylan as git submodules, may be in other
@@ -24,30 +24,62 @@ Compiler
   <https://opendylan.org/proposals/dep-0012-string-literals.html>`_ was
   implemented, adding multi-line and "raw" string literals.
 
+* `Improvements to LLVM bitcode generation <https://github.com/dylan-lang/opendylan/pull/1469>`_
+
+* A bug in `parser expansions
+  <https://opendylan.org/documentation/library-reference/language-extensions/parser-expansions.html>`_
+  that could crash the compiler if the end delimiter was missing has been fixed.
+
+* `Bug 1490 <https://github.com/dylan-lang/opendylan/issues/1490>`_, which
+  could result in spurious warnings from the compiler `has been fixed
+  <https://github.com/dylan-lang/opendylan/pull/1492>`_.
+
+
 Tooling
 =======
 
-Run-time
-========
+* The `dylan <https://github.com/dylan-lang/dylan-tool>`_ command-line tool has
+  had `various improvements
+  <https://github.com/dylan-lang/dylan-tool/compare/730b5c99627ac653636ddaf01187a213d7d23aa8...f6edf2ef5f5c04f295a075ae70eb8462580be4ef>`_,
+  including:
 
-Platform Support
-================
+  * Simplified workspace model
+  * Simplified process to publish packages
+  * Packages installed locally in workspace directory by default
+  * Global package installation follows the `XDG Base Directory Specification
+    <https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html>`_.
+  * Symlink points to current installed version of packages, for easier tooling.
 
-IDE
-===
+  Full documentation is
+  `here <https://docs.opendylan.org/packages/dylan-tool/documentation/source/index.html>`_.
 
-Documentation
-=============
+* The :program:`make-dylan-app` program has been removed and is replaced by
+  :command:`dylan new application` and :command:`dylan new library`.
 
-Library Changes
-===============
 
-common-dylan Library
---------------------
+Library Updates
+===============
 
-io Library
+Submodules
 ----------
 
+Open Dylan uses Git submodules to pull in some dependencies and user programs
+may depend on these for now. The notable changes in those submodules are listed
+below:
+
+* **sphinx-extensions** - Improvements to DRM references.
+
+* **dylan-tool** - See above.
+
+* **collection-extensions** - The ``split-at`` function has been removed. Use
+  :gf:`split` instead. Documentation improvements.
+
+* **command-line-parser** - Minor bug fix to add a missing newline when no
+  subcommand is provided.
+
+* **json** - Fixed ``sort-keys?`` option for recursive :gf:`print-json` calls.
+
+
 system Library
 --------------
 
@@ -56,18 +88,19 @@ system Library
 
 * The :func:`run-application` function is now fully documented.
 
+* A ``follow-links?:`` keyword argument has been added to the
+  :func:`file-exists?` function. The default is true, for compatibility with the
+  previous behavior.
+
 
 Contributors
 ============
 
-We'd like to thank all the people that made contributions to this release and
-to surrounding libraries in the Dylan ecosystem. This list is probably
+We'd like to thank all the people who made contributions to this release and to
+surrounding libraries in the Dylan ecosystem. This list is probably
 incomplete...
 
+* Fernando Raya
 * Peter S. Housel
+* Bruce Mitchener
 * Carl Gay
-* Peter Hull
-* phongphan
-* Fernando Raya
-* Pierre De Pascale
-* kryptine

documentation/release-notes/source/conf.py

@@ -47,9 +47,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = '2022.1'
+version = '2023.1'
 # The full version, including alpha/beta/rc tags.
-release = '2022.1.0'
+release = '2023.1.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

documentation/release-notes/source/index.rst

@@ -3,6 +3,7 @@ Open Dylan Release Notes
 
 .. toctree::
 
+   2023.1
    2022.1
    2020.1
    2019.1

sources/examples/README.rst

@@ -7,7 +7,7 @@ a `working Open Dylan <https://opendylan.org/download/index.html>`_ installation
 To verify that your installation is working correctly, check the compiler's version::
 
     $ dylan-compiler -version
-    Version 2022.1
+    Version 2023.1
 
 If a version string doesn't appear, :command:`dylan-compiler` may not be on
 your ``$PATH``. For help, check the `installation instructions

sources/lib/release-info/common-info.dylan

@@ -22,7 +22,7 @@ define constant $help-filename                = "opendylan.chm";
 /// Release constants
 define constant $release-product-name       = "Open Dylan";
 define constant $release-product-identifier = "opendylan";
-define constant $release-version            = "2023.1pre";
+define constant $release-version            = "2023.1";
 
 define constant $release-copyright
   = "Copyright (c) 1997-2004, Functional Objects, Inc.\n"

sources/registry/generic/dylan-tool

@@ -1 +1 @@
-abstract://dylan/app/dylan-tool/dylan-tool.lid
+abstract://dylan/app/dylan-tool/sources/dylan-tool.lid

sources/registry/generic/dylan-tool-app

@@ -0,0 +1 @@
+abstract://dylan/app/dylan-tool/sources/dylan-tool-app.lid

sources/registry/generic/dylan-tool-test-suite

@@ -1 +1 @@
-abstract://dylan/app/dylan-tool/tests/dylan-tool-test-suite.lid
+abstract://dylan/app/dylan-tool/sources/test-suite.lid