Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Remove the last FIXME from the howto-release-Django doc.

  • Loading branch information...
commit c2907a6e3d96315027f7313885f3d0212dd19cbe 1 parent 2408861
Carl Meyer authored August 16, 2013

Showing 1 changed file with 5 additions and 4 deletions. Show diff stats Hide diff stats

  1. 9  docs/internals/howto-release-django.txt
9  docs/internals/howto-release-django.txt
@@ -83,10 +83,11 @@ A few items need to be taken care of before even beginning the release process.
83 83
 This stuff starts about a week before the release; most of it can be done
84 84
 any time leading up to the actual release:
85 85
 
86  
-#. If this is a security release, send out pre-notification **one week**
87  
-   before the release. We maintain a list of who gets these pre-notification
88  
-   emails at *FIXME WHERE?*. This email should be signed by the key you'll use
89  
-   for the release, and should include patches for each issue being fixed.
  86
+#. If this is a security release, send out pre-notification **one week** before
  87
+   the release. We maintain a list of who gets these pre-notification emails in
  88
+   the private ``django-core`` repository. This email should be signed by the
  89
+   key you'll use for the release, and should include patches for each issue
  90
+   being fixed.
90 91
 
91 92
 #. As the release approaches, watch Trac to make sure no release blockers
92 93
    are left for the upcoming release.

0 notes on commit c2907a6

Please sign in to comment.
Something went wrong with that request. Please try again.