From 69aed8db4bc0c776c189675a3b11e74b284494c4 Mon Sep 17 00:00:00 2001 From: James Bennett Date: Fri, 11 Sep 2009 22:00:24 +0000 Subject: [PATCH] [1.1.X] Document the fact that we now put dead branches in the attic. Backport of r11523 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@11524 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/internals/svn.txt | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/docs/internals/svn.txt b/docs/internals/svn.txt index 7d010a7cfa..a287408312 100644 --- a/docs/internals/svn.txt +++ b/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 ---------------------------