Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Document the fact that we now put dead branches in the attic.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@11523 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit a53601c6748cf98c777f156068c0290b2943287f 1 parent 8da58e5
@ubernostrum ubernostrum authored
Showing with 6 additions and 8 deletions.
  1. +6 −8 docs/internals/svn.txt
View
14 docs/internals/svn.txt
@@ -114,14 +114,9 @@ not; in either case there comes a time when the branch is no longer
being actively worked on by any developer. At this point the branch is
considered closed.
-Unfortunately, Subversion has no standard way of indicating
-this. Generally, you can recognize a dead branch by viewing it through
-the web interface, which lists the date of the most recent change to
-the branch. Branches which have gone more than a month or two with no
-activity can usually be assumed to be closed. In the future, the
-layout of branches in the repository may be rearranged to make it
-easier to tell which branches are still active (e.g., by moving closed
-or abandoned branches into the ``django/branches/attic`` directory).
+Unfortunately, Subversion has no standard way of indicating this. As a
+workaround, branches of Django which are closed and no longer
+maintained are moved into the directory ``django/branches/attic``.
For reference, the following are branches whose code eventually became
part of Django itself, and so are no longer separately maintained:
@@ -184,6 +179,9 @@ were never finished:
* ``sqlalchemy``
+All of the above-mentioned branches now reside in
+``django/branches/attic``.
+
Support and bugfix branches
---------------------------
Please sign in to comment.
Something went wrong with that request. Please try again.