search

OpenHospitalityNetwork / fedi-trustroots

Next generation federated hospitality exchange platform
https://openHospitality.network
GNU Affero General Public License v3.0
23 stars 3 forks source link

Problem: Project shall have one branch, master, and no topic branches #45

Open weex opened 3 years ago

weex commented 3 years ago

Since this was forked from upstream, we haven't removed all the extra branches but quoting C4:

2.5. Branches and Releases

  1. The project SHALL have one branch ("master") that always holds the latest in-progress version and SHOULD always build.
  2. The project SHALL NOT use topic branches for any reason. Personal forks MAY use topic branches.
weex commented 3 years ago

Removed almost all branches. Only ones left are @mariha's update_nr_of_members and @chagai95 changing-trustroots-strings

Any objection to removing these branches?

Like all of the other branches, they'll exist in your local copy until you delete them there and they can always be pushed back to the repo, though it'd be preferable for topic branches only to exist in individual contributor repos. The only legit reason I've found to keep a branch is if a PR has been made to upstream based on it.

chagai95 commented 3 years ago

I was planning to remove that branch anyway, so if you get there before me, thx!