Post-release tasks

configure.ac

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

documentation/source/download/index.rst

@@ -2,12 +2,12 @@
 Install Open Dylan
 ******************
 
-The current version is **Open Dylan 2026.1**.
+The current version is **Open Dylan 2026.2**.
 
 Unix Platforms
 ==============
 
-➟ `Download binaries from GitHub <https://github.com/dylan-lang/opendylan/releases/tag/v2026.1.0>`_
+➟ `Download binaries from GitHub <https://github.com/dylan-lang/opendylan/releases/tag/v2026.2.0>`_
 
 Note that Unix versions only have a command-line compiler and not the full IDE that is
 available on Windows, although there is some integration with VS Code and Emacs.
@@ -27,7 +27,7 @@ Windows
 Open Dylan for Windows is currently a 32-bit application that runs under the WOW64 x86
 emulator on Windows 10 64-bit machines.
 
-➟ `Download binaries from GitHub <https://github.com/dylan-lang/opendylan/releases/tag/v2026.1.0>`_
+➟ `Download binaries from GitHub <https://github.com/dylan-lang/opendylan/releases/tag/v2026.2.0>`_
 
 For installation, double-click on the installer, and follow instructions.  You
 need to have either the PellesC linker or the linker of VC++ 6.0, 7.0 or the

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

@@ -13,7 +13,7 @@ now here is a manual check-list.
 #. Update submodules to the latest stable version tags and document the version
    number changes in the release notes. This command may help::
 
-     git submodule foreach --quiet 'echo -n "$name "; git describe --always --tags $sha1'
+     git submodule foreach --quiet 'echo "$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
@@ -76,7 +76,14 @@ now here is a manual check-list.
    entire "sources" directory is copied into the release, so any uncommitted
    files or a "_build" directory could be copied.
 
-   On unix platforms::
+   On Linux::
+
+     $ git clone --recursive https://github.com/dylan-lang/opendylan
+     $ cd opendylan
+     $ git co v2019.1.0      # the tag you created above
+     $ ./build/unix/container-release.sh
+
+   On other unix platforms::
 
      $ git clone --recursive https://github.com/dylan-lang/opendylan
      $ cd opendylan
@@ -131,7 +138,7 @@ Post-release Tasks
 
 These items aren't urgent but should be done after each release.
 
-#. Bump the OD version to something plausible, like 2023.1pre. `Example pull
+#. Bump the OD version to something plausible, like 2023.1pre1. `Example pull
    request <https://github.com/dylan-lang/opendylan/pull/1465>`_.
 
 #. Create a file in which to put the release notes for the next version. See

dylan-package.json

@@ -26,7 +26,7 @@
         "testworks"
     ],
     "url": "https://github.com/dylan-lang/opendylan",
-    "version": "2026.1.0",
+    "version": "2026.2.0",
     "license": "DUAL",
     "license-url": "https://github.com/dylan-lang/opendylan/blob/master/License.txt"
 }

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

@@ -22,7 +22,7 @@ define constant $license-agreement-filename   = "License.txt";
 /// Release constants
 define constant $release-product-name       = "Open Dylan";
 define constant $release-product-identifier = "opendylan";
-define constant $release-version            = "2026.2";
+define constant $release-version            = "2026.3pre1";
 
 define constant $release-copyright
   = "Copyright (c) 1997-2004, Functional Objects, Inc.\n"