Potentially unused branches
camillobruni opened this issue · 5 comments
Seems like there are a couple of branches in this main repo that either look like experiments or stale.
Would it make sense to clean those up and only have dedicated branches?
main=> current development branchexperimental=> main + future / experimental workloadsv2.1=> what is currentlyspeedometer2.1-contentv3.0=> "stable" / released version 3, once we're there
Makes sense to me
v2.1=> what is currentlyspeedometer2.1-content
This isn't quite right. This branch isn't pure 2.1 but rather 2.1 benchmark content adopted to 3's test runner so it's hybrid of the two.
This isn't quite right. This branch isn't pure 2.1 but rather 2.1 benchmark content adopted to 3's test runner so it's hybrid of the two.
Good call, that should stay as-is
The terminology 'future' could cause a bit of confusion here. It seems like future content kind of is tentative. So it seems to me like the experimental branch is just that, experimental content, and tentative content (i.e. potential future content) goes into the Main branch.
I think we can close this after discussing in last week's meeting. We're agreed on the proposal in @camillobruni's comment, with the clarification for experimental not being "future". @rniwa deleted the unused branches so we now have main and speedometer2.1-content. Once we have content for it we can push it into the experimental branch.