|
| 1 | +ietfdb (3.50) |
| 2 | + |
| 3 | + * For this release, the idsubmit port from esanchez@yaco.es has been merged |
| 4 | + in, which constitute substantial added functionality. This integrates the |
| 5 | + draft upload functionality with the python/django datatracker; it improves |
| 6 | + draft submission handling and security, and fixes problems with database |
| 7 | + breakage and inconsistency caused by the old implementation. With this also |
| 8 | + comes a major improvement of author extraction from draft text, provided by |
| 9 | + the ietf/utils/draft.py module from henrik@levkowetz.com. |
| 10 | + |
| 11 | + * Deployment note: Once the new release has been placed in its deployment |
| 12 | + directory, and the correct settings_local.py has been copied in, a command |
| 13 | + needs to be run in order to update the database tables to work with the new |
| 14 | + code. In the directory containing the ietf/ directory, run this command: |
| 15 | + |
| 16 | + $ PYTHONPATH=$PWD ietf/manage.py migrate |
| 17 | + |
| 18 | + The output should be as follows: |
| 19 | + |
| 20 | + Running migrations for liaisons: |
| 21 | + - Nothing to migrate. |
| 22 | + Running migrations for submit: |
| 23 | + - Migrating forwards to 0003_add_extra_name_fields. |
| 24 | + > submit: 0001_initial |
| 25 | + > submit: 0002_add_submission_hash |
| 26 | + > submit: 0003_add_extra_name_fields |
| 27 | + - Loading initial data for submit. |
| 28 | + |
| 29 | + Once this is done, the regular deployment routine should be continued. |
| 30 | + |
| 31 | + -- Henrik Levkowetz <henrik@levkowetz.com> 07 Apr 2011 17:15:41 +0200 |
| 32 | + |
1 | 33 | ietfdb (3.16) |
2 | 34 |
|
3 | 35 | This is a minor bugfix release. |
|
0 commit comments