We've branched 1.6.x: yay! While it's soaking, and tion for the 1.7
release cycle, I'd like to take a look at all the current branches in
our tree, find out what's mergable and what's not, and then take
appropriate action. Here's the list of the outstanding branches in
No work for two years.
No work for three years.
Branch created by Karl a year ago, only one commit.
"micro-branch" created by Neels four months ago.
Branch to maintain an EBCDIC port of Subversion. Last action
by Paul Burba 2 year ago.
Active branch worked on by Greg and Hyrum. Lots of tests currently
broken, but Greg is selectively merging stuff back to trunk.
Hope to merge the branch back to trunk in the next week or so.
No work for years.
No work over the past year.
Active branch being worked on by C-Mike and Ben. Anticipated
merge to trunk in the next few days?
Branch created by Hyrum to for some svn:mergeinfo user interface
improvements. Not being actively developed.
3-month-old branch created by Stefan Sperling to "handle dual-stack
IPv4/IPv6 servers in svnserve."
Created 2 years ago by C-Mike, with some work done by Dan Rall.
Purpose: "for adding support for all-or-nothing multi-path locks."
Created by Kamesh over a year ago, not actively being developed.
Second attempt at the above, with some activity 3 months ago.
No work for over a year.
No work for 3 years.
Started by Erik, no work for 10 months.
No work in over 16 months.
Active development by Arfrever.
Active development by Leiven.
Over year old, managed by Kamesh.
Five months old, managed by Paul.
Abortive Summer of Code 2007 project.
2-year-old branch created by Dave Anderson, only a couple of
3 years old, not actively developed.
Patch-stash branch created by Eric, over a year ago.
Summer of Code 2007 project. Can this go into 1.7?
Tree-conflicts-related branch, managed by Julian.
Over 1 year old, managed by C-Mike.
I think a number of these are doomed for the bit bucket, but a few
could be merged for 1.7. Thoughts?
Received on 2009-02-16 23:59:57 CET