Author: ubernostrum
Date: 2009-09-11 17:00:24 -0500 (Fri, 11 Sep 2009)
New Revision: 11524

Modified:
   django/branches/releases/1.1.X/docs/internals/svn.txt
Log:
[1.1.X] Document the fact that we now put dead branches in the attic. Backport 
of r11523 from trunk.

Modified: django/branches/releases/1.1.X/docs/internals/svn.txt
===================================================================
--- django/branches/releases/1.1.X/docs/internals/svn.txt       2009-09-11 
21:59:29 UTC (rev 11523)
+++ django/branches/releases/1.1.X/docs/internals/svn.txt       2009-09-11 
22:00:24 UTC (rev 11524)
@@ -114,14 +114,9 @@
 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,7 +179,10 @@
 
 * ``sqlalchemy``
 
+All of the above-mentioned branches now reside in
+``django/branches/attic``.
 
+
 Support and bugfix branches
 ---------------------------
 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to