Dear Wiki user, You have subscribed to a wiki page or wiki category on "Subversion Wiki" for change notification.
The "Berlin2013" page has been changed by brane: https://wiki.apache.org/subversion/Berlin2013?action=diff&rev1=4&rev2=5 * Are we aiming for a 9 month or rather a 18 month project? * Process changes so we can avoid incomplete features from blocking a release? * Non-binding improvement / feature wish list + * Merge * Do we need a new data model? How would that look like? * What needs to be done for move support? * In what aspects can the current merge algorithms / infrastructure be improved besides adding move support? (What problems are users still experiencing unrelated to moves?) * Refactoring our 500+kB merge.c? + * Branch cleanup * Which of the existing branches are obsolete and can be removed? + * FSFS format 7 * Goals and feature overview is given as a WebEx talk on Wednesday * Technical discussion needs to be separate from that * People's feature wish list * How to get that into /trunk? This includes organizing a review of the refactoring and improvements for f6. f7 features can be disabled (similar to what we do with Ev2 right now). + * Shared repository cache * A.k.a. "cache server". What it is and why it's useful. + * Coding Standards * GCC recently allowed C++ for its own code. What is the general opinion amongst SVN devs toways doing the same? * Parameter checking to avoid NULL values causing security bugs? + * Pipelining the client * This seems to be the only available option to make the client scale better for large projects. Is that approach feasible for a 1.10+ timeframe and what would it take? + * Benchmarking * How could a systematic scalability and performance test for SVN look like? + * Tests * Should coverage reports be part of our CI builds? * Do we want to improve coverage? If so, where and when? + * Bindings - * CXXHL leading to a consistent binding interface between languages? + * C++HL leading to a consistent binding interface between languages? + * JavaHL native implementation eventually replaced by C++HL? + * Developer Community * How can we attract more contributors? + * User work flow improvement * Ways we can make users lives easier (auto pager, stash, built-in bisect, interactive commit, patch submission automation). + * Versioned Object Model Improvements (Blue-Sky) + * Metadata indexing (''have slides about directory index --brane'') + * Almost-first-class branches + * Tracking and non-tracking links + == Discussion Notes ==
