Skip to content
This repository has been archived by the owner on Jan 31, 2022. It is now read-only.

Branches divergencies #303

Open
lpetre-ulb opened this issue Apr 14, 2020 · 1 comment
Open

Branches divergencies #303

lpetre-ulb opened this issue Apr 14, 2020 · 1 comment
Assignees

Comments

@lpetre-ulb
Copy link
Contributor

lpetre-ulb commented Apr 14, 2020

Brief summary of issue

During the branches clean-up, I noticed that several more or less active branches have diverged. Compared to release/legacy (previously rpc-playground), develop and master have diverged. It must be noted that bug fixes seem to have been applied to both develop and master.

Since those two branches are not expected to be maintained and haven't seen new commits in years, one may want to simply delete them without further consideration. I would however prefer to first check that nothing is going to be lost. Said otherwise, that no bug fix or feature is lost.

Does any developer knows if it is safe from the bug fix or feature point of view to delete develop and master?

@jsturdy
Copy link
Contributor

jsturdy commented Apr 30, 2020

If there are no plans to migrate or support the code of this repository moving forward (which is what I have understood from statements made at various meetings), what is the point of this issue?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants