Imported text files may be encoded with UTF-8, ISO 8859-1, or CP 1252. -They can be converted to ASCII, high ASCII, or Mac OS Roman.
+For plain text conversions, imported text files may be encoded with +UTF-8, ISO 8859-1, or CP 1252. They can be converted to ASCII, high ASCII, or Mac OS Roman.
diff --git a/docs/index.html b/docs/index.html index ac0082c..ff6e4d7 100644 --- a/docs/index.html +++ b/docs/index.html @@ -105,7 +105,7 @@-Download the latest release (1.0.1) from github.
+Download the latest release (1.0.2) from github.The full source code for CiderPress II is available on diff --git a/ndocs/publish.py b/ndocs/publish.py index 7e560bb..8bc494f 100644 --- a/ndocs/publish.py +++ b/ndocs/publish.py @@ -15,7 +15,7 @@ # Current version string. Used for text substitution. -app_version = "1.0.1" +app_version = "1.0.2" pkg_version = app_version # ----- nothing configurable below ----- diff --git a/ndocs/top/SourceNotes.md b/ndocs/top/SourceNotes.md index 8b55f0b..7464237 100644 --- a/ndocs/top/SourceNotes.md +++ b/ndocs/top/SourceNotes.md @@ -124,39 +124,40 @@ updating versions and running a final set of tests on the app. 1. Update the version number in `AppCommon/GlobalAppVersion.cs`. This changes the version number displayed by the applications, and determines the version in the filenames generated by MakeDist. - 1. Update the version number in `DiskArc/Defs.cs`. This just tracks + 2. Update the version number in `DiskArc/Defs.cs`. This just tracks GlobalAppVersion. It's stored redundantly because the library is intended to be separable from the application. (You don't need to update this for a non-final release.) - 1. Do a full build of the project in Visual Studio, in Debug mode. It's + 3. Do a full build of the project in Visual Studio, in Debug mode. It's important to build for Debug to enable assertions and extended checks. Note this step builds MakeDist with the updated version number. - 1. Launch the GUI application. Verify the version number. It's also good + 4. Launch the GUI application. Verify the version number. It's also good to do this because, in a Debug build, some library unit tests are executed during app startup. - 1. Run the command-line tests: `cp2 debug-test`, `cp2 debug-test-da`, - and `cp2 debug-test-fc`. All tests must pass. If you're not built for - Debug mode, you will see a warning at the end of the test runs. + 5. Run the command-line tests: `cp2 debug-test`, `cp2 debug-test-da`, + and `cp2 debug-test-fc`. These require files in the TestData directory. + All tests must pass. If you're not built for Debug mode, you will see + a warning at the end of the test runs. If this is a "final" release, you will need to publish updated documentation as well. Don't do this for pre-releases; the web documentation should always match the latest final release. - 1. Update the `app_version` number in `ndocs/publish.py`. This is used + 6. Update the `app_version` number in `ndocs/publish.py`. This is used for text substitution in the descriptive text and installer links. - 1. From the command line, in the `ndocs` directory, run `publish.py` + 7. From the command line, in the `ndocs` directory, run `publish.py` (you may need to explicitly run python). This will update the contents of the `docs` directory and the top-level documentation (including this file) with the contents of `ndocs`. Check the diffs. Finally, build the applications and submit the changes. - 1. Run `makedist build` from the top level of the source tree (it'll be in + 8. Run `makedist build` from the top level of the source tree (it'll be in `MakeDist/bin/debug/NET6.0`). This builds the distribution packages. The output will be in the `DIST` directory. - 1. Submit all changes to git, push them to the server. - 1. Create a new release on github. Drag `DIST/*.zip` into the release. - 1. Update/close any issues that have been addressed by the new release. + 9. Submit all changes to git, push them to the server. + 10. Create a new release on github. Drag `DIST/*.zip` into the release. + 11. Update/close any issues that have been addressed by the new release. Version numbers should follow the semantic versioning scheme: v1.2.3, v1.2.3-dev1, etc.