The software is finished -- and by finished, we mean there are no show-stopping, little-children-killing bugs in it. That we know of. There are probably numerous lower-priority bugs triaged into the next point release or service pack, as well.
@@ -9,13 +9,13 @@ More information about `dotnet new` can be found at <https://docs.microsoft.com/
Once the .NET Core SDK has been installed, type the following command to install the templates for creating Orchard Core web applications:
```CMD
dotnet new install OrchardCore.ProjectTemplates::1.6.0
dotnet new install OrchardCore.ProjectTemplates::1.7.0
```
This will use the most stable release of Orchard Core. In order to use the latest `main` branch of Orchard Core, the following command can be used:
```CMD
dotnet new install OrchardCore.ProjectTemplates::1.6.0-* --nuget-source https://nuget.cloudsmith.io/orchardcore/preview/v3/index.json
dotnet new install OrchardCore.ProjectTemplates::1.7.0-* --nuget-source https://nuget.cloudsmith.io/orchardcore/preview/v3/index.json
```
## Create a new website
...
...
@@ -25,7 +25,7 @@ dotnet new install OrchardCore.ProjectTemplates::1.6.0-* --nuget-source https://
#### Generate an Orchard Cms Web Application
!!! warning
Due to a bug in the current published version, the following `dotnet new` commands will require the extra argument `--orchard-version 1.6.0`. For instance, instead of typing `dotnet new occms` use `dotnet new occms --orchard-version 1.6.0`
Due to a bug in the current published version, the following `dotnet new` commands will require the extra argument `--orchard-version 1.7.0`. For instance, instead of typing `dotnet new occms` use `dotnet new occms --orchard-version 1.7.0`
```CMD
dotnet new occms
...
...
@@ -47,7 +47,7 @@ Options:
-ov|--orchard-version Specifies which version of Orchard Core packages to use.
string - Optional
Default: 1.6.0
Default: 1.7.0
```
Logging can be ignored with this command:
...
...
@@ -134,7 +134,7 @@ Options:
-ov|--orchard-version Specifies which version of Orchard Core packages to use.
@@ -18,7 +18,7 @@ There are different ways to create sites and modules for Orchard Core. You can l
In this guide we will use our [Code Generation Templates](../../getting-started/templates/). You can install the latest stable release of the templates using this command:
```dotnet new install OrchardCore.ProjectTemplates::1.6.0-*```
```dotnet new install OrchardCore.ProjectTemplates::1.7.0-*```
!!! note
To use the development branch of the template add `--nuget-source https://nuget.cloudsmith.io/orchardcore/preview/v3/index.json`
@@ -24,7 +24,8 @@ Do some housekeeping on GitHub in the [main repo](https://github.com/OrchardCMS/
Update the source so everything looks like on the new version.
- [ ] Create a `release/<version name>` branch out of `main`, e.g. `release/1.3.1`.
- [ ] Create a `release/<version name>` branch out of `main`, e.g. `release/1.8`.
-[ ] Check the [release_ci](https://github.com/OrchardCMS/OrchardCore/blob/main/.github/workflows/release_ci.yml) workflow is using the expected .NET version to build the Docker images.
- [ ] Update the `OrchardCore.Commons.props` file with `<VersionSuffix></VersionSuffix>` such that preview build numbers are not injected in packages. Verify the `VersionPrefix` tag matches the released version.
- [ ] Update module versions in `src/OrchardCore/OrchardCore.Abstractions/Modules/Manifest/ManifestConstants.cs`.
- [ ] Update the version in the command lines in from all documentation files.
...
...
@@ -87,6 +88,7 @@ Let the whole world know about our shiny new release. Savor this part! These ste
### After the release is done
- [ ] Create a new milestone with the next release number.
- [ ] Create a new release notes documentation file for the next version in the OrchardCore.Docs project. (e.g, `/releases/1.8.0.md`).
- [ ] Update the `OrchardCore.Commons.props` file with the next release number, and `<VersionSuffix>preview</VersionSuffix>` such that preview builds use the new one.
