Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

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

  • Loading branch information...
commit c2907a6e3d96315027f7313885f3d0212dd19cbe 1 parent 2408861
@carljm carljm authored
Showing with 5 additions and 4 deletions.
  1. +5 −4 docs/internals/howto-release-django.txt
View
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.
This stuff starts about a week before the release; most of it can be done
any time leading up to the actual release:
-#. If this is a security release, send out pre-notification **one week**
- before the release. We maintain a list of who gets these pre-notification
- emails at *FIXME WHERE?*. This email should be signed by the key you'll use
- for the release, and should include patches for each issue being fixed.
+#. If this is a security release, send out pre-notification **one week** before
+ the release. We maintain a list of who gets these pre-notification emails in
+ the private ``django-core`` repository. This email should be signed by the
+ key you'll use for the release, and should include patches for each issue
+ being fixed.
#. As the release approaches, watch Trac to make sure no release blockers
are left for the upcoming release.

0 comments on commit c2907a6

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