Skip to content

Commit 52ac86a

Browse files
committed
Developer documentation
Added DEVELOPMENT.md. Yet it has only info about how to create a release of the sink.
1 parent f0d79cc commit 52ac86a

File tree

2 files changed

+24
-0
lines changed

2 files changed

+24
-0
lines changed

DEVELOPMENT.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Creating Releases
2+
3+
## Creating a Pre-release (-dev suffix)
4+
5+
Whenever the `dev` branch is updated (after merging a pull request), the `Release` action is triggered. This action builds a nuget package with a prerelease identifier of the format `-dev-nnnnn` appended to the version number. This package is automatically published on nuget.org.
6+
7+
## Creating a latest Release
8+
9+
### Normal Update (no major version change) {#normal-update}
10+
11+
1. On the `dev` branch, update CHANGES.md and `VersionPrefix` in Serilog.Sinks.MSSqlServer.csproj.
12+
13+
1. Create a PR to merge the `dev` branch into `main`. The `Release` action will be triggered. This action builds a nuget package and publishes it on nuget.org. Additionally a release is created in the GitHub repo. The release summary will be taken from the description of the PR, so best thing is to put something similar to the version summary in CHANGES.md in there.
14+
15+
1. After the release is done, increase the patch version number in `VersionPrefix` in Serilog.Sinks.MSSqlServer.csproj on the `dev` branch. This ensures that the next dev release will have a higher version number than the latest release.
16+
17+
### Major Release (major version change)
18+
19+
1. On the `dev` branch, update CHANGES.md and increase the major version in `VersionPrefix` in Serilog.Sinks.MSSqlServer.csproj. Also set `EnablePackageValidation` to false because on an intial release of a new major version you don't have a baseline version yet on nuget.org to compare with.
20+
21+
1. Create a PR to merge the `dev` branch into `main`. The `Release` action will be triggered. This works the same as described above under [Normal Update]({#normal-update).
22+
23+
1. After the release is done make some changes in Serilog.Sinks.MSSqlServer.csproj on the `dev` branch. Set `EnablePackageValidation` back to true and `PackageValidationBaselineVersion` to the version of the new major release you just created (e.g. 7.0.0). Then also increase the patch version number in `VersionPrefix` (e.g. 7.0.1).

serilog-sinks-mssqlserver.sln

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution
2424
.editorconfig = .editorconfig
2525
Build.ps1 = Build.ps1
2626
CHANGES.md = CHANGES.md
27+
DEVELOPMENT.md = DEVELOPMENT.md
2728
Directory.Build.props = Directory.Build.props
2829
Directory.Packages.props = Directory.Packages.props
2930
.github\ISSUE_TEMPLATE.md = .github\ISSUE_TEMPLATE.md

0 commit comments

Comments
 (0)