Default and stale branches

[davelab6]

It seems there is recent activity on this project, but not in the default branch; and there are many merged/stale branches that could be pruned (easily with the github UI :)

[dalehenrich]

@davelab6m yes a number of the branches on this project need some loving attention, but the project is currently in a stable state with @ThierryGoubier doing the bulk of his work in support of Pharo5.0 and I am busy on other projects at the moment ...

[davelab6]

By stale I don't mean in need of more work; I mean, in need of deletion :) Is the "gemstone2.4" branch really the 'default' one?

[dalehenrich]

I understood that, but there are a number of platform branches that may appear to be stale, but aren't because there are multiple "primary" branches in this project and the github api doesn't make them obvious ... so the work involved is thinking about each branch before clicking the button ... and to me that is "work" that is not at the top of my priority list ...

Dale

On 04/21/2016 05:43 AM, Dave Crossland wrote:

By stale I don't mean in need of more work; I mean, in need of deletion :) Is the "gemstone2.4" branch really the 'default' one?

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/dalehenrich/filetree/issues/189#issuecomment-212901885

[dalehenrich]

well I've deleted the stale branches that were no brainers :)