Recent changes to Contributing

Contributing modified by Vidar Hasfjord

Vidar Hasfjord — Sat, 04 Apr 2026 13:10:12 -0000

--- v59
+++ v60
@@ -123,233 +123,5 @@

     + Upload a snapshot of the updated version of the source code to "[Files/source](http://sourceforge.net/projects/owlnext/files/source)". See existing archives for the correct directory structure.
 
     + If OWLMaker has changed, upload the updated version to "[Files/tools](http://sourceforge.net/projects/owlnext/files/tools)". See the existing archive for the correct contents and directory structure. Ideally, you should digitally sign the executables in the archive (otherwise virus checkers, browsers and operating systems may deem them unsafe). This requires that you have access to a trusted code signing certificate, or that a trusted third-party entity (e.g. a trusted project member) can sign the executables for you. Also make sure that the archive passes virus checking (e.g. at [VirusTotal](http://www.virustotal.com)).
 
     + Update the version numbers in "[Files/files-readme.md](http://sourceforge.net/projects/owlnext/files)" (OWLMaker parses this file to check for updates).
 
-    + Document the release in the wiki page "[OWLNext Releases](OWLNext_Stable_Releases)". If relevant, update wiki pages "[Installing OWLNext](Installing_OWLNext)", "[Supported Compilers](Supported_Compilers)", "[Upgrading from OWL](Upgrading_from_OWL)" (section "Changes in OWLNext"), "[FAQ](Frequently_Asked_Questions)", as well as any other wiki page affected by the changes. Finally, update the wiki [main page](Main_Page), section "Latest releases".
 
+    + Document the release in the wiki page "[OWLNext Releases](OWLNext_Stable_Releases)". If relevant, update wiki pages "[Installing OWLNext](Installing_OWLNext)", "[Supported Compilers](Supported_Compilers)", "[Upgrading from OWL](Upgrading_from_OWL)" (section "Changes in OWLNext"), "[FAQ](Frequently_Asked_Questions)", as well as any other wiki page affected by the changes.
 
     + Create a [News](http://sourceforge.net/p/owlnext/news) post announcing the release.
-
-

-
-### OWLMaker release script
-
-The following PowerShell script can be used to automate the release of a new version of OWLMaker.
-
-The script should be located in a folder that contains a subfolder "OWLMaker Package Contents", which in turn contains the current contents of the OWLMaker package (e.g. "[OWLMaker-6681.zip](https://sourceforge.net/projects/owlnext/files/tools)"). The script copies the 32-bit and 64-bit executables from the OWLMaker working directory to the corresponding folders within "OWLMaker Package Contents". You must update the script with the correct location of the OWLMaker working directory on your system.
-
-To set the credentials for the script to access our [Files](https://sourceforge.net/projects/owlnext/files) download section, you can define environment variables SOURCEFORGE_USERNAME and SOURCEFORGE_PASSWORD for your user profile in Windows. Otherwise, the script will ask for credentials interactively. To perform file transfer operations, the script uses the [Posh-SSH](https://github.com/darkoperator/Posh-SSH) module, so it has to be installed on your system for the script to work.
-
-The script starts by displaying the version of OWLMaker found in your working directory, then downloads and updates the catalog file ("[files-readme.md](https://sourceforge.net/projects/owlnext/files)") with the correct OWLMaker version number and package name.
-
-After the executables have been copied from the working directory to "OWLMaker Package Contents", the script starts kSign, a code signing tool from K Software. You should update this part of the script for your code signing solution. If you do not have a code signing certificate, and unsigned executables are acceptable, then you can remove or disable this part of the script.
-
-Finally, the script creates a new OWLMaker package and places it alongside the catalog file in the "Downloads" folder on your system. From there it then uploads the package and catalog to our [Files](https://sourceforge.net/projects/owlnext/files) download section. Note that the package is uploaded to the "tools" subfolder, while the catalog is uploaded to the root.
-
-**Note:** Perform a thorough virus scan of the package, e.g. using the [VirusTotal](https://www.virustotal.com/) online service.
-
-~~~ps1
-Clear-Host
-$nl = "`r`n"
-Write-Host -Separator $nl (
-    "",
-    "OWLMaker Release Script",
-    "See OWLNext for license information (https://sourceforge.net/projects/owlnext).",
-    "Copyright (c) 2023 Vidar Hasfjord",
-    ""   
-)
-
-function Failure {
-    param (
-        [Parameter(Mandatory=$false)]
-        [string]$ErrorMessage
-    )
-    if ($ErrorMessage) {
-        Write-Host $ErrorMessage 
-    }
-    Write-Host
-    Read-Host -Prompt "Press Enter to close"
-    if ($Global:credential) { Remove-Variable credential -Scope Global }
-    exit 1
-}
-
-# Define paths and check if they exist.
-
-$owlMaker = "..\..\OWLMaker"
-if (!(Test-Path $owlMaker)) { Failure "`"$owlMaker`" not found." }
-
-$versionHeader = "$owlMaker\version.h"
-if (!(Test-Path $versionHeader)) { Failure "`"$versionHeader`" not found." }
-
-$applicationHeader = "$owlMaker\Application.h"
-if (!(Test-Path $versionHeader)) { Failure "`"$applicationHeader`" not found." }
-
-$owlMaker64Bit = "$owlMaker\build\x64\Release\OWLMaker\OWLMaker.exe"
-if (!(Test-Path $owlMaker64Bit)) { Failure "`"$owlMaker64Bit`" not found." }
-
-$owlMaker32Bit = "$owlMaker\build\Win32\Release\OWLMaker\OWLMaker.exe"
-if (!(Test-Path $owlMaker32Bit)) { Failure "`"$owlMaker32Bit`" not found." }
-
-# Check LOCAL_TESTING flag in "Application.h".
-
-$localTestingFlagLine = Get-Content $applicationHeader| Select-String -Pattern 'LOCAL_TESTING (\d)'
-$localTesting = $localTestingFlagLine.Matches.Groups[1].Value
-if ($localTesting -ne "0") { Failure "LOCAL_TESTING is set in 'Application.h'. Did you forget to clear it?" }
-
-# Get version number and prerelease flag from "version.h".
-
-$versionLine = Get-Content $versionHeader | Select-String -Pattern 'OWLMAKER_VERSION\(v\) v\((\d+),(\d+),(\d+),(\d+)\)'
-$year, $month, $day, $revision = $versionLine.Matches.Groups[1..4].Value
-$owlMakerVersion = "$year.$month.$day.$revision"
-$prereleaseFlagLine = Get-Content $versionHeader | Select-String -Pattern 'OWLMAKER_PRERELEASE (\d)'
-$owlMakerPrerelease = $prereleaseFlagLine.Matches.Groups[1].Value
-
-# Display version numbers.
-
-Write-Host -Separator $nl (
-    "Current version of OWLMaker detected:",
-    "",
-    "   OWLMAKER_VERSION = $owlMakerVersion",
-    "   OWLMAKER_PRERELEASE = $owlMakerPrerelease",
-    ""
-)
-if ($owlMakerPrerelease -ne "0") {
-    Write-Host "Warning: OWLMAKER_PRERELEASE is set. Did you forget to clear it?$nl"
-}
-
-# Download the catalog file and show the current OWLMaker entry in the catalog.
-
-$catalogFileName = "files-readme.md"
-$catalog = "$env:HOMEPATH\Downloads\$catalogFileName"
-$project = "owlnext"
-$frsHost = "frs.sourceforge.net"
-$frsPath = "/home/frs/p/$project"
-$frsCatalogPath = "$frsPath/$catalogFileName"
-$credential = if (!$env:SOURCEFORGE_USERNAME -or !$env:SOURCEFORGE_PASSWORD)
-    {Get-Credential -UserName $env:SOURCEFORGE_USERNAME -Message "SourceForge credentials"} else
-    {New-Object System.Management.Automation.PSCredential(
-        $env:SOURCEFORGE_USERNAME, 
-        (ConvertTo-SecureString $env:SOURCEFORGE_PASSWORD -AsPlainText -Force))}
-if (!$? -or !$credential) { Failure "Failed to create PSCredential object." }
-Write-Host "Starting catalog download..."
-Get-SCPItem -Credential $credential -ComputerName $frsHost `
-    -Path $frsCatalogPath -PathType File `
-    -Destination $(Split-Path -Path $catalog -Parent)
-if (!$?) { Failure "Failed to download catalog." }
-Write-Host -Separator $nl (
-    "Downloaded the catalog file `"$frsHost`:$frsCatalogPath`".",
-    "",
-    "Current catalog entry:",
-    "",
-    (Select-String -Pattern "- OWLMaker" -Path $catalog).Line,
-    "",
-    "The next step is catalog update (if necessary), file copy and code signing. The",
-    "OWLMaker executable files will be copied to 'OWLMaker Package Contents', where",
-    "they will be digitally signed.",
-    ""
-)
-Read-Host -Prompt "Press Enter to continue"
-
-# Update the catalog, if necessary.
-
-$tmpCatalog = New-TemporaryFile
-$packageFileName = "OWLMaker-$revision.zip"
-Get-Content $catalog | ForEach-Object {
-    $line = if ($_ -match "- OWLMaker")
-        {" - OWLMaker ${owlMakerVersion}: tools/$packageFileName"} else
-        {$_}
-    $line | Out-File $tmpCatalog -Append ascii
-}
-if (Compare-Object (Get-Content $catalog) (Get-Content $tmpCatalog)) {
-    Move-Item -Force -Path $tmpCatalog -Destination $catalog
-    if (!$?) { Failure "Failed to update the downloaded catalog file." }
-    Write-Host -Separator $nl (
-        "Updated the downloaded catalog file:",
-        "",
-        (Select-String -Pattern "- OWLMaker" -Path $catalog).Line,
-        ""
-    )
-    $isCatalogUpdated = $true
-} else {
-    Remove-Item -Force -Path $tmpCatalog -ErrorAction SilentlyContinue
-    $isCatalogUpdated = $false
-}
-Remove-Variable tmpCatalog
-
-# Copy files and initiate code signing.
-
-$packageContents = "OWLMaker Package Contents"
-Copy-Item -Force -Path $owlMaker64Bit -Destination "$packageContents\"
-if (!$?) { Failure "Failed to copy `"$owlMaker64Bit`"." }
-Write-Host "Copied `"$owlMaker64Bit`"."
-
-Copy-Item -Force -Path $owlMaker32Bit -Destination "$packageContents\32-bit\"
-if (!$?) { Failure "Failed to copy `"$owlMaker32Bit`"." }
-Write-Host "Copied `"$owlMaker32Bit`"."
-
-Start-Process "OWLMaker Package Signing.ksign"
-if (!$?) { Failure "Failed to start kSign." }
-Write-Host -Separator $nl (
-    "Started kSign.",
-    "",
-    "Files have been copied and code signing initiated. Next step is package creation.",
-    ""
-)
-Read-Host -Prompt "Press Enter to continue"
-
-# Perform the package creation in Downloads.
-
-$package = "$env:HOMEPATH\Downloads\$packageFileName"
-Compress-Archive -Force -Path "$packageContents\*" -Destination $package
-if (!$?) { Failure "Failed to create package." }
-Write-Host -Separator $nl (
-    "Created package `"$package`".",
-    "",
-    "Next step is to upload the package and the catalog (if updated).",
-    ""
-)
-Read-Host -Prompt "Press Enter to continue"
-
-# Upload the package and the catalog (if updated).
-
-$packageDestination = "$frsPath/tools"
-Write-Host "Starting package upload to `"$frsHost`:$packageDestination/$packageFileName`"..."
-Set-SCPItem -Credential $credential -ComputerName $frsHost `
-    -Path $package `
-    -Destination $packageDestination
-if (!$?) { Failure "Failed to upload the package." }
-Write-Host "Completed package upload."
-
-if ($isCatalogUpdated) {
-    Write-Host "${nl}Starting catalog upload to `"$frsHost`:$frsPath/$catalogFileName`"..."
-    Set-SCPItem -Credential $credential -ComputerName $frsHost `
-        -Path $catalog `
-        -Destination $frsPath
-    if (!$?) { Failure "Failed to upload the catalog." }
-    Write-Host "Completed catalog upload."
-}
-Remove-Variable credential
-
-# We're done!
-
-Write-Host -Separator $nl (
-    "",
-    "Done. Remember to update the `"Latest Releases`" section on the wiki home page,",
-    "and set the new package as the default download for all operating systems.",
-    "",
-    "Also, you should upload the package to VirusTotal for a comprehensive scan.",
-    "",
-    "Congratulations on the release!",
-    ""
-)
-$shouldDelete = (Read-Host -Prompt "Do you want to delete the local files? [y]es/[N]o").ToUpper().StartsWith("Y")
-if ($shouldDelete) {
-    Remove-Item -Force -Path $package -ErrorAction SilentlyContinue
-    Write-Host "Deleted the package file `"$package`"."
-    Remove-Variable package
-
-    Remove-Item -Force -Path $catalog -ErrorAction SilentlyContinue
-    Write-Host "Deleted the catalog file `"$catalog`"."
-    Remove-Variable catalog
-
-    Write-Host
-    Read-Host -Prompt "Press Enter to close"
-}
-exit 0
-~~~

Contributing modified by Vidar Hasfjord

Vidar Hasfjord — Sun, 22 Feb 2026 23:29:12 -0000

--- v58
+++ v59
@@ -117,7 +117,7 @@

 + **Release**:
 
     1. Do a full build test of all libraries and configurations, ideally with all supported compilers. Make sure OWL_BUILD_DIRTY == 0 in "include/owl/version.h", i.e. that you have no uncommitted changes in the source code. Make sure you test that the documentation builds without errors as well. Ideally, also run test cases ("examples/classes", in particular) to make sure changed parts work as intended and that there are no regressions. 
 
     + Unless the release is an unfinished developer preview (also known as an "alpha" or "beta" pre-release), set the OWL_PRERELEASE flag in "source/owlcore/version.h" to 0.
 
-    + Tag the state of the release branch in the code repository (i.e. create a copy in "[tags](http://sourceforge.net/p/owlnext/code/HEAD/tree/tags). *It can be done by using the Tortoise SVN Branch/Tag command in the root for the branch that is tagged and choosing /tags/VERSION as the destination. Don't forget to specify a commit message*"). See existing tags for the naming convention.
 
+    + Tag the state of the release branch in the code repository (i.e. create a copy in "[tags](http://sourceforge.net/p/owlnext/code/HEAD/tree/tags)", which can be done by using the Tortoise SVN Branch/Tag command in the root for the branch that is tagged and choosing "/tags/{*version tag*}" as the destination). See existing tags for the naming convention. Don't forget to specify a commit message ("Created tag for {*version number*}.").
 
     + Close the relevant tickets and milestones.
 
     + Rebuild the documentation and upload an updated help file (CHM) to "[Files/documentation](http://sourceforge.net/projects/owlnext/files/documentation)". Before you build the documentation, make sure that build setup has been done, so that "include/owl/version.h" exists, and check that OWL_BUILD_DIRTY == 0 (no uncommitted changes). Unless the release is for an older version, update the [online documentation](http://owlnext.sourceforge.net/help/html/index.html) as well (see section "Updating the online documentation" earlier on this page).
 
     + Upload a snapshot of the updated version of the source code to "[Files/source](http://sourceforge.net/projects/owlnext/files/source)". See existing archives for the correct directory structure.

Contributing modified by Ognyan Chernokozhev

Ognyan Chernokozhev — Sun, 22 Feb 2026 21:50:14 -0000

--- v57
+++ v58
@@ -117,7 +117,7 @@

 + **Release**:
 
     1. Do a full build test of all libraries and configurations, ideally with all supported compilers. Make sure OWL_BUILD_DIRTY == 0 in "include/owl/version.h", i.e. that you have no uncommitted changes in the source code. Make sure you test that the documentation builds without errors as well. Ideally, also run test cases ("examples/classes", in particular) to make sure changed parts work as intended and that there are no regressions. 
 
     + Unless the release is an unfinished developer preview (also known as an "alpha" or "beta" pre-release), set the OWL_PRERELEASE flag in "source/owlcore/version.h" to 0.
 
-    + Tag the state of the release branch in the code repository (i.e. create a copy in "[tags](http://sourceforge.net/p/owlnext/code/HEAD/tree/tags)"). See existing tags for the naming convention.
 
+    + Tag the state of the release branch in the code repository (i.e. create a copy in "[tags](http://sourceforge.net/p/owlnext/code/HEAD/tree/tags). *It can be done by using the Tortoise SVN Branch/Tag command in the root for the branch that is tagged and choosing /tags/VERSION as the destination. Don't forget to specify a commit message*"). See existing tags for the naming convention.
 
     + Close the relevant tickets and milestones.
 
     + Rebuild the documentation and upload an updated help file (CHM) to "[Files/documentation](http://sourceforge.net/projects/owlnext/files/documentation)". Before you build the documentation, make sure that build setup has been done, so that "include/owl/version.h" exists, and check that OWL_BUILD_DIRTY == 0 (no uncommitted changes). Unless the release is for an older version, update the [online documentation](http://owlnext.sourceforge.net/help/html/index.html) as well (see section "Updating the online documentation" earlier on this page).
 
     + Upload a snapshot of the updated version of the source code to "[Files/source](http://sourceforge.net/projects/owlnext/files/source)". See existing archives for the correct directory structure.

Contributing modified by Vidar Hasfjord

Vidar Hasfjord — Sat, 14 Feb 2026 03:20:09 -0000

--- v56
+++ v57
@@ -108,8 +108,8 @@

 This section describes the administrative steps you need to perform to prepare and release a new version of OWLNext.

-1. Unless the new version is a minor ABI-compatible update, create a new release branch in the [code repository](http://sourceforge.net/p/owlnext/code) (i.e. create a copy in "[branches/.](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches)"), and set the OWL_PRERELEASE flag in "source/owlcore/version.h" to 1.
 
-+ Update the version number in "source/owlcore/version.h" on the release branch.
 
+1. Unless the new version is a minor ABI-compatible update, create a new release branch in the [code repository](http://sourceforge.net/p/owlnext/code) (i.e. create a copy in "[branches/.](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches)").
 
++ Update the version number in "source/owlcore/version.h" on the release branch, and set the OWL_PRERELEASE flag to 1.
 

 + If applicable, update [OWLMaker](OWLMaker) to recognise the new version and the supported compilers.
 
 + Create new version milestones in the [Bugs](http://sourceforge.net/p/owlnext/bugs/milestones) and [Feature Requests](https://sourceforge.net/p/owlnext/feature-requests/milestones) tracker tools.
 
 + Create and/or target tickets for the version milestones.

Contributing modified by Vidar Hasfjord

Vidar Hasfjord — Wed, 27 Aug 2025 19:34:17 -0000

--- v55
+++ v56
@@ -108,22 +108,22 @@

 This section describes the administrative steps you need to perform to prepare and release a new version of OWLNext.

-1. Unless the new version is a minor ABI-compatible update, create a new release branch in the [code repository](http://sourceforge.net/p/owlnext/code) (i.e. create a copy in "[branches/.](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches)"), and set the OWL_PRERELEASE flag in "source/owlcore/version.h" to 1.
-+ Update the version number in "source/owlcore/version.h" on the release branch.
-+ If applicable, update [OWLMaker](OWLMaker) to recognise the new version and the supported compilers.
-+ Create new version milestones in the [Bugs](http://sourceforge.net/p/owlnext/bugs/milestones) and [Feature Requests](https://sourceforge.net/p/owlnext/feature-requests/milestones) tracker tools.
-+ Create and/or target tickets for the version milestones.
-+ Review the resolutions to the tickets.
-+ Release:
-    1. Do a full build test of all libraries and configurations, ideally with all supported compilers. Make sure OWL_BUILD_DIRTY == 0 in "include/owl/version.h", i.e. that you have no uncommitted changes in the source code. Make sure you test that the documentation builds without errors as well. Ideally, also run test cases ("examples/classes", in particular) to make sure changed parts work as intended and that there are no regressions. 
-    + Unless the release is an unfinished developer preview (also known as an "alpha" or "beta" pre-release), set the OWL_PRERELEASE flag in "source/owlcore/version.h" to 0.
-    + Tag the state of the release branch in the code repository (i.e. create a copy in "[tags](http://sourceforge.net/p/owlnext/code/HEAD/tree/tags)"). See existing tags for the naming convention.
-    + Close the relevant tickets and milestones.
-    + Rebuild the documentation and upload an updated help file (CHM) to "[Files/documentation](http://sourceforge.net/projects/owlnext/files/documentation)". Before you build the documentation, make sure that build setup has been done, so that "include/owl/version.h" exists, and check that OWL_BUILD_DIRTY == 0 (no uncommitted changes). Unless the release is for an older version, update the [online documentation](http://owlnext.sourceforge.net/help/html/index.html) as well (see section "Updating the online documentation" earlier on this page).
-    + Upload a snapshot of the updated version of the source code to "[Files/source](http://sourceforge.net/projects/owlnext/files/source)". See existing archives for the correct directory structure.
-    + If OWLMaker has changed, upload the updated version to "[Files/tools](http://sourceforge.net/projects/owlnext/files/tools)". See the existing archive for the correct contents and directory structure. Ideally, you should digitally sign the executables in the archive (otherwise virus checkers, browsers and operating systems may deem them unsafe). This requires that you have access to a trusted code signing certificate, or that a trusted third-party entity (e.g. a trusted project member) can sign the executables for you. Also make sure that the archive passes virus checking (e.g. at [VirusTotal](http://www.virustotal.com)).
-    + Update the version numbers in "[Files/files-readme.md](http://sourceforge.net/projects/owlnext/files)" (OWLMaker parses this file to check for updates).
-    + Document the release in the wiki page "[OWLNext Releases](OWLNext_Stable_Releases)". If relevant, update wiki pages "[Installing OWLNext](Installing_OWLNext)", "[Supported Compilers](Supported_Compilers)", "[Upgrading from OWL](Upgrading_from_OWL)" (section "Changes in OWLNext"), "[FAQ](Frequently_Asked_Questions)", as well as any other wiki page affected by the changes. Finally, update the wiki [main page](Main_Page), section "Latest releases".
+1. Unless the new version is a minor ABI-compatible update, create a new release branch in the [code repository](http://sourceforge.net/p/owlnext/code) (i.e. create a copy in "[branches/.](http://sourceforge.net/p/owlnext/code/HEAD/tree/branches)"), and set the OWL_PRERELEASE flag in "source/owlcore/version.h" to 1.
 
++ Update the version number in "source/owlcore/version.h" on the release branch.
 
++ If applicable, update [OWLMaker](OWLMaker) to recognise the new version and the supported compilers.
 
++ Create new version milestones in the [Bugs](http://sourceforge.net/p/owlnext/bugs/milestones) and [Feature Requests](https://sourceforge.net/p/owlnext/feature-requests/milestones) tracker tools.
 
++ Create and/or target tickets for the version milestones.
 
++ Review the resolutions to the tickets.
 
++ **Release**:
 
+    1. Do a full build test of all libraries and configurations, ideally with all supported compilers. Make sure OWL_BUILD_DIRTY == 0 in "include/owl/version.h", i.e. that you have no uncommitted changes in the source code. Make sure you test that the documentation builds without errors as well. Ideally, also run test cases ("examples/classes", in particular) to make sure changed parts work as intended and that there are no regressions. 
 
+    + Unless the release is an unfinished developer preview (also known as an "alpha" or "beta" pre-release), set the OWL_PRERELEASE flag in "source/owlcore/version.h" to 0.
 
+    + Tag the state of the release branch in the code repository (i.e. create a copy in "[tags](http://sourceforge.net/p/owlnext/code/HEAD/tree/tags)"). See existing tags for the naming convention.
 
+    + Close the relevant tickets and milestones.
 
+    + Rebuild the documentation and upload an updated help file (CHM) to "[Files/documentation](http://sourceforge.net/projects/owlnext/files/documentation)". Before you build the documentation, make sure that build setup has been done, so that "include/owl/version.h" exists, and check that OWL_BUILD_DIRTY == 0 (no uncommitted changes). Unless the release is for an older version, update the [online documentation](http://owlnext.sourceforge.net/help/html/index.html) as well (see section "Updating the online documentation" earlier on this page).
 
+    + Upload a snapshot of the updated version of the source code to "[Files/source](http://sourceforge.net/projects/owlnext/files/source)". See existing archives for the correct directory structure.
 
+    + If OWLMaker has changed, upload the updated version to "[Files/tools](http://sourceforge.net/projects/owlnext/files/tools)". See the existing archive for the correct contents and directory structure. Ideally, you should digitally sign the executables in the archive (otherwise virus checkers, browsers and operating systems may deem them unsafe). This requires that you have access to a trusted code signing certificate, or that a trusted third-party entity (e.g. a trusted project member) can sign the executables for you. Also make sure that the archive passes virus checking (e.g. at [VirusTotal](http://www.virustotal.com)).
 
+    + Update the version numbers in "[Files/files-readme.md](http://sourceforge.net/projects/owlnext/files)" (OWLMaker parses this file to check for updates).
 
+    + Document the release in the wiki page "[OWLNext Releases](OWLNext_Stable_Releases)". If relevant, update wiki pages "[Installing OWLNext](Installing_OWLNext)", "[Supported Compilers](Supported_Compilers)", "[Upgrading from OWL](Upgrading_from_OWL)" (section "Changes in OWLNext"), "[FAQ](Frequently_Asked_Questions)", as well as any other wiki page affected by the changes. Finally, update the wiki [main page](Main_Page), section "Latest releases".
 
     + Create a [News](http://sourceforge.net/p/owlnext/news) post announcing the release.

Contributing modified by Vidar Hasfjord

Vidar Hasfjord — Fri, 18 Apr 2025 16:31:53 -0000

--- v54
+++ v55
@@ -75,8 +75,10 @@
 RSync is well suited for updating the [Online OWLNext Documentation](http://owlnext.sourceforge.net/help/html/index.html). Assuming that you have the updated documentation files in the local folder "documentation/html", this command updates the online documentation:

 ~~~~
-$ rsync -avsz --delete -e "ssh -l admin" documentation/html admin,owlnext@web.sourceforge.net:/home/project-web/owlnext/htdocs/help/.
-~~~~
+$ rsync -avsz --delete --chmod=D755,F644 -e "ssh -l admin" documentation/html admin,owlnext@web.sourceforge.net:/home/project-web/owlnext/htdocs/help/.
+~~~~
+
+The `--chmod` option makes sure that directories will have full permissions (read, write and execute) for "admin", while only read and execute (browse) permissions for the group and others, and that files will have read and write permissions for "admin", but only read permission for the group and others. For the other options used here, see the [rsync documentation](https://rsync.samba.org/documentation.html).

 

 ### Code repository backup

Contributing modified by Vidar Hasfjord

Vidar Hasfjord — Tue, 05 Nov 2024 12:05:25 -0000

--- v53
+++ v54
@@ -5,6 +5,7 @@
   * Participate in the [forums](https://sourceforge.net/projects/owlnext/forums). 
   * Help us improve the information on this [wiki](Help:Contents). 
   * Submit feature requests, bug reports and patches to the [trackers](Submitting_bugs_and_feature_requests). 
+  * Review our code and documentation.

 If you want to participate as an OWLNext developer or administrator with elevated access rights to the project site, then contact the current administrators by posting in the forum, at the bottom of this page or by email.

@@ -26,8 +27,8 @@
 * Get to know the [code](http://sourceforge.net/p/owlnext/code/HEAD/tree) repository layout and the [Subversion](http://subversion.apache.org) (SVN) version control system. The [TortoiseSVN](http://tortoisesvn.net) client for Windows is highly recommended and has good documentation.
 * Make sure you thoroughly read the guidelines above. Look at the code [log](http://sourceforge.net/p/owlnext/code/HEAD/log/?path=) to get a feel for our style.
 * Learn to use the issue trackers ([Bugs](http://sourceforge.net/p/owlnext/bugs/) and [Feature Requests](http://sourceforge.net/p/owlnext/feature-requests)).
-* Read and contribute to our [Roadmap](OWLNext_Roadmap_and_Prereleases).
-* Read and contribute to the documentation in our [wiki](Main_Page).
+* Review and contribute to our [Roadmap](OWLNext_Roadmap_and_Prereleases).
+* Review and contribute to the documentation in our [wiki](Main_Page).

Contributing modified by Vidar Hasfjord

Vidar Hasfjord — Thu, 31 Oct 2024 18:05:39 -0000

--- v52
+++ v53
@@ -112,8 +112,8 @@
 + Create and/or target tickets for the version milestones.
 + Review the resolutions to the tickets.
 + Release:
-    1. Unless the release is an unfinished developer preview (also known as an "alpha" or "beta" pre-release), set the OWL_PRERELEASE flag in "source/owlcore/version.h" to 0.
-    + Do a full build test of all libraries and configurations, ideally with all supported compilers. Ideally, also run test cases ("examples/classes", in particular) to make sure changed parts work as intended and that there are no regressions. Make sure OWL_BUILD_DIRTY == 0 in "include/owl/version.h", i.e. that you have no uncommitted changes in the source code.
+    1. Do a full build test of all libraries and configurations, ideally with all supported compilers. Make sure OWL_BUILD_DIRTY == 0 in "include/owl/version.h", i.e. that you have no uncommitted changes in the source code. Make sure you test that the documentation builds without errors as well. Ideally, also run test cases ("examples/classes", in particular) to make sure changed parts work as intended and that there are no regressions. 
+    + Unless the release is an unfinished developer preview (also known as an "alpha" or "beta" pre-release), set the OWL_PRERELEASE flag in "source/owlcore/version.h" to 0.
     + Tag the state of the release branch in the code repository (i.e. create a copy in "[tags](http://sourceforge.net/p/owlnext/code/HEAD/tree/tags)"). See existing tags for the naming convention.
     + Close the relevant tickets and milestones.
     + Rebuild the documentation and upload an updated help file (CHM) to "[Files/documentation](http://sourceforge.net/projects/owlnext/files/documentation)". Before you build the documentation, make sure that build setup has been done, so that "include/owl/version.h" exists, and check that OWL_BUILD_DIRTY == 0 (no uncommitted changes). Unless the release is for an older version, update the [online documentation](http://owlnext.sourceforge.net/help/html/index.html) as well (see section "Updating the online documentation" earlier on this page).

Contributing modified by Vidar Hasfjord

Vidar Hasfjord — Thu, 26 Sep 2024 11:41:25 -0000

--- v51
+++ v52
@@ -1,4 +1,4 @@
-# Contributing to the OWLNext Project
+# Contributing to the OWLNext project

 Here are some ways you can contribute: 

@@ -125,7 +125,7 @@

 


-### OWLMaker Release Script
+### OWLMaker release script

 The following PowerShell script can be used to automate the release of a new version of OWLMaker.

Contributing modified by Vidar Hasfjord

Vidar Hasfjord — Mon, 23 Sep 2024 13:39:53 -0000

--- v50
+++ v51
@@ -96,7 +96,7 @@
 

 ### References

-* http://software.ac.uk/resources/guides/creating-and-managing-sourceforge-projects
+* https://www.software.ac.uk/guide/how-create-and-manage-sourceforge-projects