Fossil SCM
Updates to the "aboutdownload" documentation page.
Commit
f5d1c5e0f9125a974b91f79b3bbd66ba79a7044ae3b6b729736c50da9c5d3547
Parent
452f8e1ffc99c60…
1 file changed
+2
-2
+2
-2
| --- www/aboutdownload.wiki | ||
| +++ www/aboutdownload.wiki | ||
| @@ -47,11 +47,11 @@ | ||
| 47 | 47 | <verbatim><div class='fossil-doc' data-title='Download Page'>...</div></verbatim> |
| 48 | 48 | |
| 49 | 49 | Fossil knows to add its standard header and footer information to the |
| 50 | 50 | document, making it look just like any other page. See |
| 51 | 51 | "[./embeddeddoc.wiki|embedded documentation]" for further details on |
| 52 | -how <div class='fossil-doc'> this works. | |
| 52 | +how this <div class='fossil-doc'> markup works. | |
| 53 | 53 | |
| 54 | 54 | With each new release, the "releases" variable in the javascript on |
| 55 | 55 | the [/uv/download.js?mimetype=text/plain|download.js] page is |
| 56 | 56 | edited (using "[/help?cmd=uv|fossil uv edit download.js]") to add |
| 57 | 57 | details of the release. |
| @@ -62,11 +62,11 @@ | ||
| 62 | 62 | constructed by matching unversioned files against regular expressions |
| 63 | 63 | in the "releases" variable. |
| 64 | 64 | |
| 65 | 65 | Build products need to be constructed on different machines. The precompiled |
| 66 | 66 | binary for Linux is compiled on Linux, the precompiled binary for Windows |
| 67 | -is compiled on Windows10, and so forth. After a new release is tagged, | |
| 67 | +is compiled on Windows11, and so forth. After a new release is tagged, | |
| 68 | 68 | the release manager goes around to each of the target platforms, checks |
| 69 | 69 | out the release and compiles it, then runs |
| 70 | 70 | [/help?cmd=uv|fossil uv add] for the build product followed by |
| 71 | 71 | [/help?cmd=uv|fossil uv sync] to push the new build product to the |
| 72 | 72 | [./selfhost.wiki|various servers]. This process is repeated for |
| 73 | 73 |
| --- www/aboutdownload.wiki | |
| +++ www/aboutdownload.wiki | |
| @@ -47,11 +47,11 @@ | |
| 47 | <verbatim><div class='fossil-doc' data-title='Download Page'>...</div></verbatim> |
| 48 | |
| 49 | Fossil knows to add its standard header and footer information to the |
| 50 | document, making it look just like any other page. See |
| 51 | "[./embeddeddoc.wiki|embedded documentation]" for further details on |
| 52 | how <div class='fossil-doc'> this works. |
| 53 | |
| 54 | With each new release, the "releases" variable in the javascript on |
| 55 | the [/uv/download.js?mimetype=text/plain|download.js] page is |
| 56 | edited (using "[/help?cmd=uv|fossil uv edit download.js]") to add |
| 57 | details of the release. |
| @@ -62,11 +62,11 @@ | |
| 62 | constructed by matching unversioned files against regular expressions |
| 63 | in the "releases" variable. |
| 64 | |
| 65 | Build products need to be constructed on different machines. The precompiled |
| 66 | binary for Linux is compiled on Linux, the precompiled binary for Windows |
| 67 | is compiled on Windows10, and so forth. After a new release is tagged, |
| 68 | the release manager goes around to each of the target platforms, checks |
| 69 | out the release and compiles it, then runs |
| 70 | [/help?cmd=uv|fossil uv add] for the build product followed by |
| 71 | [/help?cmd=uv|fossil uv sync] to push the new build product to the |
| 72 | [./selfhost.wiki|various servers]. This process is repeated for |
| 73 |
| --- www/aboutdownload.wiki | |
| +++ www/aboutdownload.wiki | |
| @@ -47,11 +47,11 @@ | |
| 47 | <verbatim><div class='fossil-doc' data-title='Download Page'>...</div></verbatim> |
| 48 | |
| 49 | Fossil knows to add its standard header and footer information to the |
| 50 | document, making it look just like any other page. See |
| 51 | "[./embeddeddoc.wiki|embedded documentation]" for further details on |
| 52 | how this <div class='fossil-doc'> markup works. |
| 53 | |
| 54 | With each new release, the "releases" variable in the javascript on |
| 55 | the [/uv/download.js?mimetype=text/plain|download.js] page is |
| 56 | edited (using "[/help?cmd=uv|fossil uv edit download.js]") to add |
| 57 | details of the release. |
| @@ -62,11 +62,11 @@ | |
| 62 | constructed by matching unversioned files against regular expressions |
| 63 | in the "releases" variable. |
| 64 | |
| 65 | Build products need to be constructed on different machines. The precompiled |
| 66 | binary for Linux is compiled on Linux, the precompiled binary for Windows |
| 67 | is compiled on Windows11, and so forth. After a new release is tagged, |
| 68 | the release manager goes around to each of the target platforms, checks |
| 69 | out the release and compiles it, then runs |
| 70 | [/help?cmd=uv|fossil uv add] for the build product followed by |
| 71 | [/help?cmd=uv|fossil uv sync] to push the new build product to the |
| 72 | [./selfhost.wiki|various servers]. This process is repeated for |
| 73 |