Change branch/versioning system
See original GitHub issueRight now we use Git Flow.
main
always represents the most recent release ofv1
develop
is thev1
working branchv2_develop
is thev2
working branch- There is no
main
forv2
- the .csproj files do not contain real version information
- We don’t effectively used “pre-release” semver
4 and 5 are problematic for maintaining multiple versions of T.Gui over time (v1 and v2 etc…).
6 makes it hard to determine what version of T.Gui is in use when doing local dev.
Here’s my thoughts on addressing this. I’ve spent a bunch of time digging into this, but am still quite confused anď unclear on the right approach. This Issue is my attempt to write it all down to drive more clear thinking. Help appreciated.
Issue Analytics
- State:
- Created a month ago
- Comments:5
Top Results From Across the Web
Branch version scenarios—ArcGIS Pro | Documentation
Branch versioning has a simplified version hierarchy that allows only one level of named versions to be created from the default branch version....
Read more >- An Introduction to Branch Versioning
Branch versioning is a new platform for multiuser editing that leverages the services-based ... It tracks changes made to a database.
Read more >A New Branch on the Versioning Tree: An Overview of ...
Branch versioning is a new type of geodatabase versioning available to Esri users. This new type of versioning has been reconfigured to ...
Read more >[ArcGIS Enterprise] Has anyone switched to branch ...
If you have traditional versioned data you want to switch to branch, you have to unregister your traditional versioned data, then re-register as ......
Read more >Branch Versioning—What is it and How Does it Work?
Registering as Versioned. It all starts here. Instead of the Adds/Deletes tables that Traditional Versioning creates for every feature class you ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve renamed the branches. Not sure this is going to work, but I gotta keep trying…
v1
- wasmain
v1_develop
- wasdevelop
v2
- new (v2 release)v2_develop
- wasv2_develop
Sorry for any trouble this causes as I do this.
Ok…
develop
now publishes onpush
using1.14.0-pre.146
I’m backing away from using
next-version:
in gitversion.yml. Instead, we will use tags.