This was extracted (@ 2024-03-20 21:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Project Status: Current project status: Ongoing, mature. Issues for the board: None at this time. ## Membership Data: Apache Subversion was founded 2010-02-16 (14 years ago). Prior to joining ASF, the project began in February of 2000 (24 years ago). There are currently 87 committers, of which 48 are PMC members, in the project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - One new PMC member: Vincent Lefevre joined the PMC on 2024-01-23. - One new committer: Same. ## Project Activity: Apache Subversion 1.14.3 was released on 29 December 2023. This is the latest bugfix release on the 1.14.x Long Term Support (LTS) release line. The release announcement is archived here: https://lists.apache.org/thread/gcbmxzyssxk4693c7lcwv8yp1lfhsg7g In addition, the Subversion PMC is happy to welcome Vincent Lefevre as its newest member. Discussions regarding the next release line, 1.15, have been taking place gradually. This new release line will bring two major new features: Pristines On Demand and Streamy Checkouts. Currently there is one unresolved question regarding whether (and, if so, how) to change the hash codes used to check for file modification in local working copies. ## Community Health: The community is healthy for a mature and stable project: This quarter, a new patch release was made and a new PMC member was added. There are steady contributions to the codebase, website, documentation, backports, and other areas. Issues are being triaged and addressed. Development questions are being debated. User questions usually receive helpful responses. Our community is fully volunteer-driven and we would like to thank everyone for their support.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Project Status: Current project status: Ongoing, mature. Issues for the board: None at this time. ## Membership Data: Apache Subversion was founded 2010-02-16 (13 years ago). Prior to joining ASF, the project began in 2000 (23 years ago). There are currently 86 committers and 47 PMC members in the project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Daniel Sahlberg on 2021-08-02. - No new committers. Last addition was Daniel Sahlberg on 2020-12-14. ## Project Activity: This quarter's activities were mainly related to ongoing maintenance and improvements. Discussion of the upcoming 1.14.3 release is taking place. There is a volunteer for release manager, for whom this will be the first time managing a release. The main challenge for a first-time release manager is getting the environment setup with the necessary clean dependencies. This is currently taking place and the actual release management process is expected to take place this month. ## Community Health: The community is healthy for a mature and stable project. Maintenance is ongoing. There are steady contributions to the codebase, website, documentation, backports, and other areas. User questions at our mailing lists and IRC channels have been receiving helpful responses. Our community is fully volunteer-driven and we would like to thank everyone for their support.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Project Status: Current project status: Mature with ongoing maintenance. New features coming in the next major release (1.15.0) include Pristines-On-Demand and Streamy Checkouts. Issues for the board: None at this time. The issue mentioned in our May 2023 report has been resolved; VP Legal has replied to our question. ## Membership Data: Apache Subversion was founded 2010-02-16 (13.5 years ago). There are currently 86 committers and 47 PMC members in the project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Daniel Sahlberg on 2021-08-02. - No new committers. Last addition was Daniel Sahlberg on 2020-12-14. ## Project Activity: Prior reports discussed the new Pristines-On-Demand feature, expected to be released in Subversion 1.15.0. When in use, this optional feature can reduce by up to half the amount of disk space occupied by a Subversion working copy. It accomplishes this by not keeping a local cache of unchanged "Pristine" copies of all the files. The savings can be significant when the files are very large or when there is a very large number of files. To exercise this new feature, I have been using a build of trunk with this feature activated as my "daily driver" Subversion client for some time now. The results have been excellent: at least in my own workflows, my experience has been smooth and problem-free. This quarter's activities were mainly related to ongoing maintenance and improvements, such as: * An optimization that avoids unnecessary accesses to the working copy database (r1910050). * Bugfix for SVN-4913 related to a move or copy of a URL into a subdirectory of itself (r1909127) and corresponding updates to the automated regression test suite (r1910112, r1910129, r1911062). * Bugfix for 'svn info --show-item wc-root' related to display of paths in the correct style (r1910264). * Bugfix in the regression test suite to assure the SQLite database connection is closed properly (this affected tests only, r1910464). * Build system maintenance related to a recent new release of Apache Serf (r1910152) and deprecations in older versions of Python (r1910098). * Improvements in the Subversion client's built-in help for commands that support a peg-revision indicator with '@' in response to a user question on the mailing list (r1910826, r1910833). * Several backports have been approved for the 1.14.x release line, expected to be released in 1.14.3. * Miscellaneous documentation and website updates. * As mentioned in our previous report, the Subversion website has a new Blog section, found at https://subversion.apache.org/blog/. Currently, it is populated with articles that were previously hosted elsewhere and imported with permission. This quarter, an additional article, "Authz and anon authn agony," has been imported with permission, raising the current total to eleven articles. Hopefully we will be able to add new content in the near future! ## Community Health: The community is healthy: Though the summer season is historically quieter than the spring and fall months, we have been receiving steady contributions to the codebase, website, documentation, backports, and other areas. User questions at our mailing lists and IRC channels have been receiving helpful responses. Our community is fully volunteer-driven and we would like to thank everyone for their support.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: We are still waiting for communication with VP Legal regarding our questions on copyright transfer. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (23 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (13 years ago). There are currently 86 committers and 47 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. In the weeks following the mail "A Message from the Board to PMC members" by Rich Bowen, several PMC members who were dormant and/or not subscribed to the private list have resigned. No new committers or PMC members have been added since the last report. Our most recently added PMC member, Daniel Sahlberg (dsahlberg@) joined the PMC in August 2021. ## Project Activity: The Subversion website has a new Blog section, which can be found at https://subversion.apache.org/blog/. Currently, the blog is populated with articles from 2006 through 2013 which document technical design choices and usage examples. Previously these were hosted by CollabNet (now Digial.AI) and are now hosted here with permission. Hopefully the blog will acquire new articles over time! Our August 2022 board report discussed the need for a plaintext password cache in certain situations on Unix systems. Normally Subversion stores passwords in encrypted form by using standard OS facilities like Windows APIs and macOS Keychain. On Unix systems, where there is no one standard encrypted store, Subversion supports GNOME Keyring, KWallet, GPG-Agent, and a plaintext cache which can be used only after a warning and user confirmation. Subversion 1.12.x through 1.14.x disabled the possibility of storing passwords in the plaintext cache in the default build. Unfortunately, this caused problems for users who need this feature, especially when using the svn client in unattended processes such as CI systems, or on remote machines through ssh. Users have been quite vocal in requesting the reversal of this decision. Some users reported that they had to employ workarounds that caused passwords to be stored in plaintext anyway. Others reported that they could not or would not upgrade their Subversion installations to recent releases because of this issue. Based on the feedback received and numerous discussions spanning several years, default builds of the Subversion client starting with 1.15.x can once again write to the plaintext cache (after warning and user confirmation). Sites that wish to disable this possibility can compile Subversion with the --disable-plaintext-password-storage option (or install a binary package that was compiled this way) and/or set "store-plaintext-passwords = no" in Subversion's run-time config settings. More details can be found at the draft release notes for this change: https://subversion-staging.apache.org/docs/release-notes/1.15.html#plaintext-passwords-supported This quarter saw bug fixes and refinements for the upcoming Pristines On Demand feature, scheduled for release with Subversion 1.15.0. This feature allows users, at their option, to cut in half the storage space requirement for a Subversion working copy at the expense of additional network communication with the repository server. This tradeoff was originally requested for checkouts containing very large files that change infrequently, but is equally useful in any situation where bandwidth to the repository server is more abundant than storage space on the local device. Other development work this quarter includes: * Experimental (proof-of-concept) work on a "pristine-checksum-salt" branch, partly in support of Pristines On Demand. * Bug fixes in the build system, an issue related to file externals in combination with redirected URLs (Issue #4911), and an issue involving moving a directory into its own subdirectory (Issue #4913). We've communicated with other ASF projects which provide some of Subversion's dependencies: * Communicated with the Apache Portable Runtime (APR) project regarding an issue in APR v1.7.3 that makes it impossible to use that release with Subversion. In response to that, APR v1.7.4 was released very quickly. Thanks to the APR team! * Communicated with the Apache Serf project regarding the need for a new release to move past EOL-OpenSSL 1.1.1 to the current supported version 3. The needed changes have been committed and nominated for backport and discussions have begun regarding the logistics of Serf's next release. Thanks to the Serf team! ## Community Health: The community is healthy: Activity comes and goes in waves, but we are seeing steady improvements to the codebase, friendly developer discussions, and helpful replies to user questions. Our community is fully volunteer-driven and we would like to thank everyone for their support.
@Sander: follow up on the issues section for Subversion
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (23 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (13 years ago). There are currently 88 committers and 50 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. No new committers or PMC members have been added since the last report. Our most recently added PMC member, Daniel Sahlberg (dsahlberg@) joined the PMC in August 2021. ## Project Activity: The most exciting new Subversion feature, Pristines On Demand, has finally been merged from its development branch to trunk. This means the feature is expected to ship in the next "point zero" release, which will be Subversion 1.15.0. Pristines On Demand lets users, at their option, cut in half the storage space requirement for a Subversion working copy at the expense of additional network communication with the repository server. This tradeoff was originally requested for checkouts containing very large files that change infrequently, but is equally useful in any situation where bandwidth to the repository server is more abundant than storage space on the local device. At this time, the Pristines On Demand feature is believed to be substantially complete. Interested parties are encouraged to get involved by helping to test the feature before the next release. If unsure how, please ask on our mailing lists: https://subversion.apache.org/mailing-lists.html. In addition to the new feature development, ongoing maintenance work continued this quarter, including bug fixes in Subversion's core code, JavaHL bindings, and automated test suite, updated dependency versions in the unix-build scripts, improved compilation times on Windows in certain configurations, and updated hyperlinks. Currently, project participants are debating several technical issues, including: * How terminal escape sequences should be displayed if present in commit logs or other user-supplied information. * Possible changes regarding how Subversion handles working copies that span filesystem and/or ownership boundaries. * Possible changes in the hash codes Subversion uses to manage working copies, including the possibility of supporting multiple hash code types. ## Community Health: The community is healthy: Activity has picked up this quarter relative to the previous quarter. User questions on our mailing lists are receiving helpful responses. Patches supplied by community members have been vetted and committed. Developer discussions are taking place, and though there are some disagreements, the community remains a friendly and welcoming place. Our community is fully volunteer-driven and we would like to thank everyone for their support.
@Roman: follow up with Subversion about VP Legal request
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (over 22 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (over 12 years ago). There are currently 88 committers and 50 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. No new committers or PMC members have been added since the last report. Our most recently added PMC member, Daniel Sahlberg (dsahlberg@) joined the PMC in August 2021. ## Project Activity: Ongoing maintenance work has continued this quarter, including: * Bug fixes in Subversion's Python and Ruby SWIG bindings * Bug fixes in Subversion's JavaHL bindings * Improvements to the Swedish translation * One backport approved * Additional backport nominations in the pipeline * Other minor fixes and maintenance ## Community Health: Our community is fully volunteer-driven and we would like to thank everyone for their support. Some quarters are busier than others. Although the last few months have been relatively quiet, activity has increased slightly over the previous quarter, mostly in areas of ongoing maintenance, bug fixes, and patches from community members which have been reviewed and committed. User questions on our mailing lists and IRC channels have for the most part received helpful responses, though in cases where the question is complex and requires specialized knowledge or research, there is a sometimes a delay. One such question which has not been responded to yet is with regards to reconstruction of data that has been rendered as good as destroyed by a ransomware attack that affected the victim's backups as well as their production systems. These types of attacks have been in the news for some time now and can affect anyone, regardless of the type of data and whether there is a version control system in place. Questions like these should be a reminder to everyone to reassess their backup and disaster recovery strategies to ensure they take this kind of scenario into account.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (22.5 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (12.5 years ago). There are currently 88 committers and 50 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. No new committers or PMC members have been added since the last report. Our most recently added PMC member, Daniel Sahlberg (dsahlberg@) joined the PMC in August 2021. ## Project Activity: Ongoing maintenance work has continued this quarter, including: * Fixes in Subversion's build system * Better Python compatibility * Extensive updates to the Swedish translation * Improvements in tooling scripts and documentation to better assist future Subversion release managers * A client-side script to assist users who need to cache Subversion client credentials in plaintext That last item is the outcome of numerous discussions, debates, and even complaints since plaintext credential storage has been disabled by default at build-time starting in Subversion 1.12. It turns out, though, that plaintext storage is appropriate and even necessary in some situations. Users who need this feature have been quite vocal in requesting it. Until now, the only solution we could suggest to such users was to build Subversion themselves and enable plaintext storage at build time, but this can be a non-trivial undertaking. The new script provides a middle ground, allowing users to explicitly store a credential in plaintext, with appropriate warnings documented within the script itself and at our FAQ entry which discusses credential storage at length and provides the link to the script: https://subversion.apache.org/faq.html#plaintext-passwords ## Community Health: Activity tends to come in waves around here, with peaks of energy around release time followed by a few calmer, quieter months as our volunteers get busy with other work. This summer has been one of the quieter quarters, following closely on the heels of several action-packed months that saw new feature development in Pristines On Demand, updates to our release policy, and the simultaneous releases of Subversion 1.10.8 and 1.14.2. Our community is fully volunteer-driven and we would like to thank everyone for their support.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (22 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (12 years ago). There are currently 88 committers and 50 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. No new committers or PMC members have been added since the last report. Our most recently added PMC member, Daniel Sahlberg (dsahlberg@) joined the PMC in August 2021. ## Project Activity: This has been an eventful and rewarding quarter for Subversion with ongoing new features development, improved and expanded regression tests, bug fixes, website improvements, an emerging consensus on future release planning policies, and, perhaps most notably, two releases including security fixes. On 4 April 2022, we released Subversion 1.10.8 and 1.14.2. These releases fix two server-side security issues known as CVE-2021-28544 and CVE-2022-24070, in addition to a number of other bug fixes and improvements on both the client and server. Development of new features is ongoing and has progressed nicely during this quarter. Two major features currently in development are described below: Previously, Subversion clients could operate only on the latest available working copy format. A new feature known as Multi-WC-Format, which has already been merged to trunk, will allow newer clients to operate on multiple working copy formats. This will alleviate the need for users to upgrade their working copies unless they wish to use features that require a new format. It will also allow users who have multiple installed versions of Subversion clients (e.g., the latest command line client installed in parallel to an IDE with an older built-in Subversion client library) to experience less hassle if they access a working copy with more than one of these clients. Multi-WC- Format is expected to be released with Subversion 1.15.0 and will support working copies from Subversion 1.8 and up. This feature is motivated by a desire to balance the maturity and stability enjoyed by Subversion's users with the needs of the upcoming Pristines On Demand feature, described below. Our last few reports have mentioned Pristines On Demand, a new feature which, at the user's option, cuts in half the storage space consumed by a Subversion working copy at the expense of potential additional network communication with the repository server. This tradeoff makes sense in a number of situations, such as when version controlling very large files that change infrequently (e.g., release artifacts, binary formats, etc.), or where network bandwidth is more abundant than storage space (e.g., Subversion working copies on FLASH-limited embedded systems). This quarter, development of the initial production-ready version of the feature continued, with excellent results. Though it is currently a little rough around the edges, the feature appears to work as advertised. (I have used a recent development build and have not encountered any problems with it.) Altogether, over 300 commits were made to the Subversion subtree this quarter, roughly categorized as follows: 30% in new features development, 7% in improved regression tests, 7% in bug fixes, 41% in release engineering, and 15% in website improvements. To everyone who has helped move this project forward, thank you. ## Community Health: It is this chair's opinion that community health is good, despite the ups and downs and various challenges we experience as a community- driven project. For several years, the Subversion website described a time-based release policy under which new minor release lines would be released every six months, with a combination of LTS releases supported for four years and Regular releases having short six month lifespans. This replaced an earlier policy of making releases whenever we were ready with no predefined time-based lifespan. Motivation for the time-based policy was to encourage new feature development, release new features to users more quickly, and help system administrators plan server upgrades. The time-based policy worked well when corporate sponsorship made it possible, but turned out to be unrealistic without corporate backing. As a community, we've discussed this issue on and off for some time with some developers encouraging a return to the original "when we're ready" policy and others suggesting a variety of alternatives. Finally, there is an emerging consensus to go with a hybrid of the newer and older policies which should be more in tune with the realities of a community-driven project while still providing the most important benefits that motivated the time-based policy: New minor release lines will be made "when we're ready" but we'll keep the LTS and Regular designations to help system administrators plan server upgrades. To ensure that there is always at least one supported LTS release line, these will be supported for at least four years, or three months after the next LTS release, whichever is later. There is no longer a requirement to make releases on any fixed schedule, but to facilitate development and timely release of new features, the option to make Regular (six month lifespan) releases exists. Also, if and when we make new minor release lines frequently enough to justify it, we'll designate some of them as Regular to avoid creating too many LTS lines that need to be supported in parallel. Interested readers can find the new policy text on the "roadmap" part of our website: https://subversion.apache.org/roadmap.html. We hope this new release policy strikes a balance that is both advantageous and realistic. As always, we encourage and welcome participation, both in development and project management, on our mailing lists.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (22 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (12 years ago). There are currently 88 committers and 50 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. No new committers or PMC members have been added since the last report. Our most recently added PMC member, Daniel Sahlberg (dsahlberg@) joined the PMC in August 2021. ## Project Activity: Our previous report mentioned a proof-of-concept called "Pristines On Demand" which explores a long standing feature request known in our issue tracker as Issue #525: https://subversion.apache.org/issue/525 This quarter, development has begun on an initial production-ready version of the feature. Once implemented and when activated at the user's option, this new feature could cut in half the amount of storage space required to hold a Subversion working copy, at the tradeoff of requiring additional network communication with the repository server. This tradeoff makes sense in a number of situations, such as when version controlling very large files that change infrequently, or where network bandwidth is much cheaper than storage space. The feature is being developed in our "pristines-on-demand" branch and an ongoing discussion is taking place our dev@ mailing list topic "A two-part vision for Subversion and large binary objects," archived at https://lists.apache.org/thread/ncs7y5j7zf7oxfjo7crl2nwcf1188brd and other places. As always, interested parties are encouraged to join our mailing lists and participate in discussions and development activities. Other improvements this quarter include fixes to Python bindings, work on logging in XML format, improvements to the documentation, web site, and Subversion client's built-in help text, new regression tests, improvements to the regression testing infrastructure, fixed compiler warnings, general cleanups, and triaging and closing of obsolete and fixed issues in our issue tracker. For all of these unglamorous but important efforts, we owe a big debt of gratitude to all of our volunteers. ## Community Health: Our biggest challenge is to secure a volunteer for Release Manager, causing a delay in making the next release. In the past, release managers often volunteered for this role for many releases in a row. While this substantial investment of effort and time is greatly appreciated by the community, it is unfair to the volunteer and causes a vacuum that is difficult to fill when the release manager is no longer able to volunteer for that role. We had a recent discussion about the need for more rotation of the Release Manager role within the project, with encouragement for a release manager to step aside after managing the last minor release or approximately two patch releases. Hopefully we will overcome this challenge soon and be a healthier community as a result.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (nearly 22 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (almost 12 years ago). There are currently 88 committers and 50 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. No new committers or PMC members have been added since the last report. Our most recently added PMC member, Daniel Sahlberg (dsahlberg@) joined the PMC on August 2021. ## Project Activity: Recently on our mailing lists, we've been hearing from existing and potential new users who need version control for non-source-code assets, often in binary formats and sometimes quite large in size. This is one of the areas where Subversion is much stronger than other version control systems due to its centralized nature, locking features, and feasibility of maintaining large repositories. This quarter, a new proof-of-concept development aims to make Subversion even stronger in this area: Known as Issue #525 or "Pristines On Demand," the amount of storage space needed to hold Subversion working copies could be cut in half, which can be significant when the files in question are very large and change infrequently. This is possible because Subversion currently makes two copies of each file checked out onto a user's machine: one for the user to work with and possibly modify, and a second "pristine" copy kept on the back burner for operations like comparing, differencing, or reverting changes. While pristines help keep operations local, some use cases would benefit from reducing or eliminating them. The proof of concept can be found in Subversion's "pristines-on- demand" branch, with a description in our dev@ mailing list topic "A two-part vision for Subversion and large binary objects." See the message dated August 27, 2021, archived at https://lists.apache.org/thread/ncs7y5j7zf7oxfjo7crl2nwcf1188brd, for a description of the branch. Interested parties are encouraged to experiment with the branch and participate in its further development. Also this fall, a number of bugs have been squashed, including some sneaky ones hiding in the conflict resolver, several new regression tests have been added, and various documentation and website improvements have been implemented. Though these activities may seem less glamorous than new feature developments, they are nevertheless crucial to our project and to those of us who rely on Subversion day in and day out to store and manage our important data. We owe a debt of gratitude to all of our volunteers for the work they do. ## Community Health: Currently our biggest challenge is to secure a volunteer for Release Manager. Our usually most active developers have been busy with other work for most of this quarter, leading to a delay in making a release. Our most recent release, 1.14.1, was made on 2021-02-10, and we have numerous fixes waiting on the 1.10.x and 1.14.x branches, plus several exciting performance improvements waiting to be released in 1.15.0. We have heard from users and downstream packagers who are eagerly awaiting the next release. Notwithstanding the above challenge, which we hope will be resolved before the next report, development and maintenance activities continue and the user and developer community is responsive to questions and discussions on the mailing lists and IRC channels.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (21 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (11.5 years ago). There are currently 88 committers and 50 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. One PMC member has been added since the last report: Daniel Sahlberg (dsahlberg@) joined the PMC on 03 August 2021. No new committers have been added since the last report. ## Project Activity: This quarter, we moved our Internet Relay Chat (IRC) presence from freenode to Libera.chat. On 19 May 2021 we began a transition process to move our IRC user (#svn) and developer (#svn-dev) channels. The transition process, including the moving of bots and other services, lasted a week and was completed and announced on 26 May 2021. We'd like to extend a warm welcome to all community members and developers who wish to join and discuss all things Subversion. As always, our mailing lists and other resources are available as well. For more, see: http://subversion.apache.org/faq.html#more-information The Subversion website has been improved with respect to mobile friendliness. Users who access the site via their smartphone or other mobile device should enjoy a site that is easier to read and navigate than before. In addition, some graphics which were raster formats have been upgraded to vector formats, resulting in sharper and clearer images. (Note that web browsers that have cached copies of our old CSS may render the site strangely; currently this can be fixed by force-reloading the page.) Currently the site retains the same general appearance as before. There has been talk of a larger update, though the initial goal of mobile friendliness has been achieved. Several bugs have been fixed, including a workaround for a Python bug in our SWIG bindings, a fix for a wrong path transcoding that could occur under some circumstances when invoking the user's editor, and a missed dependency in the build system that only manifested if attempting to make the davcheck or davautocheck targets immediately after configure. The build system has been made aware of Windows on ARM and ARM64, which should make it possible to build Subversion on these systems. Various docs and comments throughout the code have been improved. Numerous links, found throughout our website, in our code, and in our documentation, have been updated to new locations and switched from http to https. Finally, our repository subtree has reached a symbolic milestone this quarter: our trunk has reached its 60,000th commit! We'd like to take this opportunity to express our gratitude to all of our developers, whose efforts, often over late nights, weekends, and vacations, have made and kept this project possible. ## Community Health: The user and developer community is responsive on the mailing lists and IRC channels. There is an ongoing discussion in both venues about the possibility of developing an ambitious new feature known as Issue #525. If implemented, this could make Subversion stronger at certain use cases where it already has an advantage over other systems, such as management of large binary assets. Development activity on the actual core of Subversion has been slow this summer. However, the activities and improvements mentioned above are equally important and appreciated.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (21 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (11 years ago). There are currently 88 committers and 49 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. No new committers have been added since the last report. Our most recently added committer, Daniel Sahlberg (dsahlberg@) received a commit bit in December 2020. No new PMC members have been added since the last report. Our most recently added PMC member, Jun Omae (jun66j5@) joined the PMC in May 2020. ## Project Activity: This quarter, two exciting client-side performance improvements landed in trunk. The first speeds up 'svn checkout' and 'svn update' operations when fetching large directories from the server while simultaneously solving an annoying issue with server-side timeouts. This is achieved by combining what were previously separate steps that at times held the server connection open without reading from it, leading to the timeouts. The new process, which could be called "streamy checkouts," results in a noticeably snappier user experience. The second is a new "thread pool" API to leverage modern multi-core systems. The challenge is order of operations: certain steps must run in a deterministic sequence, contrary to the asynchronous nature of thread pools. The new APIs address this by running part of the work in multiple threads, after which a follow-up runs in the same order as sequential code. Currently only 'svn status' uses the new APIs, but other features could be made to take advantage of them in the future. These new features are expected to eventually ship in a future 1.15 release line, which has not been scheduled yet. Other improvements and bug fixes developed during this quarter include improved Python 2 and Python 3 compatibility, a workaround for Python issue #40312, bug fixes for SWIG bindings, contributed scripts, string encoding handling, i18n regressions, out-of-tree builds, building Subversion on Windows, improved handling of foreign repository merges, new regression tests, and other minor improvements. ## Community Health: Activity seems to come in waves, as our volunteers desire and are able to invest their time and effort into Subversion. Our last quarter of 2020 was our quietest ever, but it was followed by an action-packed first quarter of 2021. In comparison to it, this second quarter of 2021 felt slower, but was nevertheless quite eventful. It began with the releases of 1.10.7 and 1.14.1, the culmination of the previous quarter's work, and was soon followed by the new feature development and other improvements and bug fixes mentioned earlier. Recently we had a discussion about our community health. It began when one of our volunteers noticed that an easy-to-make but serious C programming mistake was committed and went unnoticed for 11 days. This error affected only a new regression test that was added in the same commit; it has never been included in a release and was quickly fixed once it was pointed out, but it did prompt the discussion. Various aspects of community health were discussed and ideas proposed. It does not escape us that we have difficulty enticing volunteers to take on demanding tasks such as release management. The final word seems to be that to ensure long-term longevity, we need to attract new developers to the project. Notwithstanding the above discussion and the challenges that we do face, it is this chair's feeling that our project is more active and our community health is better than it may at times feel. It may look dismal when compared to the heyday of our early years, but considering that this quarter, we had 100 commits, more than one for each day, with the vast majority of these being quite substantive, not "easy" things like typo fixes; 100% of questions posted to our users@ mailing list received responses; new features were developed; bugs were fixed; when compared to other volunteer-driven projects of similar age and maturity, some of which go weeks or months without a commit, our community health looks far more encouraging.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. Subversion was founded in February 2000 (21 years ago) and joined the ASF to become Apache Subversion on 2010-02-16 (11 years ago). There are currently 88 committers and 49 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. We have added one new partial committer since the last report: Daniel Sahlberg (dsahlberg@) received a commit bit in December 2020. No new PMC members have been added since the last report. Our most recently added PMC member, Jun Omae (jun66j5@) joined the PMC in May 2020. ## Project Activity: This quarter, our all-volunteer developers have burned the midnight oil to prepare new releases in our 1.10 and 1.14 lines. These will bring numerous bug fixes and improvements in the core code, build system, regression test suite, Python 3 support, JavaHL bindings, and other areas. Several long standing bugs have been brought to our attention and fixed. The release candidates are now undergoing our testing, signing, and voting process, and we expect to ship 1.10.7 and 1.14.1 later this month. Last quarter, we reported that svn.haxx.se, "an unofficial Subversion related mailing list archive," was about to shut down forever. That would be a tremendous loss for our community because it would 404 the only archive from Subversion's birth in 2000 through joining the ASF in late 2009. That part of our history contains the most important discussions about the design of Subversion's internals and might be the only documentation of the rationale behind some significant technical decisions. The impact of such a loss cannot be estimated. We are pleased to report that we have coordinated with INFRA and the original operators of svn.haxx.se and are now hosting the archive on one of our PMC's virtual machines. We do not know whether this will be a permanent arrangement or just a stopgap while we search for a better solution. The current setup has the advantage of preserving URLs, which are found throughout our archived emails and commit logs and across the Internet. However, it has the disadvantage of living on a virtual machine that we believe is not currently backed up, and therefore continues to be at risk of loss. Nevertheless, we would like to extend our most gracious thanks to everyone who helped bring us this far, with a big shout-out to Daniel Sahlberg for the lion's share of the work, to the long-time operators of svn.haxx.se for maintaining the archive for over 20 years, and to INFRA for being very helpful (and patient!) with our many questions and requests. ## Community Health: Activity seems to happen in waves. While the previous quarter was rather quieter than usual, activity has picked up significantly this quarter. Developer email discussions increased 85% and commit activity increased 222%. Recently, we received several questions at our users mailing list about how to migrate to Subversion from other systems, including Git. With the increased activity, work toward saving of the archive, and upcoming releases, our community health feels much improved this quarter.
## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Issues: There are no Board-level issues at this time. ## Membership Data: Apache Subversion was founded 2010-02-16 (11 years ago). There are currently 87 committers and 49 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Our developer and user community is all-volunteer and we'd like to begin by thanking everyone for their support. We have added one new partial committer since the last report: Alexandr Miloslavskiy (amiloslavskiy@) received a commit bit in Sepember 2020. No new PMC members have been added since the last report. Our most recently added PMC member, Jun Omae (jun66j5@) joined the PMC in May 2020. ## Project Activity: This has been an eventful year for our project, starting with our 20th anniversary and followed by our major 1.14.0 milestone release in the first half of the year. ## Community Health: This quarter, the community has been quieter than usual. Although our developers and community members are monitoring the mailing lists and responding to questions and discussions, our usually most active developers have been more limited in their time. This may be a balance for our action-packed first half of the year, or perhaps is attributed to this year's unique challenges. Having said so, there have been some important bugs fixed and user requests implemented. Some of these are expected to appear in an upcoming 1.14.1 patch release, which we have begun discussing. Recently we learned that svn.haxx.se, "an unofficial Subversion related mailing list archive," plans to shut down this month. Although not part of Apache Subversion, it has been popular with our community members for many years. The impact for our project is that the early years of archived developer and user emails, from Subversion's birth in 2000 through joining the ASF in late 2009, are not archived nor available at lists.apache.org. In a community discussion about this, there has been some indication that the popular site could be hosted elsewhere, though it might be best if we could find a way to integrate the early years of the archives and host them here.
The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no board-level issues at this time. However, we would like to make the board aware of the following: This quarter, we made a long-awaited milestone release. Our PMC was blocked from announcing it on the ASF-wide announce@a.o mailing list by one of the list's moderators who acted unilaterally. We feel this was unjust and outside the scope of moderation, but more importantly, it interfered with the normal operations of our PMC. As we have not yet exhausted the normal path of escalation, we are not requesting any board intervention at this time. * Community Our developer community is all-volunteer and we'd like to begin by thanking everyone for their hard work and support. This quarter began with a flurry of activity in the run-up to our recent 1.14 release (see Releases below). This is our most important release since 1.10 in 2018 and the first since our 20th Anniversary. We'd like to thank Sally and ASF Marketing for assisting us with a Press Release to announce this major milestone. Since the release, our developer mailing list has quieted down considerably as we all catch our breath. However, we have been receiving constructive feedback and bug fixes. These are gradually being vetted for inclusion in an upcoming point release. Our user support forums (Email and IRC) receive questions and answers regularly and our dev@ list has been receiving bug reports and patches for bug fixes. We have added one PMC member since the last report: Jun Omae (jun66j5@) joined the PMC in May 2020. * Releases Our most recent release, 1.14.0, was made on 27 May 2020.
The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues at this time. * Community At the Subversion project, we believe that it is healthy for our community to change PMC chairs from time to time. This April, the PMC chair hat transitioned from Stefan Sperling to Nathan Hartman. Stefan served as PMC chair for a bit over two years, and we anticipate that our new chair will serve for about the same length of time. As we welcome Nathan to this role, we'd like to extend our heartfelt thanks to Stefan for his diligent service these past two years. This February, we celebrated the 20th Anniversary of the Subversion project, and, with the help of Apache Marketing, we recognized this occasion with a press release on February 27th. During this process, we collected testimonials and success stories from a few of our long-time users in the corporate world. We'd like to thank Apache Marketing and give a shout-out to Sally Khudairi for making this possible. Also we'd like to thank our own Daniel Shahaf for providing the inspiration to do it. This quarter, we have seen a noticeable uptick in activity, both from developers and users. Much of the increase is due to our upcoming release (see Releases below). There is now an ongoing discussion at our users@ list about a possible major new development, aimed at making Subversion even stronger than it already is at handling large binary files. This appears to be an important use case for work in video games, semiconductors, and other industries. Our user support forums (Email and IRC) receive questions and answers regularly and our dev@ list has been receiving patches for minor new features, bug fixes, and proposed optimizations. No new PMC members have been added since the last report. Our most recently added PMC member, Yasuhito Futatsuki (futatuki@), joined the PMC in November 2019. * Releases Our most recent release, 1.13.0, was made on 30 Oct 2019. A large part of our development efforts this quarter have been focused on the upcoming release of Subversion 1.14.0. The 1.14.x series will be our latest Long Term Support (LTS) line, with planned support for at least four years. The latest release candidate is currently undergoing a four-week "soak" period, part of our process for creating quality releases. During this time, interested developers, users, and other stakeholders are highly encouraged to test the release candidate and report any issues that should be addressed. If no "showstoppers" are found, Subversion 1.14.0 is scheduled to be released later this month.
WHEREAS, the Board of Directors heretofore appointed Stefan Sperling (stsp) to the office of Vice President, Apache Subversion, and WHEREAS, the Board of Directors is in receipt of the resignation of Stefan Sperling from the office of Vice President, Apache Subversion, and WHEREAS, the Project Management Committee of the Apache Subversion project has chosen by consensus to recommend Nathan Hartman (hartmannathan) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Stefan Sperling is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Subversion, and BE IT FURTHER RESOLVED, that Nathan Hartman be and hereby is appointed to the office of Vice President, Apache Subversion, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7G, Change the Apache Subversion Project Chair, was approved by Unanimous Vote of the directors present.
The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The Subversion development community is fairly quiet these days. A small trickle of development is ongoing. The community usually responds to bug reports and is willing to help the reporter or any other volunteer to develop a fix. However, in many cases there is no such volunteer, and those bug reports are filed but often remain unresolved. Our user support forums (Email and IRC) receive questions and answers regularly. We have added no new committers/PMC members since the last report. Most recently added PMC members are Nathan Hartman (hartmannathan@) and Yasuhito Futatsuki (futatuki@). * Releases The currently supported releases are Subversion 1.13.0 and 1.10.6. We are currently preparing for the 1.14 release which is expected in April: https://subversion.apache.org/roadmap.html#release-planning Discussions about the frequency of minor releases are still taking place on our dev@ list. Because funding for a developer who managed our time-based releases is no longer available the community is reconsidering the viability of time-based releases. One particular question is whether we should move towards a release model which is focused on maintenance in the long term, as opposed to development of new features.
The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The Subversion development community is fairly quiet these days. A small trickle of development is ongoing. The community usually responds to bug reports and is willing to help the reporter or any other volunteer to develop a fix. However, in many cases there is no such volunteer, and those bug reports are filed but often remain unresolved. Our user support forums (Email and IRC) receive questions and answers regularly. We have added two PMC members since the last report: Nathan Hartman (hartmannathan@) and Yasuhito Futatsuki (futatuki@). * Releases Subversion 1.13.0-rc1 and 1.13.0 have been released. Subversion 1.12.x reaches end of life. Subversion 1.10 and Subversion 1.9 are still supported. Discussions about the frequency of minor releases have taken place on dev@. The community is still evaluating the cost and benefits of the time-based release schedule which was introduced in 2018. https://subversion.apache.org/roadmap.html#release-planning
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The Subversion development community is fairly quiet these days. A small trickle of development is ongoing. The community usually responds to bug reports and is willing to help the reporter or any other volunteer to develop a fix. However, in many cases there is no such volunteer, and those bug reports are filed but often remain unresolved. In July 2019, a handful of developers has managed to put new releases out the door. Concerns over potential lack of testing and release signatures from PMC members were raised beforehand, but these problems did not materialize. Regardless, the project would do better with more active developers. The good news is that these issues are being openly discussed on our mailing lists, with even non-PMC members contributing to these discussions. Our user support forums (Email and IRC) receive questions and answers regularly. No new committers were added since the one reported in February. * Releases Subversion 1.12.2, 1.10.6, and 1.9.12 were released on July 24 2019. These releases contain fixes for two security issues, CVE-2018-11782 and CVE-2019-0203 (these affect Subversion 'svnserve' servers only.) We are currently discussing the possibility of dropping support for the 1.9 release series. Subversion 1.11 is no longer supported. * Delayed patching of known security issues Patches for the pending security issues mentioned in the previous report have now been released.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The Subversion development community is fairly quiet these days. A small trickle of development is ongoing. The community usually responds to bug reports and is willing to help the reporter or any other volunteer to develop a fix. However, in many cases there is no such volunteer, and those bug reports are filed but often remain unresolved. Our user support forums (Email and IRC) receive questions and answers regularly. No new committers were added since the one reported in February. * Releases Subversion 1.12.0 was released on April 24 2019. This is a regular release which will receive 6 months of support. Subversion 1.11, the previous regular release, is no longer supported. Subversion 1.9 and 1.10 are our current long-term-support (LTS) releases and will receive support until August 2019 and April 2022, respectively. * Delayed patching of known security issues There are currently two pending private security issues, the one mentioned in the last report which was reported to us in August 2018, and a newer one which was reported to us in February 2019. In the past, there were usually enough volunteers willing to address security issues. A PMC member with commercial funding (Julian Foad) has recently been assigned some work time to address one or both of these.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The community is healthy and active. New features are being designed and developed, and bug reports are being handled. Our user support forums (Email and IRC) receive questions and answers regularly. We added Yasuhito Futatsuki (futatuki@), who is working on Subversion's bindings to Python 3, as a committer in January 2019. * Releases Subversion 1.9.10, 1.10.4, and 1.11.1 were released January 11 2019. Subversion 1.12.0 is expected in April 2019, at which point we will stop supporting 1.11 releases. Subversion 1.9 and 1.10 are our current long-term-support (LTS) releases and will receive support until August 2019 and April 2022, respectively. * Delayed patching of known security issues The project has been discussing its approach to security issues. We decided to move parts of related documentation and scripting, which had been kept private, to our public repository. We have two processes for handling security issues, a "public" process where fixes are committed to our public repository before a release is cut, and a "private" process where patches are maintained in the private area of our repository and are included in the release by our release manager. The community is currently debating the merits of each process, and perhaps switching to a single unified process. On January 18, we published a security advisory for CVE-2018-11803. The issue formerly known as CVE-2018-1293 is not fixed yet. It is no longer considered a security issue because its impact is minimal and the workaround is easy (use 'svn rm' on offending path). A fix is being developed in public and status is being tracked in https://issues.apache.org/jira/browse/SVN-4788
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The community is healthy and active. New features are being designed and developed, and bug reports are being handled. Our user support forums (Email and IRC) receive questions and answers regularly. Our last committer additions happened in October 2017: Pavel Lyalyakin who has been contributing to the project's website. Troy Curtis Jr who has been contributing to SVN's Python 3 bindings. * Releases We have released Subversion 1.10.3 on October 10 2018, and Subversion 1.11.0 on October 30 2018. The current supported releases are 1.9.9, 1.10.3, and 1.11.0. * The PMC was formally enquired by the European Commission regarding the merger of Microsoft and GitHub. The RFI was responded to by the Chairman. * Delayed patching of known security issues The developer base keeps prioritizing other work over known security problems. The Apache Security team keeps sending us occasional reminders about problems which got CVE numbers assigned to them but have no public fix yet after months of being reported. Part of the problem is that our active developer base is shrinking. Some outstanding work on security issues was begun by developers who appear to have since become inactive. The status of outstanding known security issues is documented below. ^/pmc/subversion/security/CVE-2018-1293 Per recommendation by the Apache Security team, this problem is now being treated as a non-security issue. The impact is a DoS which can only be triggered by an authenticated attacker, and is easily resolved with 'svn rm'. Also, the work required for a fix is not trivial so development on a public branch will be easier than mailing patch files around. A fix is now being developed in public: https://svn.apache.org/r1846391
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The community is healthy and active. New features are being designed and developed, and bug reports are being handled. Our user support forums (Email and IRC) receive questions and answers regularly. Our last committer additions happened in October 2017: Pavel Lyalyakin who has been contributing to the project's website. Troy Curtis Jr who has been contributing to SVN's Python 3 bindings. * Releases We have released Subversion 1.10.2 and 1.9.9 on July 20 2018. The current supported releases are 1.10.2 and 1.9.9. Several bug fixes for our stable release series have been proposed, New patch releases can be expected in the near future. We have changed our supported release policy. Our plan is to publish new standard releases (SVN-1.x) every 6 months, with a bug-fix support period of 12 months. Every 2 years, a long-term support (LTS) release will be issued which receives bug fixes for a period of 4 years. Subversion 1.11.0 is therefore expected in October 2018. Our new release policy is documented in detail here: https://subversion.apache.org/roadmap.html#release-planning We have also changed our release signature requirements. Our previous policy required 6 PGP signatures from PMC members, 3 of which count for UNIX-like platforms and 3 of which count for Windows platforms. The new policy requires at least 3 PGP signatures from PMC members, where at least one signature counts for UNIX-like systems and another one counts for a Windows system. See https://svn.apache.org/r1835191 and https://svn.apache.org/r1835195 for related changes made to our policy documentation. * Trademarks The PMC has decided against renewing the Japanese trademark registration for "SUBVERSION" (Reg No.5148681). This trademark had been registered by CollabNet, Inc. Corresponding registered trademarks for US and EU are still in place.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The community is healthy and active. New features are being designed and developed, and bug reports are being handled. Our user support forums (Email and IRC) receive questions and answers regularly. Our last committer additions happened in October 2017: Pavel Lyalyakin who has been contributing to the project's website. Troy Curtis Jr who has been contributing to SVN's Python 3 bindings. We thank Johan Corveleyn and Mark Thomas for their behind-the-scenes assistance in dealing with code of conduct violations. * Releases We have released Subversion 1.10.0 on April 13 2018. This release was accompanied by an ASF blog post: https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces31 The current supported releases are 1.10.0 and 1.9.7. Several bug fixes for our stable release series have been proposed, New stable releases can be expected in the near future. * Wiki Migrated Our Wiki was migrated from the ASF's old MoinMoin instance to the Confluence wiki on cwiki.apache.org. The migration took considerable effort to get right, preserving full history and as much of the original layout as possible. The various conversion tweaks will be documented for ASF Infra so they can be reused for other interested projects. The old wiki pages will be edited to become redirects to the new pages, after which they can be made read-only.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The community is healthy and active. New features are being designed and developed, and bug reports are being handled. Our user support forums (Email and IRC) receive questions and answers regularly. Our last committer additions happened in October 2017: Pavel Lyalyakin who has been contributing to the project's website. Troy Curtis Jr who has been contributing to SVN's Python 3 bindings. * Releases There were no new releases published since August 10 2017. The current supported releases are still 1.9.7 and 1.8.19. Several bug fixes for our stable release series have since been proposed, implying that new stable releases can be expected in the near future. None of the proposed bug fixes have security implications. We continue moving towards the first GA release of Subversion 1.10.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The community is healthy and active. New features are being designed and developed, and bug reports are being handled. Our user support forums (Email and IRC) receive questions and answers regularly. The project is holding a hackathon in Aachen, Germany, for a duration of 5 days in November (21st - 26th). At least 5 developers will be attending this event. The community has reached out to the general public with an invitation to a "meet and greet" event which will occur on the 23rd of November. Funding for this hackathon was first sought from the Foundation, but ended up being covered by the company Assembla. Two committer additions happened in October 2017: Pavel Lyalyakin who has been contributing to the project's website. Troy Curtis Jr who has been contributing to SVN's Python 3 bindings. In October, the PMC chair hat was passed from Evgeny Kotkov to Stefan Sperling. There was no pressing need for this switch. The switch was discussed beforehand and agreed upon by the entire PMC. Our main motivation was our belief that occasionally passing such responsibilities around benefits our community in the long term. Evgeny Kotkov served as PMC chair for one year, and we expect our new chair to serve for at least the same amount of time. * Releases There were no new releases published since August 10 2017. The current supported releases are still 1.9.7 and 1.8.19. Several bug fixes for our stable release series have since been proposed, implying that new stable releases can be expected in the near future. None of the proposed bug fixes have security implications. We continue moving towards the first GA release of Subversion 1.10.
WHEREAS, the Board of Directors heretofore appointed Evgeny Kotkov (kotkov) to the office of Vice President, Apache Subversion; and WHEREAS, the Board of Directors is in receipt of the resignation of Evgeny Kotkov from the office of Vice President, Apache Subversion; and WHEREAS, the Community of the Apache Subversion project has chosen to recommend Stefan Sperling (stsp) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Evgeny Kotkov is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Subversion; and BE IT FURTHER RESOLVED, that Stefan Sperling be and hereby is appointed to the office of Vice President, Apache Subversion, to serve in accordance with and subject to the direction of the Board of Directors. and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7D, Change the Apache Subversion Project Chair, was approved by Unanimous Vote of the directors present.
Apache Subversion exists to be universally recognized and adopted as
an open-source, centralized version control system characterized by
its reliability as a safe haven for valuable data; the simplicity of
its model and usage; and its ability to support the needs of a wide
variety of users and projects, from individuals to large-scale
enterprise operations.
* Board Issues
There are no Board-level issues of concern.
* Community
The community has finished the work on resolving the prior-reported
SHA1 hash collision issues. This resulted in preparing two new patch
releases, Subversion 1.8.18 and 1.9.6, with the corresponding fixes.
These releases were simultaneously made available to our users on July 6th.
Apart from this, we also finished the work on the first alpha release of
the upcoming Subversion 1.10 series, 1.10-alpha3 ("alpha1" and "alpha2"
were not released for various technical reasons). While we continue
moving towards the first GA release of Subversion 1.10, such pre-
releases should allow for more widespread testing by the community.
There hasn't been any visible benefits from the previously reported
experimental integration with the Transifex (https://www.transifex.com)
translation platform at this time. We will, however, continue to monitor
how this experiment works out.
During this quarter, there is a major increase in commit activity and
in both dev@ and users@ mailing lists traffic. For instance, our dev@
mailing list has received around 547 messages, opposed to 318 in the
previous quarter. We have seen new people actively participating in
the discussions of some of the upcoming and developed features in
Subversion 1.10, and this may partly explain the increased amount
of traffic.
Last PMC addition was in February 2017 (Stefan Hett).
Last committer addition happened in November 2015 (James McCoy).
* Releases
Subversion 1.8.18 and 1.9.6 were released on July 6th, 2017.
Subversion 1.10-alpha3 was released on July 26th, 2017.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community Within this quarter, the community has been working on resolving the previously reported SHA1 collision issues and on preparing the first alpha release of Subversion 1.10. The work is not yet complete, but some good progress has happened on the SHA1-related issues. We will continue working on these tasks in the next quarter. In order to improve the quality of the translations and to allow more people to participate in the translation process, the community has set up an experimental system using Transifex (https://www.transifex.com) for these purposes. There is a bit of slowdown in the commit activity and in the users@ mailing list traffic, which has received 151 messages during these three months, opposed to 336 in the previous quarter. The dev@ mailing list is active and has received 318 messages. There are no new faces in the community at this time, but we would be happy to include such people to our community if they arrive and try to maintain an open atmosphere with the questions being answered and the feedback occurring in a timely fashion. Last PMC addition was in February 2017 (Stefan Hett). Last committer addition happened in November 2015 (James McCoy). * Releases Subversion 1.8.17 and 1.9.5 were released on November 29th 2016. The work toward Subversion 1.10.x continues.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community During this quarter, the community has finished the work on two bugfix/security releases addressing the CVE-2016-8734 vulnerability. Apart from this, we have been working on changes planned for Subversion 1.10.x. Overall, these changes include different minor improvements, and two new features: the interactive tree conflict resolver, and the reimplemented authorization mechanism with a support for wildcard rules. There are plans to release an alpha version with these features in the nearby time. Our dev@ and users@ mailing lists are active and have received 292 and 336 messages during the past three months. (This is roughly the same amount as in the previous quarter.) The commit rate remains on the same level as well. Stefan Hett was added to the Subversion PMC in February 2017. Last committer addition was November 2015 (James McCoy). * SHA1 Collisions and Subversion With the recent publication of the first known SHA1 collision by Google and CWI, we have identified a couple of related issues. While Subversion is designed to not rely on SHA1 for content indexing, we found a few bugs in the implementations of particular features. The most severe issue is caused by an oversight in the data deduplication feature. It can result in inability to access files with colliding SHA1 values or result in data loss for such files. We are now working on resolving these issues. It is likely that we will need to prepare new 1.8.x and 1.9.x patch releases, and schedule additional changes for Subversion 1.10.x. * Releases Since the last report, Subversion 1.8.17 and 1.9.5 were released on November 29th. The work toward Subversion 1.10.x continues, and we hope to prepare a 1.10.0-alpha1 release soon.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community A hackathon hosted by elego was held in Berlin during October 10th-14th, with approximately 8 developers attending. The discussion was mostly focused around a new developed feature, the interactive tree conflict resolver, and a lot of progress occurred on its development. During this quarter, there is an increase in the dev@ mailing list activity (353 messages, as opposed to 188 in the previous quarter), and a slight increase in the number of commits. Our users@ mailing list is active as well, and receives about 100 messages per month from users and the community members assisting them. There has been a conflict on the ground of inviting a new PMC member, and unfortunately one of the existing PMC members has resigned from the Subversion PMC. The community is now working through several discussions that should help to avoid similar situations in the future. These discussions happen on our private mailing list. Last PMC addition was in December 2015 (James McCoy). Last committer addition was November 2015 (James McCoy). * Releases Our last 1.8.16 and 1.9.4 releases were made on April 28, 2016. The work toward 1.10.x is progressing, with no specific release date planned.
WHEREAS, the Board of Directors heretofore appointed Greg Stein (gstein) to the office of Vice President, Apache Subversion; and WHEREAS, the Board of Directors is in receipt of the resignation of Greg Stein from the office of Vice President, Apache Subversion; and WHEREAS, the Community of the Apache Subversion project has chosen to recommend Evgeny Kotkov (kotkov) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Greg Stein is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Subversion; and BE IT FURTHER RESOLVED, that Evgeny Kotkov be and hereby is appointed to the office of Vice President, Apache Subversion, to serve in accordance with and subject to the direction of the Board of Directors. and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7B, Change the Apache Subversion Project Chair, was approved by Unanimous Vote of the directors present.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community The community continues to operate in a healthy fashion, with continued activity on the dev@ and user@ mailing lists. As a mature project, we are not attracting new developers like we did a decade ago (heh) ... but we continue to accomodate all newcomers and make it easy for them to contribute and to become part of the larger community. Last PMC addition: December 2015. Last committer addition: November 2015. * Releases Last releases were made on April 28, 2016: 1.9.4 and 1.8.16. The community continues to work on a 1.10.x release, with no specific release date planned.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community We have seen a bit of slowdown in dev@ and commit activity, which has been expected, given the (prior-reported) change in employments and the time our developers have available to work on Subversion. But with that said, it has not hampered our development. The project continues to move forward, with good commit activity and discussion occurring on our mailing lists. The project is quite active, and has been responsive (see below) to some security issues that have arisen over the past few months. The users@ mailing list remains active, with about 100 messages per month from users and our community assisting them. Last PMC addition: December 2015. Last committer addition: November 2015. As a mature project, we are not attracting lots of new people, yet (as always) we maintain an open/inviting atmosphere. * Releases On April 28, two releases were made: 1.9.4 and 1.8.16. These were primarily to address CVE-2016-2167 and CVE-2016-2168. The 1.9.x line is our "current stable" release, and 1.8.x is our maintenance line receiving security and critical bug fixes. The community is developing 1.10.x, but has no specific timeline or feature set (yet) defined.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community Our last PMC addition was in December 2015 (James McCoy) Our last committer addition was in November 2015 (James McCoy). The community remains active on its mailing lists: * almost 800 subscribers to users@ with over 100 messages per month * over 300 subscribers to dev@ with over 120 messages per month The dev@ activity and a healthy commit rate is encouraging, as we have seen a downward trend of paid developers over the past six months. * Releases Apache Subversion 1.9.3 was released on December 14, 2015. Apache Subversion 1.8.15 was released on December 14, 2015. Development continues on 1.10.x, with about 250 commits per month. No target date or feature set has been defined.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community Our last PMC addition was in February 2014 (kotkov) Our last committer addition was in September 2015 (luke1410). The community remains active on its mailing lists: * almost 800 subscribers to users@ with over 100 messages per month * over 300 subscribers to dev@ with about 250 messages per month * Releases Apache Subversion 1.9.1 was released on September 2, 2015. Apache Subversion 1.9.2 was released on September 23, 2015. Development continues on 1.10.x, with over 400 commits per month. No target date or feature set has been defined. * Issue Tracker Moved The Subversion community did not move its issue tracker when it entered the Incubator and later become a TLP. We continued to use our original tracker on tigris.org. With some heavy lifting by our member Ivan Zhakov, the issues were ported over to the ASF's Jira instance, and the old tracker has been locked/closed.
Apache Subversion exists to be universally recognized and adopted as
an open-source, centralized version control system characterized by
its reliability as a safe haven for valuable data; the simplicity of
its model and usage; and its ability to support the needs of a wide
variety of users and projects, from individuals to large-scale
enterprise operations.
* Board Issues
There are no Board-level issues of concern.
* Community
Our last PMC addition was in March 2014.
On July 12, 2015, Holden Karau (ID: holden) was added as a
committer. Holden worked on Subversion before its move to the
Foundation, so while she is "new" here, this is a return from
hiatus to work on Apache Subversion's Scheme bindings.
* Releases
Since our report in May, the community has made multiple releases:
- On June 9th, our second release candidate for 1.9.x line (1.9.0-rc2)
- On July 14th, our third candidate (1.9.0-rc3)
- On August 5th, 1.7.21 was released to remedy two security issues:
CVE-2015-3184 and CVE-2015-3187
Note that the 1.8.x was "current" at the time, so releases to 1.7.x
are made only to fix security issues or severe/critical bugs.
- On August 5th, 1.8.14 was released to remedy the same CVEs noted
above for the 1.7.21 release. These two releases were complicated
by working with Apache HTTPD and their CVE-2015-3185 fixes, but
only from a release/publication standpoint. The two communities
worked well together.
- On August 5th, the first release to the 1.9.x line was made (1.9.0).
Release notes at:
http://subversion.apache.org/docs/release-notes/1.9.html
This moves the 1.7.x line to "unsupported", and the 1.8.x line will
only see future releases to fix security/severe/critical bugs.
- On August 14th, 1.7.22 was released to fix a test case, so that
our 1.7.x series can be set aside cleanly.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community A small hackathon/gathering occurred during the ApacheCon US in Austin. Some work was completed, but it was not as well-orgniazed as past hackathons. There are another couple possibilities in the near future. The community tends to gather at hackathons once or twice per year. Subscribership across our mailing lists is down about 1% this quarter, but activity is up about 20%. The project has 43 PMC members and 79 committers (in varying capacities). We are one of the few PMCs with Universal Commit. Our last PMC addition was Mar 2014, and committer in Sep 2014. As a mature project, new faces in our community are rare, but we continue to work to include people as they arrive. * Releases Since our last report in Feb, we released 1.7.20 and 1.8.13 in March to (primarily) fix some security issues. (1.8.12 was skipped) On May 11, we posted our first 1.9.0 release candidate (1.9.0-rc1). Based on past experience, the actual release should drop in the next month or two.
Apache Subversion exists to be universally recognized and adopted as
an open-source, centralized version control system characterized by
its reliability as a safe haven for valuable data; the simplicity of
its model and usage; and its ability to support the needs of a wide
variety of users and projects, from individuals to large-scale
enterprise operations.
* Board Issues
There are no Board-level issues of concern.
* Community
The community is getting ready to branch 1.9.x as part of our
release process. Assuming the branch occurs in the next week or two,
then the release should appear late March or early April.
There is some planning in-process for a Subversion hackathon to
occur around the same time as ApacheCon (Austin).
Mailing list activity:
users@ (779 subscribers): 390 messages across Nov/Dec/Jan.
dev@ (330 subscribers): 583 messages across Nov/Dec/Jan.
Our last PMC addition was February 2014, and our last (non-PMC)
committer was added in July 2013.
* Releases
The project made two releases to resolve CVE-2014-3580 and
CVE-2014-8108:
1.8.11 -- Current series, released on December 15, 2014
1.7.19 -- Prior series, receives maintenance/security patches,
released on December 15, 2014
Information about our 1.9.x releases should be present in our next
quarterly report.
Apache Subversion exists to be universally recognized and adopted as
an open-source, centralized version control system characterized by
its reliability as a safe haven for valuable data; the simplicity of
its model and usage; and its ability to support the needs of a wide
variety of users and projects, from individuals to large-scale
enterprise operations.
* Board Issues
There are no Board-level issues of concern.
* Community
The community has been working through some issues on features to be
included (or not) in the upcoming 1.9 release. It has been
difficult, and tensions have risen, but it appears the impasse has
been resolved and focus on a release can resume.
Regarding the above, it should be noted that the VP (Greg) declared
a past veto as closed/not-applicable, with the intent of moving the
community forward, and repairing the discussion/dynamic. The PMC
members involved seem to alright with that decision, and certainly
retain their rights/desires to reinstate a veto upon the changes and
features, should they find them suspect for a release.
Our last PMC addition was February 2014, and our last (non-PMC)
committer was added in July 2013.
* Releases
No releases have been made since our report in August.
Current releases are:
1.8.10 -- Current series, released on August 11, 2014.
1.7.18 -- Prior series, receives maintenance/security patches,
released on August 11, 2014.
1.9.0-alpha2 -- Future series, released on April 4, 2014.
Apache Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. * Board Issues There are no Board-level issues of concern. * Community Evgeny Kotkov was added to the Subversion PMC in February 2014 (this was apparently left out of previously reports). No change in committers, our last new committer was in July 2013. An Elego hosted hackathon was held in Berlin from June 16th - 20th. We had approximately 11 developers attend. In Berlin we discussed issues with the upcoming 1.9.0 release and started planning future features for 1.10.0. There will be another hackathon August 18th - 22nd in Sheffield, England, with around 8 developers expecting to attend. We hope to finish up on 1.9.0 issues with that hackathon and spend more time working on changes planned for 1.10.0. Beyond our work towards the 1.9.0 release, we continue to support the 1.8.x series. The 1.7.x series receives security updates, and (sometimes) high-value functionality updates. We continue to get around 200 messages per month on the users@ mailing list, with most questions being answered. Often times by non-developer community members. The development list continues to see between 150-250 messages a month, and around 200 commits per month. The commit rate has slowed slightly as we work towards stability on trunk for a 1.9.0 release. Development can still be considered healthy. * Releases Work toward 1.9.0 is progressing but no further alpha has been produced since our last report. However, we do anticipate a branch sometime in the near future and our normal stabilization period following that. Which typically includes betas and release candidates. Since our report in May, Apache Subversion 1.8.10 and 1.7.18 were both released on August 11th.
* Overview No board-level issues at this time, since our report in February. * Community No changes in committers or PMC makeup. Our last committer was added in July 2013. Our last PMC addition was March 2012. The Subversion Live conferences hosted by WANdisco were held in early May. An elego-hosted hackathon will be held in Berlin in June, and a hackathon hosted by WANdisco is being assembled for August. Historically, these have been well-attended and well- regarded by the Subversion committers. * Releases In February, the community began preparing an alpha release of 1.9.0. That alpha had several problems and was pulled. 1.9.0-alpha2 was eventually released on April 14, 2014. Discussions are being held regarding finalizing "trunk", branching, and beginning the release process. Much of the discussion will occur at the above- mentioned hackathon in June with summaries posted to the list for non-attendees to participate (as is typical with Subversion hackathons and the face-to-face discussions). Since our report in February, Apache Subversion 1.8.9 was released on May 14, and 1.7.17 was released on May 19.
* Overview No board-level issues at this time, since our report in January. * Community No changes in committers or PMC makeup. Our last committer was added in July 2013. Our last PMC addition was March 2012. * Releases The community is currently voting on a number of releases, at the time of the February board meeting. These candidates consist of an alpha for 1.9.0, for 1.8.8, and for 1.7.16. For those keeping score at home since the prior release numbers, the 1.7.15, 1.8.6, and 1.8.7 version numbers were skipped/pulled.
verbal approval of late report
* Overview No board-level issues at this time. This is a make-up report for Nov 2013. Our last report was Aug 2013. We will report again next month (Feb 2014). * Community No changes in committers or PMC makeup. Our last committer was added in July 2013. Our last PMC addition was March 2012. The developers continue to work towards a 1.9 release, and on supporting the 1.8.x series. The 1.7.x series receives security updates, and (sometimes) high-value functionality updates. We get about 200-300 messages per month on the users@ mailing list, and interaction is good. We have a broad set of people to support the community. The development list sees about 150-250 messages per month, and 200-700 commits per month. Development is progressing smoothly. * Releases In our last report, the community was preparing 1.8.2 and 1.7.12. Those versions were pulled, and (instead) 1.8.3 and 1.7.13 were released on August 30. We also released 1.8.4 on Oct 29, 2013, then 1.8.5 and 1.7.14 on Nov 25, 2013.
No report was submitted.
AI: Brett to pursue a report for Subversion
No report was submitted.
* Board Issues There are no Board-level issues of concern. * Community Daniel Gruno was added as a committer in July (2013), Markus Schaber in June, and Mattias Engdegård in May. Our last PMC addition was in March, 2012. There is nothing special to report about the community. It is working towards 1.9.x, supporting the 1.8.x series on the users@ mailing list, and responding to issues and security concerns. The elego hackathon in June went well, with many in the community attending. Lots of discussion occurred, with the consensus ideas brought back to the developer list. There will be a "Subversion & Git Live" series of events in October. This will be the third year WANdisco has run the event; they provide support for PMC members and other Subversion developers to attend, so it has been a good opportunity for the community to meet. * Releases Apache Subversion 1.8.1 and 1.7.11 were released on July 24, 2013. The community will start the release process for 1.8.2 and 1.7.12, the week of August 19, 2013.
On Tuesday, June 18, Apache Subversion 1.8.0 was released. This release was the culmination of twenty months of work, and the Apache Marketing/PR group helped with announcing and spreading the word. With this release, the development community will begin work on the 1.9.x series. Fixes will be backported to 1.8.x and releases will be performed (historically, this happens about once a month). Security fixes will be backported to the 1.7.x series, which historically occurs once every two or three months. The 1.6.x series will be retired and no further releases will be made. When the Apache Subversion project arrived at the Foundation, the community continued to perform backported releases of 1.5.x and 1.6.x via the tigris.org platform. With the 1.6.x pre-Foundation release now deprecated, the community will only be producing Foundation releases henceforth. Moving forward, the community is looking to shrink the twenty month release cycle to approximately nine months. As that frequency would deprecate a release in just eighteen months, the community may adjust its support policies to include a third historical release series.
* Board Issues There are no Board-level issues of concern. * Community elego is sponsoring a hackathon in Berlin again. Unlike past years, this is being run independent of a paid conference. This will happen next month (June), lasting for a week. The Subversion community has greatly benefited from these hackathons and is looking forward to attending again. We added one new committer (rschupp). Our last PMC Member was added in March, 2012. * Releases 1.8.0-rc2 has been produced for the community to evaluate. We expect the 1.8.0 release to occur in June. When that happens, we will fully deprecate the 1.5.x series, according to Subversion policy. The 1.6.x series will receive only security updates, and 1.7.x will continue receive useful, important, and security updates. Since our February report, Subversion 1.6.21 was released on April 4th (to tigris.org); this was primarily a security release. In addition, Apache Subversion 1.7.9 was released on the same day to fix the same set of security issues. The Security Team helped the PMC with CVE generation, and overall assistance. LATE NOTE: the versioning policy described above is incorrect. Please see subversion.apache.org and our report next month. In short: 1.6.x will be fully deprecated and receive no updates.
Subversion will report again next month to clarify the handling/deprecation of older versions
* Board Issue There are no Board-level issues of concern. * Community We have two new "partial" committers (their work is primarily constrained to branches). One is Gabriela Gibson (gbg), who was accepted as part of the [GNOME] Outreach Program for Women (https://live.gnome.org/OutreachProgramForWomen), with Stefan Sperling acting as her mentor. The second committer is Prabhu Gnana Sundar (prabhugs). elego is hosting a hackathon in Berlin in June. The past few years have been a great success, with many from the Subversion community in attendance. This year, there will not be an associated conference as in the past, allowing for a stronger ASF branding and wider range of visibility/invitations. * Releases Apache Subversion 1.7.8 was released on December 20th. The pre-ASF Subversion had a maintenance update to 1.6.20 on January 8th.
** Board Issues There are no Board-level issues at this time. ** Releases As we reported in June, the Apache Subversion 1.7.6 was imminent, and was released on August 15. Since then, Apache Subversion 1.7.7 was released on October 9th. We also performed a non-Apache release of Subversion 1.6.19 on September 21. ** Community The Subversion Live events in October (produced by WANdisco) were well-attended by users, and many of the Subversion committers. We have added no new committers or PMC members since our last report. Ben Reser has returned from inactive status, and is being his old productive self.
No Board issues at this time. Since our report in June, the Apache Subversion project has added no new committers or PMC members; we have added to each group within the past six months. The 1.7.6 release is in-process and should occur coincident with the Board meeting, or within the following two days. One of the Foundation's sponsors, WANdisco, is hosting several Subversion events in October. A number of PMC members will be speaking and/or attending, along with a few ASF Members attending.
** Board Issues The Subversion project has no Board-level issues at this time. This is a supplemental report since our scheduled May report was late and abbreviated. ** Community The mailing list activity continues normally, with discussion on dev@ a bit higher than on users@. June 11 to June 15, elego hosted a hackathon for Subversion developers and invited guests. This coincided with their Subversion Day event on June 14. In past years, the community has found the hackathon to be a great way to gather and work through problems. Discussion results are returned to the list for larger community input. Since our last full report in January, we have added one PMC Member (Trent Nelson) and two committers (Ashod Nakashian and Vladimir Berezniker). In March, Greg queried the PMC on whether it was time to rotate the VP role. After a short discussion, the PMC confirmed their confidence with Greg continuing as VP, and potentially reviewing the situation in another year or two. ** Releases The project released Apache Subversion 1.7.4 on March 8, 2012, followed by 1.7.5 on May 17. The community also put together the (non-Apache) Subversion 1.6.18 release was made on April 12. These continue to be offered from Subversion's old project home on tigris.org. The release artifacts are also copied over to archive.apache.org. Discussion is ongoing, along with development for the 1.8.0 release.
An abbreviated, late report: the Subversion project is progressing normally, with no issues to report to the Board. Since the last report, we have added one committer (ashod) and one PMC member (trent). We have released 1.7.3 (as reported in February) and 1.7.4, and the 1.7.5 release is hitting the wire "now". Additionally, the community made a release of 1.6.18 (a non-Apache version, distributed from tigris.org). A complete report will be filed in June.
** Board Issues The Subversion project has no Board-level issues at this time. ** Community The user community continues its regular handling of about 400 messages per month. The development list is a bit higher, near an average of 500 per month. There have been no obvious problems over the past reporting period. In January, Andreas Stieger was added as a committer on the project. ** Releases The project released version 1.7.3 on Monday, February 13. We are planning a 1.6.18 release "soon" to deal with some high-profile issues. The 1.6.x series continues to be maintained under a "security and important fixes only" profile. These releases are made from tigris.org (rather than the ASF) due to its pre-ASF historical licensing. The community is looking forward to deprecating the 1.6.x series upon the release of the 1.8.x series. Currently, there are no dates for the 1.8.x series. The community does not want the overly-long release cycle that occurred with 1.7.0, so the next version should happen this year. ** Other elego has set the date for their Subversion hackathon in Berlin: it will be held June 11 to June 15, at their offices. The hackathon is open to all Subversion committers and selected invitees.
** Board Issues The Subversion project has no Board-level issues at this time. ** Community The user community is as active and healthy as ever. Many questions and answers are being handled for the new 1.7.x series of releases. The development community has been hard at work on the 1.8 release, tentatively scheduled for late Q1 or Q2 of 2012. The roadmap has not been positively defined, but there is a general feeling of coding to fit that timeframe, rather than a specific set of features. The community does not want to repeat a 2+ year development cycle, like what happened with the 1.7 release. We have added one new committer: Eric S. Raymond. No PMC Members have been added for quite a while. ** Releases This is the big news since our last report in August: the 1.7.0 release was made on October 11th. That is about 2.5 years from the 1.6.0 release in March 2009. The release has been well-accepted for its new features and performance updates. It is important to note this is the first release under the Foundation's policies, license, and distribution (the 1.6.x releases were made via tigris.org). Since that initial release, we made a 1.7.1 release on October 23rd, and then 1.7.2 on December 5th. We do not have a schedule for the 1.7.3 release, but it will likely appear in the next few weeks. ** Other Some private discussions have started about Subversion events next year, but nothing has (yet) been finalized or made public. These events have been very successful at bringing the development community together for some great discussions and hacking. More information will be provided as events are finalized.
No report received.
** Board Issues The Subversion project has no Board-level issues at this time. ** Community The user community has seen its typical level of questions, answers, and responsiveness. With our recent series of releases (see below), we've seen some great testing as the project leads up to its 1.7 release. The development community has been incredibly active since the 1.7 branch was created. There was a rather major division regarding the underlying network provider to use for the 1.7 release. The community handled this very well, working through the issue with lots of discussion, stating positions, bringing up concerns, and bringing in the necessary details to resolve the situation. While the community disagreed, it was handled with the peer respect that we expect of our communities. In the end, the issue was resolved just prior to this Board report and meeting, and should allow the community to proceed with the 1.7 release with many happier people. ** Releases Since the last report, the Apache Subversion project has created the stabilization branch for its 1.7.0 release. Since that time, the project has release three alphas, and two betas (beta1 and beta3, skipping beta2 for board-unimportant reasons). The project is very close to releasing its first release candidate. The only issue here is the rate of backports from trunk, and the aforementioned network provider. Presumably, the rate of requests for backporting to the stabilization branch will drop in the next few weeks and an RC1 will be produced. ** Other The project added two committers in June (moklo, arwin).
No Board-level issues at this time. This is a supplemental report, outside of our regular reporting timeframe. I'm happy to report that Apache Subversion is now releasing alphas under the Apache banner. The project has enjoyed a much-too-long grace period on making releases under the standard Apache banner and licensing regime. The community did not envision or desire it taking this long to produce a 1.7 release, but... well, it did take a while. On June 10, we released the first "alpha" of the 1.7 series. Beyond the proper Apache licensing and copyright, this is also the first release to go into the standard Apache distribution and mirror system. The 1.6 (and 1.5) releases that the community has produced while at the Foundation have resided at the old tigris.org distribution point since they were not true Foundation releases. They also are also mirrored on archive.apache.org. And yes, this is a self-congratulatory pat on the back to the community for finally reaching this point :-)
No Board-level issues at this time. We released 1.6.16 on March 3rd, 2011, and are preparing the 1.6.17 release for early next week. Both releases contain the standard mix of bug fixes, along with some security fixes (unfortunately). The PMC has worked with the Apache Security Team to acquire CVEs, discuss notification, and other issues. Many of the Subversion developers are in Berlin this week (the week of May 16). One of the main issues of discussion is the branching for the 1.7 release. We've hit our performance targets and are wrapping up the last dozen bugs. Most feel good about (finally!) branching by the end of the month, in preparation for early releases before our final 1.7.0 release. We are going to have early release series to get feedback, and also to iron out any issues with releasing from apache.org (the 1.6 releases continue from tigris.org since they do not use the ALv2 license). In our last report, we discussed the problems with WANdisco and its problems with our marks. Since that report, WANdisco has made progress and will be phasing out its older, infringing products in favor of a new product named uberSVN. We continue to monitor the situation and will be turning our focus to other actors in the Subversion space. No new PMC members or committers have been added in this period (last PMC appointment was in January 2011, and last committers were November and July 2010). Greg has entered into a private agreement with WANdisco for some work on Subversion. The agreement has been structured to avoid imposition on his duties at the Foundation, and the PMC has not raised any flags.
No Board-level issues at this time. The Subversion project has reached its end-game for the 1.7 development line and hopes to perform the branch soon. Meanwhile, the community is preparing a 1.6.16 release for the week of Feb 21, 2011. With review from Trademarks and Legal, the Subversion project has engaged WANdisco about numerous problems with trademark recognition, attribution, and customer confusion. The CEO has stated that a number of internal issues have been filed to bring their website, products, and other aspects in line with the ASF trademark guidelines. Given the extent of problems, it will take a while to complete this process. Since the last report, we have (re)added Ben Reser to the PMC. Ben was previously on Subversion's notion of a "PMC" before joining the ASF, but was omitted from the original PMC construction resolution. He has since re-engaged and was added to the PMC via grandfathering rules (rather than an additional vote). In addition, Johan Corveleyn was voted onto the PMC.
The project filed an extra report last month to report its 1.6.13 release and its status as "not quite Apache", along with our 1.7.0 plans which *will* be a true and proper release from the ASF. The project is preparing a new 1.6.14 release at the time of the Board meeting, and 1.7.0 is still on track for a release in Q1 of 2011. In the past month, we have added three new PMC members: * John Szakmeister (jszakmeister) * Daniel Näslund (dannas) * Stefan Fuhrmann (stefan2) John has been a "full committer" for years, so he has effectively been on the PMC. His addition this month is simply clearing up the paperwork. We added one new committer, Johan Corveleyn, to work on an experimental branch. At ApacheCon, CollabNet sponsored a Subversion meetup, but the event saw very few in attendance. The community is trying to determine better methods of outreach and marketing, and/or whether it is simply a reflection of Subversion's maturity and lack of "new hotness". Some discussions have begun recently about usage of the Subversion (registered) trademark. The community has had a usage policy for quite a few years and is trying to figure out the right alignment with the standard ASF policy, and if any policy changes need to occur. There is significant external usage that has been causing concern, but the community is also worried about hurting the very people who contribute most to the project. As is typical, the right answers are not obvious, and the Subversion project is working with the Trademarks group to figure out the right course.
This is an out-of-band report to the Board, to ensure that the Board is aware that we have released Apache Subversion 1.6.13, on October 1, 2010. This release is under the pre-Apache copyright notice and license, and the primary download point is at tigris.org. We have also placed the (signed) tarballs on archive.apache.org for long-term archival storage (where we have also duplicated all pre-Apache releases). Subversion 1.7.0 will be our first release under the Apache banner, with the appropriate copyright header, licensing, and standard release location. We expect to branch for the release by the end of this year, with the actual release occurring 30-60 days after that.
Subversion is a project that has yet to release under an Apache license, while the pre-Apache team continues to release code externally. There are plans to release under the Apache License 2.0 for the next major release 1.7.0.
** Board Issues
There are no Board-level issues at this time.
** Community
Since our last report, in May, we have added two more committers.
These are "partial" committers, meaning they are restricted to certain
portions of the tree. The first, artagnon, is a GSoC student for
Git(!) and is adding a new "svnrdump" client-side tool to produce or
load Subversion dump files remotely (eg. for fast-loading into Git).
The second, stefan2, is working on a branch with a broad set of
performance improvements across the system.
No new PMC Members ("full committers") have been added.
** Releases
We released 1.6.12 on June 21, and the development team is hopeful to
begin cutting 1.7 alpha releases in a few months. Subversion normally
does not produce "alpha" or "beta" releases, but with the major
changes in the 1.7 working copy, we wanted to return to a mechanism
that will get early releases into more peoples' hands.
A graduate student produced some initial work on a new MySQL-based
backend for Subversion. His school term ended, along with his
available time to work on the project. However, he has signed an ICLA
and provided a large patches for his work. This is due to land in our
tree, on a branch, Real Soon Now. Our hope is that others will be
interested and can investigate and continue his work, and that having
it in our tree will make that process easier.
** Other
elego's "Subversion Day" was considered very successful by all
participants. elego hosted a hackathon for the committers over four
days, and was an excellent host. Several guests from the community
were also able to join in, and an Apache Dinner was scheduled during
this time for a broader mingling of Subversion developers with their
new Apache friends.
SubConf is approaching in mid-September, to be held in Munich.
As noted by the Trademarks report in June, the Subversion (registered)
mark has been transferred from the Subversion Corporation over to the
ASF. We are in-process on pulling together all prior licensees of the
mark, and working to re-issue a new license between the ASF and those
licensees. The intent is to honor all prior commitments that
Subversion Corporation made to those entities.
Approved by general consent.
** Board Issues The Subversion project has no Board-level issues at this time. ** Community We have seen some patches and interest from new people on the list, and are paying close attention to them, so they will feel welcome and hopefully join the community. ** Releases Since we last reported (March), Subversion made a 1.6.11 release under its old header/licensing regime (continuing on the 1.5.x and 1.6.x branches; 1.7.0 will be the first ASF release). We are hoping for 1.7 to occur late this summer, and the development community continues to work on that release. We are planning to put all prior releases (back to 1.0 and possibly earlier) onto archive.apache.org for historical preservation. Some of the historical (signed) tarballs include LGPL dependent elements, so we will carefully label these (we cannot remove them without destroying the original signatures). More recent releases separate the dependencies, and we will simply omit those (they are optional). The 1.7 series will use the standard distribution and mirroring framework since they are true ASF releases. ** Other The issue tracker continues to remain offsite, as nobody is in any great rush to tackle that project (nor is there a specific known requirement for that to happen; just a desire of the project). The March Subversion event in NYC went well, producing a suggested roadmap that has been well-received and signed-off by the community. The Berlin Subversion event is on-track for the 10th through the 13th, and an "Apache dinner" will also be held during that time. We acquired one GSoC student who will improve the diff format generation to support additional options.
Greg will keep concom@ in the loop about these cool SVN events.
No board level issues. Greg to submit a make-up report next month.
** Board Issues The Subversion project has no Board-level issues at this time. ** Community We have seen a solid migration of our user and development community from our tigris.org ancestry over to the new ASF infrastructure. The new user list is very active; the development community had very few issues and has continued at a fast and healthy rate of development. One new committer was added: Daniel Näslund ** Releases 1.6.9 was released at the end of January (as reported in February, as part of our podling report) No releases are planned in the near-term. We typically release updates every 4-6 weeks, so it is reaching the point for a 1.6.10, but we have no pressing bug fixes or community interest (yet) in doing this. But historically, it is likely we will craft up a release within the next two months. The community is targeting Summer 2010 for our major 1.7 release, incorporating a complete revamp of the client-side operation, for speed and stability. ** Other Our transition from Incubator to TLP status has gone smoothly, simply because we *started* our ASF infrastructure setup as if we were a TLP. No changes were needed. We still need to move our issue tracker over to the ASF infrastructure. Much time as been spent lately on a website revamp. We've taking the transition as an opportunity to re-examine users' needs and how our website can best address that. There have been many examples at apache.org on how to best (or not!) help users seek the information they need. There is a Subversion event being planned in Berlin, in June, primarily sponsored by Elego. There will be a hackathon, along with a more structured program at that event. There will also be a gathering of a number of Subversion developers in New York City around March 25th, which will primarily be an informal discussion (over beers?) rather than a formal hackathon or program. The Subversion project will be jostling for a couple GSoC students this summer. Mentors and summer projects are being identified, along with engaging the Community Development people.
WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to version control, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Subversion Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Subversion Project be and hereby is responsible for the creation and maintenance of software related to version control; and be it further RESOLVED, that the office of "Vice President, Apache Subversion" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Subversion Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Subversion Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Subversion Project: * Max Bowsher <maxb@apache.org> * Paul Burba <pburba@apache.org> * Stephen Butler <sbutler@apache.org> * Branko Čibej <brane@apache.org> * Ben Collins-Sussman <sussman@apache.org> * Justin Erenkrantz <jerenkrantz@apache.org> * Brian W. Fitzpatrick <fitz@apache.org> * Julian Foad <julianfoad@apache.org> * Karl Fogel <kfogel@apache.org> * David Glasser <glasser@apache.org> * Lieven Govaerts <lgo@apache.org> * Neels J. Hofmeyr <neels@apache.org> * Greg Hudson <ghudson@apache.org> * Bert Huijben <rhuijben@apache.org> * Erik Hülsmann <ehu@apache.org> * Kamesh Jayachandran <kameshj@apache.org> * Mark Benedetto King <mbk@apache.org> * Senthil Kumaran S <stylesen@apache.org> * Stefan Küng <steveking@apache.org> * Philip Martin <philip@apache.org> * Joe Orton <jorton@apache.org> * Mark Phippard <markphip@apache.org> * C. Michael Pilato <cmpilato@apache.org> * Daniel Rall <dlr@apache.org> * Garrett Rooney <rooneg@apache.org> * Peter Samuelson <peters@apache.org> * Daniel Shahaf <danielsh@apache.org> * Stefan Sperling <stsp@apache.org> * Greg Stein <gstein@apache.org> * Sander Striker <striker@apache.org> * Kouhei Sutou <kou@apache.org> * Jeremy Whitlock <jwhitlock@apache.org> * Hyrum Wright <hwright@apache.org> * Blair Zajac <blair@apache.org> * Ivan Zhakov <ivan@apache.org> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Greg Stein be appointed to the office of Vice President, Apache Subversion, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Subversion PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Subversion Project; and be it further RESOLVED, that the Apache Subversion Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Subversion podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Subversion podling encumbered upon the Apache Incubator Project are hereafter discharged. Special Order 7D, Establish the Apache Subversion Project, was approved by Unanimous Vote of the directors present.
Subversion entered the Incubator on November 7, 2009. Subversion is a version control system. The Apache Subversion web presence at subversion.apache.org has been filled with content migrated from the existing website at subversion.tigris.org. Work continues to cull unneeded information, and better organize existing content. The community released Subversion 1.6.9 late last month. The release was made under the old license (to avoid having to relicense mountains of code on the release branch), and the release process was observed and monitored by the Incubator PMC as part of the podling's progress toward graduation. The podling's graduation vote was in-process when this report was written. It is strongly trending for graduation, so a resolution will be presented to the Board once the podling determines who will be recommended for the VP.
Subversion entered the Incubator on November 7, 2009. Subversion is a version control system. Mailing lists have been migrated to ASF infrastructure, and the old lists on tigris.org have been turned into read-only mode. No progress has been made to backfill archives, though some discussion has occurred. (Backfilling of archives is not required for graduation.) The most recent RAT report for Subversion shows only 32 unknown licensed files. Work continues on either removing inappropriately licensed files from the distribution tarballs or adding licenses to files found deficient. The Apache Subversion web presence at subversion.apache.org is being filled with content migrated from the existing website at subversion.tigris.org. Once migrated, the Subversion community plans on culling unneeded information, and better organizing existing content. (You don't get to redesign your page hierarchy everyday!) The community's plans to create a new patch release, have been a bit bumpy, due to a number of technical issues caught during the signing/validating period. These have been resolved, and the new patch release should be imminent. It should be noted that although this release will be made under the old license (to avoid having to relicense mountains of code on the release branch), the release process will be observed and monitored by the Incubator PMC as part of the podling's progress toward graduation. The podling remains optimistic that a rapid progression to graduation is possible in the next month. The project is very active, with over a 1100 commits in December and ~200 so far in January; 100s of messages per mailing list.
Subversion entered the Incubator on November 7, 2009. Subversion is a version control system. Mailing lists have been migrated to ASF infrastructure. As of Dec. 10th, the development mailing list has fully migrated over with the old tigris.org dev@ list being shut down. A users@ list has been created on ASF infrastructure and is being used, but there are a number of published references to the old tigris.org users@ address, so we are still discussing that transition - that should be complete within the next month. No progress has been made to backfill archives, though some discussion has occurred. (Backfilling of archives is not required for graduation.) The Subversion project has merged its source code history into the One True Repo at svn.apache.org. The old repository on svn.collab.net has been put in read-only mode, and all new development is happening on svn.apache.org. Most, if not all, active Subversion contributors have filed their ICLAs, and are continuing development on the new infrastructure. The most recent http://ci.apache.org/projects/subversion/rat-output.txt for Subversion shows only 70 unknown licensed files, down from more than 200 a couple of weeks ago. Work continues on either removing inappropriately licensed files from the distribution tarballs or adding licenses to files found deficient. The community plans to create a new patch release, Subversion 1.6.7, before the end of the year. Although this release will be made under the old license (to avoid having to relicense mountains of code on the release branch), the release process will be observed and monitored by the Incubator PMC as part of the podling's progress toward graduation. The podling remains optimistic that a rapid progression to graduation is possible in the next month or two.
Subversion entered the Incubator on November 7, 2009. Discussions have been occurring on general@incubator with respect to graduation requirements, and some options for the podling's mailing lists and location in the main ASF Subversion repository. In addition, a number of discussions have been occurring on Subversion's developer mailing list (dev@subversion.tigris.org) regarding the mailing lists (migration, shut down, target address, etc), repository choices and location, which bug tracker to use, website migration, and the buildbot system(s). INFRA-2321 has been opened to track the code migration, and is scheduled for the afternoon (EST) of Sunday, November 15th. INFRA-2324 has been opened to construct the core five mailing lists for the Subversion podling: dev@, users@, commits@, private@, and announce@. These mailing lists will be built on the subversion.apache.org hostname. While this is non-standard for a podling, discussion on general@incubator has raised no issues with it. We will later backfill archives for these lists with the content from their equivalents on subversion.tigris.org. The software grant from Subversion Corporation was filed in ASF records on November 14. Many Subversion developers have been sending ICLAs into the ASF. An initial batch of *eighteen* account requests has been sent to root. There are fifteen(!) Subversion committers who already had accounts at the ASF, and they will simply be added to the authorization file for the Subversion repository. The project has an initial status file in place, and its checklist items are being worked through. The podling is hoping that it can complete its work in time to place a TLP resolution on the December Board meeting's agenda.