Bump version number and update change log.

Author: c-lipka

changes.txt

@@ -29,10 +29,8 @@ should be located in the same directory as this file is.
 ------------------------------------------------------------------------------
 
 
-Changes between v3.7.1-rc.1 and v3.8.0-???
-==========================================
-
-This version is still under active development, and not finalized yet.
+Changes between v3.7.1-rc.1 and v3.8.0-beta.1
+=============================================
 
 NOTE: This release cycle has been redesignated v3.8.0. There will not be a
 v3.7.1 release proper.
@@ -74,6 +72,11 @@ Changed Behaviour
   - Greyscale output no longer automatically forces bit depth to 16 bpc. To get
     16 bpp greyscale output, explicitly specify `Bits_Per_Color=16`.
   - Preview now reflects greyscale setting.
+  - POV-Ray will now warn when using v3.7 or v3.8 features without matching
+    `#version` directive.
+  - For consistency, POV-Ray will no longer throw an error whenever
+    encountering anything macro-related in v3.0 scenes, and instead just
+    warn when encountering `#macro` in such scenes.
 
 New Features
 ------------
@@ -117,7 +120,7 @@ Reported via GitHub:
   - #317 ("Boost 1.65.0 incompatibility")
   - #319 ("Need -lboost_date_time in non-optimized Unix builds")
   - #341 ("macOS build failure for 3.7.0.5", configure script failing to use
-    -lboost_system with Boost 1.66)
+    `-lboost_system` with Boost 1.66)
   - #342 ("AX_FIX_INCORRECT_PATH is broken", configure script failing to
     properly handle `.` directory in `C_INCLUDE_PATH` or `CPLUS_INCLUDE_PATH`)
   - #403 ("povray 3.7.0.8 does not build on macOS 11.0 Big Sur").
@@ -174,9 +177,6 @@ Development Related
 Other Noteworthy
 ----------------
 
-  - During alpha development phase, POV-Ray v3.8.0-alpha for Windows will
-    piggypack on an existing v3.7 installation to allow for raw binary
-    distribution.
   - The source code now requires a C++11-compliant compiler.
   - The Unix build process now officially requires Autoconf 2.68 or later.
   - Added `--generation` command-line switch to POV-Ray for Unix, which will

revision.txt

@@ -32,9 +32,92 @@ Notes:
 ------------------------------------------------------------------------------
 
 ------------------------------------------------------------------------------
-POV-Ray v3.8.0-???
+POV-Ray v3.8.0-beta.1
 ------------------------------------------------------------------------------
 
