test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

This commit is contained in:
Carl Meyer 2013-08-16 23:55:43 -06:00
parent 240886183b
commit c2907a6e3d
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/internals/howto-release-django.txt
View File

@ -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 This stuff starts about a week before the release; most of it can be done
any time leading up to the actual release: any time leading up to the actual release:
#. If this is a security release, send out pre-notification **one week** #. If this is a security release, send out pre-notification **one week** before
before the release. We maintain a list of who gets these pre-notification the release. We maintain a list of who gets these pre-notification emails in
emails at *FIXME WHERE?*. This email should be signed by the key you'll use the private ``django-core`` repository. This email should be signed by the
for the release, and should include patches for each issue being fixed. 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 #. As the release approaches, watch Trac to make sure no release blockers
are left for the upcoming release. are left for the upcoming release.