-
Notifications
You must be signed in to change notification settings - Fork 34
/
How to release.txt
49 lines (46 loc) · 1.58 KB
/
How to release.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
Pre-conditions:
---------------
- Build environment is green
- No FIXME or NotImplementedException left in source code
- All versions are up-to-date:
- MigSharp\MigSharp.csproj
- see "Assembly version" and "Assembly file version" under Properties > Package
- Migrate\AssemblyInfo.cs
- Generate\AssemblyInfo.cs
- Release Notes are up-to-date
- All changes synched and pushed to GitHub
- Wiki on GitHub reflects new features and changes
Releasing:
----------
- Build the NuGet on TC: adjust /p:PackageVersion=1.0.0 paremter of "dotnet pack" step
- On GitHub: tag the sources with AssemblyVersion
git tag -a v1.0.0 -m "v1.0.0"
git push origin v1.0.0
- Grab the MigSharp.1.0.0.nupkg from TC artifacts and go to https://www.nuget.org/packages/manage/upload
- Verify upload was okay. The content should be:
lib/
netstandard2.0/
MigSharp.dll
MigSharp.xml
Post-actions:
-------------
- Increment AssemblyVersion (see above)
- TC: adjust /p:PackageVersion=1.0.1-beta1 paremter of "dotnet pack" step
- Announce
- Close all issues related to the released milestone and close milestone
To branch a release for patches:
--------------------------------
- Use the tag to branch off a release branch for patches:
git checkout -b RB-1.0 v1.0.0
- Publish the branch:
git push origin RB-1.0
- Switch back to master:
git checkout master
- Delete the local RB-1.0 branch:
git branch -d RB-1.0
- Fetch the remote:
git fetch
- Start tracking the new remote branch:
git checkout --track origin/RB-1.0
- Merge bug-fixes from the master:
git cherry-pick -n 07f42ff9379d99869048ee61264fbdf732ff6b8a