question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Change branch/versioning system

See original GitHub issue

Right now we use Git Flow.

  1. main always represents the most recent release of v1
  2. develop is the v1 working branch
  3. v2_develop is the v2 working branch
  4. There is no main for v2
  5. the .csproj files do not contain real version information
  6. 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:open
  • Created a month ago
  • Comments:5

github_iconTop GitHub Comments

1reaction
tigcommented, Aug 17, 2023

I’ve renamed the branches. Not sure this is going to work, but I gotta keep trying…

  • v1 - was main
  • v1_develop - was develop
  • v2 - new (v2 release)
  • v2_develop - was v2_develop

Sorry for any trouble this causes as I do this.

1reaction
tigcommented, Aug 17, 2023

Ok…

develop now publishes on push using 1.14.0-pre.146

I’m backing away from using next-version: in gitversion.yml. Instead, we will use tags.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found