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.

Remove redundant repository branches

See original GitHub issue

ControlsFX repository has the following branches:

master - previous default branch, used for Java 8 development
9.0.0 - Forked out of master, contains changes for JDK 9 and later
jfx-13 - Current default branch. Forked out of 9.0.0 branch and contains changes for JDK 11 and later
revert-1139-patch-1 - Stale branch

Since all development and bug fix effort is targeted on jfx-13, my proposal is to:

Remove all branches except jfx-13
Rename jfx-13 to something generic: master or main
All tags will remains intact

This issue is to gather community feedback and keep track of the progress.

@Maxoudela @eugener your feedback is appreciated.

Issue Analytics

State:
Created 3 years ago
Reactions:3
Comments:9 (4 by maintainers)

Top GitHub Comments

1reaction

Maxoudelacommented, Feb 28, 2021

That sounds good.

I have no opinion on the Github flow versus GitFlow. Maybe a bit in favor of having only master, especially if we are already following it and our release process is already up to date.

Thanks a lot @abhinayagarwal for all the effort and the time you take to maintain this project. Kudos !

0reactions

abhinayagarwalcommented, Feb 28, 2021

Protected branches is definitely a strong advantage and keeps production branches away from unwanted changes. However, I am biased towards the TAG approach as the release automation is already running based on TAGs 😇

I will start working on this issue by removing the branches and renaming jfx-13 to master. This will most probably break the local repositories for everyone. I apologize in advance for this.