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 branching scheme, again.

See original GitHub issue

Hopefully for the last time.

Current:

master: development
android11: stable, translations
android10, android9: old version-specific branches
tags: stable

Proposed:

android12: development, translations
android11, android10, android9: old version-specific branches
tags: stable

I am proposing to do away with the master branch, and directly develop on android12

We’ve started tagging releases so anybody who wants something stable can use those, and others can keep using the branch.

It’ll avoid confusion and also make handling translations easier.

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

grotecommented, Aug 25, 2021

Nothing in particular really, just that they used to be previous stable branches I guess?

ok, because I think the version number of the tag should already make clear what android version it is for and every tag is stable, so I think we don’t need to introduce stable/oldstable terminology

0reactions

chirayudesaicommented, Apr 26, 2022

@chirayudesai Is that list above up to date? Or can we close this ticket?

Yep!

Top Results From Across the Web

Basic Branching and Merging - Git SCM

Create a branch to add the hotfix. After it's tested, merge the hotfix branch, and push to production. Switch back to your original...

The Best Branching Strategies For High-Velocity Development

Branching strategies help manage changes and code integrations across teams. ... And as files are modified, teams can merge back changes.

Git Branching and Merging: A Step-By-Step Guide - Varonis

Merging takes your branch changes and implements them into the main branch. Depending on the commit history, Git performs merges two ways: fast ......

Adopt a Git branching strategy - Azure Repos - Microsoft Learn

Use release branches to coordinate and stabilize changes in a release of your code. This branch is long-lived and isn't merged back into...

Git Branching Strategies: GitFlow, Github Flow, Trunk Based...

Developers will first need to create the release branch then make sure any final work is also merged back into the development branch...