We have some old branches:
2012-05-09 refs/remotes/origin/jena-owl2
2013-01-31 refs/remotes/origin/streaming-update
2015-04-22 refs/remotes/origin/JENA-380
2015-05-22 refs/remotes/origin/add-contract-tests
2015-07-08 refs/remotes/origin/jena2
2015-08-06 refs/remotes/origin/jena-text-cache
2016-01-28 refs/remotes/origin/JENA-507
2017-01-11 refs/remotes/origin/ThreadPerGraphDataset
+ master and HEAD.
where the date is the latest commit.
(that's from
git for-each-ref \
--sort='committerdate:short' \
--format=' %(committerdate:short)%09%(refname)' \
refs/remotes
and help from StackOverflow).
All but "jena2" and "ThreadPerGraphDataset" look like they can be deleted.
---- Investigation
"jena-owl2" - has no activity.
It probably creates a false impression - better to delete it.
"streaming-update"
Refers to JENA-330 which is closed.
The branch can be deleted.
"JENA-380" - "Migrate core tests to junit4"
This is done.
The branch can be deleted.
We need to close the JIRA.
"add-contract-tests"
This is done.
The branch can be deleted.
Jena2 ends at branch "jena2" 2015-07-08 (with release 2015-07-29) so
everything before is very out of date.
"jena-text-cache"
Refers to JENA-999 which is closed so this looks like it is finished with.
The branch can be deleted.
"JENA-507"
"Add support for Leviathan extension functions to ARQ"
This is done. The branch can be deleted.
Close JIRA.
"ThreadPerGraphDataset"
Recent.
--------------------
That leaves:
2015-07-08 refs/remotes/origin/jena2
2017-01-11 refs/remotes/origin/ThreadPerGraphDataset
2017-02-12 refs/remotes/origin/HEAD
2017-02-12 refs/remotes/origin/master
We have tools - github, clones and pull requests - that make discussion
and review easier. For example, a PR gives a cumulative view of all
commits as well as all commits.
Nowadays, I think it is better to develop new capabilities through
clones and dynamic PRs and better to keep the main code repository as
focused on the main line of development so I propose deleting branches
and closing JIRA as noted above.
Comments?
Andy
