project_status.html   [plain text]


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<style type="text/css"> /* <![CDATA[ */
  @import "branding/css/tigris.css";
  @import "branding/css/inst.css";
  /* ]]> */</style>
<link rel="stylesheet" type="text/css" media="print"
  href="branding/css/print.css"/>
<script type="text/javascript" src="branding/scripts/tigris.js"></script>
<title>Project Status</title>
</head>

<body>
<div class="app">

<h1 style="text-align: center">Subversion Project Status</h1>

<p>Here is information about upcoming and past releases.  Each release
goes through a stabilization phase as described in
the <a href="hacking.html#release-stabilization">Hacker's Guide to
Subversion</a>.
The <a href="http://svn.collab.net/repos/svn/trunk/CHANGES"
>CHANGES</a> file contains an overview of what's new in each release.
Releases are always source tarballs; binary package updates for
various OS's generally follow the source tarball by a few days.</p>

<p>For information about what features are being worked on, and how we
coordinate features with releases, please see the <a
href="roadmap.html">roadmap</a> page.</p>

<div class="h2" id="upcoming" title="upcoming">
<h2>Upcoming</h2>

<ul>
  <li>
    <p><b>Subversion 1.6.0</b> (<i>future</i>):
    Feature and bugfix release.<br />
    See <a href="http://subversion.tigris.org/issues/buglist.cgi?component=subversion&amp;issue_status=NEW&amp;issue_status=STARTED&amp;issue_status=REOPENED&amp;target_milestone=1.6&amp;target_milestone=1.6-consider"
    >open issues marked for 1.6 or 1.6-consider</a>.</p>
  </li>

  <li>
    <p><b>Subversion 2.0.0</b> (<i>future</i>):
    Feature and <a href="hacking.html#release-numbering"
    >compatibility-affecting</a> release.<br />
    See <a href="http://subversion.tigris.org/issues/buglist.cgi?component=subversion&amp;issue_status=NEW&amp;issue_status=STARTED&amp;issue_status=REOPENED&amp;target_milestone=2.0"
    >open issues <em>under consideration</em> for 2.0</a>
    (<em>absolutely not commitments</em>, and likely to change).</p>
  </li>
</ul>

</div>

<div class="h2" id="older-releases" title="older-releases">
<h2>Older Releases</h2>

<p>Information about older releases is located on a <a
href="release-history.html">separate page</a>.</p>

</div>

</div>
</body>
</html>