+Commit 946673f5 on 2021-07-11 by Christoph Lipka
+
+    Warn when using v3.8 features without `#version 3.8`.
+
+    - Addresses issue #420
+    - POV-Ray will now warn when using v3.7 or v3.8 features without matching
+      `#version` directive.
+    - For consistency, POV-Ray will no longer throw an error whenever
+      encountering anything macro-related in v3.0 scenes, and instead just
+      warn when encountering `#macro` in such scenes.
+    - Modified internal tracking of scene language version to use a dedicated
+      class instead of an `int`.
+    - Added a framework to print certain warnings only once.
+
+Commit a50e1202 on 2021-07-11 by Christoph Lipka
+
+    Change editor DLL distribution method.
+
+    - `cmedit*.dll` will now be distributed under the AGPL 3 as part of
+      the POV-Ray installer proper; only `povcmax*.dll` will continue to be
+      deployed separately.
+    - Editor DLLs no longer come in a 32-bit SSE2 flavor. Instead, both
+      32-bit variants of POV-Ray for Windows now use the same set of DLLs.
+
+Commit b408434a on 2021-07-11 by Christoph Lipka
+
+    Miscellaneous housekeeping for v3.8.0 beta.
+
+    - Update list of contributors (preliminary).
+    - Fix typo in `scenes/portfolio/readme.txt`.
+    - Fix GitHub Workflow for automated builds.
+    - Update GitHub release build Workflow to earmark binary as official.
+
+Commit 50dfa9b4 on 2021-07-11 by Christoph Lipka
+
+    Try to fix GitHub release build Workflow failing to build source
+    documentation.
+
+    - Update `tools/doxygen/doxygen.sh` script (and a few otther tool scripts)
+      to check out as executable.
+    - Include PlantUML tool in repository.
+
+Commit f6d214dd on 2021-07-09 by TonVanDenBroek
+
+    Changes to support OpenEXR 3.0. (#423)
+
+Commit 5385cec6 on 2021-06-26 by Christoph Lipka
+
+    More work on GitHub Actions.
+
+    - Add Workflows for automated releases and GitHub CodeQL code analysis.
+    - Remove GitHub Actions from this branch, as we're referencing those
+      on the master branch anyway.
+    - Remove Travis CI and AppVeyor config files for this branch.
+
+Commit a4759368 on 2021-06-21 by Christoph Lipka
+
+    Refrain from issuing an error when `#version 3.8` seems to be specified
+    late.
+
+    Previous v3.8 development versions issued an outright error when the
+    scene did not start with `#version`, but specified `#version 3.8`
+    or higher later; the rationale was that such scenes would clearly not
+    be legacy scenes, and the lack of a now-mandatory leading `#version`
+    statement therefore safe to be considered an outright error without
+    breaking backward compatibility. However, the current implementation
+    fails to account for a fringe scenario involving the `Include_Header`
+    INI setting. We're therefore disabling this error for now, and just
+    let the parser issue a warning as in v3.7.
+
+Commit 065fafed on 2021-06-18 by Christoph Lipka
+
+    [ci skip] Update version information extraction scripts.
+
+    Updated the scripts that extract version information from
+    `source/base/version.h`, and added a script to extract version information
+    from binaries, in preparation for auto-building installable releases
+    using GitHub Actions.
+
+Commit e3a97fbc on 2021-06-10 by Christoph Lipka
+
+    Update change log.
+
 Commit d4cf497d on 2021-06-10 by Christoph Lipka
 
     Fix bug in transparent TGA output introduced with commit.bd73d0e6.
@@ -2354,7 +2437,7 @@ Commit e287133b on 2016-04-29 by Christoph Lipka
 
     - Remove the `+avN` postfix from generated release tags.
     - Automatically flag builds as experimental if their version number
-    has a prefix beginning with `-x`, e.g. `3.7.1-x.foo.8765432`.
+      has a prefix beginning with `-x`, e.g. `3.7.1-x.foo.8765432`.
 
     Also updated the developers' documentation on version numbering.
 
@@ -2650,20 +2733,20 @@ Commit e1e7b0df on 2016-01-24 by Christoph Lipka
 
     Fix GitHub issue #53.
 
-      - The `version` pseudo-variable will now evaluate to the effective
-        language version at the time the expression is parsed, _except_
-        when used in a `#version` directive, in which case the behaviour
-        remains unchanged.
-      - Using the `version` pseudo-variable in a `#version` directive is now
-        deprecated. A new dedicated syntax, `#version auto`, has been added
-        to explicitly set the scene language version to whatever version of
-        POV-Ray is used to render the scene, making the `#version version`
-        idiom obsolete.
-      - The requirement to start each scene with a `#version` statement
-        is now more strongly enforced for POV-Ray 3.7 scenes, by reporting
-        a parse error if the scene file does not begin with a `#version`
-        directive but does have a `#version 3.7` (or later) directive anywhere
-        in the main scene file.
+    - The `version` pseudo-variable will now evaluate to the effective
+      language version at the time the expression is parsed, _except_
+      when used in a `#version` directive, in which case the behaviour
+      remains unchanged.
+    - Using the `version` pseudo-variable in a `#version` directive is now
+      deprecated. A new dedicated syntax, `#version auto`, has been added
+      to explicitly set the scene language version to whatever version of
+      POV-Ray is used to render the scene, making the `#version version`
+      idiom obsolete.
+    - The requirement to start each scene with a `#version` statement
+      is now more strongly enforced for POV-Ray 3.7 scenes, by reporting
+      a parse error if the scene file does not begin with a `#version`
+      directive but does have a `#version 3.7` (or later) directive anywhere
+      in the main scene file.
 
 Commit bb59a4e1 on 2016-01-20 by Christoph Lipka
 
@@ -3345,7 +3428,7 @@ Commit fd2e0dd1 on 2015-01-30 by Christoph Lipka
     - Added Doxygen configuration.
     - Minor changes to stand-alone source documentation pages.
     - Styleguide change: `@startuml` tag format is now to be used for
-    sequence charts instead of `@msc` tag format.
+      sequence charts instead of `@msc` tag format.
     - Added page on compiler requirements.
 
 ------------------------------------------------------------------------------
@@ -3538,24 +3621,24 @@ Commit 54b283a0 on 2014-07-23 by Christoph Lipka
 
     Improved finish features for more realism:
 
-      - Radiosity support for brilliance is now available; to activate it,
-        specify `brilliance on` in the global radiosity settings.
-      - The brilliance effect can now be applied not only to incoming
-        light, but also to outgoing light; to activate this, specify a second
-        FLOAT value
-        after the `brilliance` keyword. For maximum realism, both parameters
-        should be set to the same value.
-      - Fresnel angle-dependent attenuation can now also be enabled for
-        highlights and the diffuse component, by specifying `fresnel on`
-        directly in the finish block.
-        (Note that you will still need to enable fresnel attenuation
-        for reflections separately; also note that where reflection and
-        highlights increase at shallow angles,
-        the diffuse component decreases accordingly.) For a perfect match
-        between reflection and highlights use the `albedo` keyword for the
-        highlight with the same
-        value as the reflection maximum; the reflection minimum should be
-        set to zero.
+    - Radiosity support for brilliance is now available; to activate it,
+      specify `brilliance on` in the global radiosity settings.
+    - The brilliance effect can now be applied not only to incoming
+      light, but also to outgoing light; to activate this, specify a second
+      FLOAT value
+      after the `brilliance` keyword. For maximum realism, both parameters
+      should be set to the same value.
+    - Fresnel angle-dependent attenuation can now also be enabled for
+      highlights and the diffuse component, by specifying `fresnel on`
+      directly in the finish block.
+      (Note that you will still need to enable fresnel attenuation
+      for reflections separately; also note that where reflection and
+      highlights increase at shallow angles,
+      the diffuse component decreases accordingly.) For a perfect match
+      between reflection and highlights use the `albedo` keyword for the
+      highlight with the same
+      value as the reflection maximum; the reflection minimum should be
+      set to zero.
 
 Commit 9b10411d on 2014-07-21 by Christoph Lipka
 
@@ -3610,8 +3693,8 @@ Commit 365fc8fd on 2014-06-27 by Christoph Lipka
 
     5th iteration of the styleguide draft; Minor changes:
 
-      - Source comments can now use the "Dot" tool.
-      - Certain method names can now use `camelCase`.
+    - Source comments can now use the "Dot" tool.
+    - Certain method names can now use `camelCase`.
 
 Commit a190a10c on 2014-06-12 by Christoph Lipka
 

source/base/version.h

@@ -100,7 +100,7 @@
 /// where `N` is a serial number starting at 1 in each phase, `TIME` is the number of minutes
 /// since 2000-01-01 00:00, and `FEATURE` is an arbitrary alphanumeric moniker for a particular
 /// experimental feature.
-#define POV_RAY_PRERELEASE          "pre-beta"
+#define POV_RAY_PRERELEASE          "beta.1"
 
 #if defined(DOXYGEN) && !defined(POV_RAY_PRERELEASE)
     // Work around doxygen being unable to document undefined macros.
@@ -111,7 +111,7 @@
 /// @def POVRAY_IS_BETA
 /// Whether this version is a beta.
 /// Leave undefined for pre-beta, release candidate or final releases.
-//#define POVRAY_IS_BETA
+#define POVRAY_IS_BETA
 
 #if defined(DOXYGEN) && !defined(POVRAY_IS_BETA)
     // Work around doxygen being unable to document undefined macros.
@@ -125,7 +125,7 @@
 /// platforms where development builds typically cannot run stand-alone, but require an existing
 /// host installation to be dropped into. Define as the latest installable release's major and
 /// minor version number for vX.Y.0.0 pre-beta versions, or leave undefined otherwise.
-#define POV_RAY_HOST_VERSION        "3.7"
+//#define POV_RAY_HOST_VERSION        "3.7"
 
 #if defined(DOXYGEN) && !defined(POV_RAY_HOST_VERSION)
     // Work around doxygen being unable to document undefined macros.