Repository navigation
Mainline development mode - #950
Conversation
|
The branching strategy images still contain |
| [assembly: AssemblyProduct("GitVersion")] | ||
| [assembly: AssemblyVersion("1.0.0")] | ||
| [assembly: AssemblyFileVersion("1.0.0")] | ||
| [assembly: AssemblyVersion("4.0.0.0")] |
There was a problem hiding this comment.
Isn't this set through GitVersion in the build process and should be kept to 1.0.0 in the repo?
There was a problem hiding this comment.
Ran build script locally, forgot to reset these changes
|
We should also make sure to document the new mainline mode properly. There is already a mainline documentation available which should be updated with these changes. |
cba2bf7 to
defc31b
Compare
| As such we force a pre-release tag on all branches, this is fine for applications but can cause problems for libraries. As such this mode may or may not work for you, which leads us into a new mode in v4. Mainline development. | ||
|
|
||
| ## Mainline development | ||
| Mainline development works more like the Continuous Delivery mode, except that it tells GitVersion to *infer* releases from from event. |
|
I did a local build and tried it out, worked great and as expected during my quick testing. My 🍠 I did get two test failures though when running build.ps1: |
This builds on top of #832
It's pretty rough but will ship this as part of 4.0.0 beta if it looks ok